CAPCON Admin Help

Platform administration โ€” institutions, users and groups, as in the SAGRIS ODC platform (ยง2), plus the platform settings the other apps depend on.
โ† All apps

CAPCON Admin

Platform administration โ€” institutions, users and groups, as in the SAGRIS ODC platform (ยง2), plus the platform settings the other apps depend on.

Platform administration โ€” institutions, users and groups, as in the SAGRIS ODC platform (ยง2), plus the platform settings the other apps depend on. The user-facing surface of the auth service on :5100; it holds no account data of its own.

What it does

Panels

Use the menu on the left; each panel has its own help topic.

Institutions

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Manage institutions (contract holders) and their app entitlements.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Users

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Manage user accounts, their institution membership and activation.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Groups & Permissions

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Manage groups and the permissions each group grants.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Roles & Approvals

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Assign the scoped roles (company manager, group manager), approve group members and grant each member their applications.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Project Access

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Grant per-project access, which is what Checks, Models and Results filter their project lists by.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Platform Settings

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Set platform settings, above all the base folder of the project tree.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.