CAPCON Admin Help

Platform administration β€” Clients and their contracts, people and their role in each Client, what each role may do, and the platform settings the other apps depend on.
← All apps

CAPCON Admin

Platform administration β€” Clients and their contracts, the people of each Client with their role there, what each role may do, and the platform settings the other apps depend on.

ADMIN is the Administrators' application. It is the user-facing surface of the auth service on :5100 and holds no account data of its own. A Client's Managers run their own Client's people and project grants in PROJECTS β†’ Users.

What a person needs

Set separately on purpose β€” the role is what someone may do in a Client, the contract what the Client may open, the grant which projects. Missing one is the usual cause of "I can sign in but see nothing".

Stored inWhat it decidesSet in
Client & roleuser_companiesWhere they work, and ONE role there: Manager Β· Operator Β· Viewer. Different Clients may give different roles. No role: nothing.Clients or Users
ContractcompaniesThe applications the Client bought β€” a ceiling for every role. FARMING is an add-on.Clients
FARMINGuser_companies.farmingAn Operator opens FARMING only when the contract has it and their Manager ticks it.Clients, Users, or PROJECTS β†’ Users
Project grantproject.yamlWhich projects an Operator or Viewer sees, by name. Managers see their Client's own.PROJECTS β†’ Users

An Administrator needs none of them: the role is system-wide β€” every application, every Client, every project.

Order of work: Client and contract β†’ person into the Client with a role β†’ project grant.

The screen

<Client>: <role> for each Client you work in) and the applications you open. Almost every "why can't I…" starts with being signed in as somebody other than you think.

Manager** (set one in Clients β†’ Edit), how many people and how many of them are disabled, and how many have no role yet (place them in a Client with a role).

Panels

PanelDoes
ClientsCreate Clients, set their contract, activate and deactivate them; their Managers listed under each; the people of each with their role there.
UsersEvery person: Clients & roles, active, what they open. Edit β€” the Administrator switch, roles per Client, FARMING β€” and Delete.
RolesWhat each role may do β€” edit the optional permissions, essential ones locked β€” and what it may open: default, add-on, restricted.
SettingsPlatform settings, above all the base folder of the project tree.

When it goes wrong

list means scope, not an empty platform.

not the protection: the auth service re-checks every change and refuses one that is outside your reach.

button). Admin uses your sign-in token, not an API key.

lists. Signed in as is still shown; the message says what failed.

Clients

What this panel is for

A Client is a contract-bound customer: the applications it bought, and the people who work for it, each with one role in it β€” Manager, Operator or Viewer. The same person may be Manager in one Client and Viewer in another.

Open it to register a new customer, to change what a customer's contract covers, to put people into a Client and give them their role there, and to check that every Client has a Manager. Everything on this panel is an Administrator's; a Manager runs their own Client's people in PROJECTS β†’ Users.

The table

Each Client takes two rows.

RowShows
firstclient β€” the name, an amber inactive tag if it is switched off, and its description; applications (contract) β€” every application: green when the contract covers it, greyed when it does not; people β€” how many work for it; Edit, Deactivate / Activate, Delete
secondManagers: each Manager's e-mail in green β€” or an amber none yet when the Client has no Manager β€” then how many Operators, Viewers and people without a role it has

A Client with none yet is run by nobody but the Administrators. Set a Manager in Edit.

How to use it

Register a Client

  1. Type the name under the table (new Client name), optionally a

description, and press + Create. Created <name>. Edit it to set its contract and people.

  1. Press Edit on its row.

A new Client's contract starts with every application but FARMING: the add-on is ticked only when it is bought.

Edit β€” contract

  1. description β€” a contract note; it wraps under the name in the table.

Press Save description.

  1. Tick or untick the applications covered by this contract. **Each tick

saves at once**, and the result is shown at the top of the editor: FARMING added to <Client>'s contract. No role in the Client opens an application that is not ticked here: the contract is a ceiling.

FARMING is a commercial add-on. Ticking it here does not open it for everyone: the Client's Managers open it by role, and each Operator opens it only when their Manager (or you) ticks FARMING for them. Viewers never do. Without it, the editor says FARMING is not in this contract, so nobody here opens it.

Edit β€” People of <Client>

Administrators are listed first, as Administrator β€” system-wide, in every Client. Their role is not set here and cannot be removed here: it is the Administrator switch in USERS β†’ Edit.

One row per person in the Client:

ColumnMeans
persone-mail, and the full name under it
role in <Client>Manager Β· Operator Β· Viewer Β· β€” no role β€”. Changing it saves at once: <e-mail> is now Operator in <Client>.
FARMINGa tick box for an Operator, when the contract includes FARMING; by role for a Manager; β€” otherwise
Remove β€” takes the person out of this Client, after you confirm

To add someone, choose them in + add a person… β€” every registered account not yet in this Client, with newly registered ones marked (new β€” in no Client) β€” pick their role (Operator is preselected) and press Add. <e-mail> added to <Client> as Operator. Then grant them projects (the Client's Manager does it in PROJECTS β†’ Users).

Deactivate, activate, delete

they open nothing through it β€” and keeps every record. Activate restores everything.

application this contract gave. Their accounts are untouched. It cannot be undone.

What it writes

Nothing in the project tree. Everything goes to the auth service's database (schema capcon_auth): the Client, its description, contract and active flag to companies; each person's membership, role and FARMING tick to user_companies. A change reaches the other applications within a minute (they cache a sign-in check for 60 s).

When it goes wrong

application not ticked here stays closed whatever the role.

contract, and the tick in their row.

is inactive.

grant, set by the Client's Manager in PROJECTS β†’ Users.

CLIENTS* β€” tick FARMING in the contract first.

granted, at once β€” that is intended. Put them back with + add a person… and the grants count again.

Users

What this panel is for

Every registered person, and what decides what they can do:

setting. A switch on the person;

Manager in one Client and Viewer in another is normal. On a project, the role in that project's Client applies, and the Client's contract caps the applications (see Roles);

it.

Open it when someone has just registered, when someone's job changes, and first of all when someone says "I can sign in but see nothing". The same per-Client roles are edited from the other side in Clients β†’ Edit.

Before you start

place them. They appear here with no Client β€” place them via Edit.

The table

ColumnMeans
persone-mail, and the full name under it if one is set
Clients & rolesfor an Administrator, a green Administrator β€” in every Client (the role holds in each Client and is not set per Client); otherwise each Client they work in with their role there (Manager in green, β€” no role β€” in amber), and FARMING where the add-on is on for them. A Client tag in amber is an inactive Client β€” it gives them nothing while it is off
activethe dot: on = active, off = disabled (every key stops working)
opensthe applications they actually open now, by the same rule every app enforces: ALL for an Administrator, otherwise each role's applications within its Client's contract; nothing if none

Use the filter box to narrow the list by e-mail or name.

How to use it

Place a newly registered person

  1. Find the person and press Edit. The editor opens below the row.
  2. Under Clients & roles, choose their Client in + add to a Client…,

pick their role there (Operator is preselected) and press Add. <e-mail> added to <Client> as Operator.

  1. For an Operator in a Client whose contract includes FARMING, tick

FARMING if they need it.

  1. Check the opens column, then have them granted the projects they need β€”

the Client's Manager does it in PROJECTS β†’ Users.

Every change in the editor saves at once and says so in the status line; there is no separate Save, except Save name for name and organisation.

Other changes

It applies in that Client only. <e-mail> is now Viewer in <Client>.

only where the contract includes it. A Manager shows by role.

confirm. Untick to undo. Not on your own account.

and confirm. They lose their role there, its applications, and every project of that Client.

it is reversible. Prefer it to deleting.

API keys and its roles in every Client. It cannot be undone; the person can register again, as a new account with nothing.

(PROJECTS β†’ Users). The panel lists such accounts at the top, and the row carries a deletion requested tag naming who asked, when and why. The account is already suspended in every Client. Deleting is yours: review, then Delete β€” or leave it suspended. Managers cannot delete accounts.

person in that Client, or switched some of their Operator modules off.

What it writes

Nothing in the project tree. Everything goes to the auth service's database (schema capcon_auth): the Administrator switch to users.role, each Client membership with its role and FARMING tick to user_companies, name, organisation and active flag to users. A change reaches the other applications within a minute (they cache a sign-in check for 60 s).

Who sees what

An Administrator sees everyone, including people placed in no Client. Only an Administrator places a person into a Client or takes them out, and only an Administrator makes or unmakes an Administrator. Managers do not use this app: they set the roles of their own Client's people in PROJECTS β†’ Users.

When it goes wrong

role β€”* in the Client: set one. The Client tag is amber: the Client is inactive. opens shows the apps but the project is missing from the selector: that is a project grant (PROJECTS β†’ Users), not something this panel sets.

<Client> does not include '<permission>' β€” ask that Client's Manager* β€” on a project, the role in that project's Client applies, not their strongest role elsewhere. Change the role in that Client, or what the role may do in Roles.

(Clients) and their FARMING tick must be on.

your own Administrator tick is locked for the same reason.

CLIENTS* β€” add it to the contract in Clients β†’ Edit first.

β€” you cannot delete or disable your own account.

Administrator switch are an Administrator's; you are signed in as someone else than you think (check Overview β†’ Signed in as).

Manager of an active Client.

Roles

What this panel is for

The roles, what each may do, and what each may open.

An Administrator is system-wide. Everyone else holds one role in each Client they work in β€” Manager, Operator or Viewer β€” and on a project the role in that project's Client applies. Manager in one Client and Viewer in another is normal.

Open it to answer "what can an Operator actually do?", to switch a permission on or off for a role, or to see who holds each role. A person's role is set elsewhere: Clients β†’ Edit (per Client) or Users β†’ Edit (per person).

The cards

One card per role: Administrator, Manager, Operator, Viewer.

Administrator(s), or holder(s) across Clients (a person who holds the role in two Clients counts twice).

May do

ChipMeans
πŸ”’ greenessential β€” always on. The role does not work without it, so it cannot be switched off
amberon β€” click to switch off
β—‹ greyoff β€” click to switch on

The Administrator card says may do β€” everything. The platform permissions (users.manage, platform.settings) are an Administrator's alone and are not offered to the Client roles at all.

Essential, for reference: a Manager always holds projects.read, projects.write and client.read; an Operator and a Viewer always hold projects.read.

May open

ColumnMeans
defaultthe applications the role opens, within the Client's contract
add-onFARMING β€” for a Manager, open when the Client's contract includes it; for an Operator, when the contract includes it and their Manager ticks it
restrictedapplications the role never opens

What a role opens is fixed by the platform, not edited here. It may be revised in future.

How to use it

  1. To check what a role allows, read its card.
  2. To change it, click a chip on a Manager, Operator or Viewer card. It saves

at once: Operator: client.push switched on. Takes effect within a minute.

  1. If a role's permissions differ from the platform's default, **Restore the

default** appears under its chips. Operator: default permissions restored.

A change applies to every holder of that role, in every Client, on this server, within a minute. There is no per-Client variant: switching client.push on for Operators gives every Operator of every Client the right to write into their client's database.

Only an Administrator can edit what a role may do.

What it writes

The Administrator's choice for each Client role, to role_permissions in the auth service's database. No row means the platform's default. The server re-applies the essential set and drops any platform permission whatever is stored, so an essential permission can never be lost.

When it goes wrong

the role in that project's Client applies: they may be Viewer there. Check their row in Users. Or the application is outside the Client's contract (Clients).

ticked for them in Clients β†’ Edit, Users β†’ Edit or PROJECTS β†’ Users.

every role but Administrator. A Manager's administration is in PROJECTS β†’ Users.

permission* β€” exactly that.

(ADMIN_BOOTSTRAP_EMAILS on the server) are Administrators without the stored role, and are not counted.

Platform Settings

The folders every CAPCON application depends on. Each is set once, here, and every app reads it on each request, so a change takes effect immediately, with no restart.

SettingHoldsDefault
Project tree<base>/<year>/<project>/<period>/ β€” projects, their field layers, statistics and results; the Inputs region store (_regions/)/opt/capcon_projects (x93: /mnt/disk1/projects)
Source data (obligatory)<base>/<year>/<cell>/ β€” one folder per year, one per 50 Γ— 50 km grid cell inside it, holding symlinks to the Sentinel-1 dekadal and monthly COG products. Projects β†’ Sampling reads its rasters here./mnt/disk1/images
Sentinel-1 RGB maps<base>/<year>/<CC>/ β€” one folder per year, one per three-letter country code inside it (LIT, LAT), holding symlinks to GeoTIFF (COG) RGB images on this server and on NFS servers/mnt/disk1/maps/S1
Sentinel-2 RGB mapsthe same layout, for Sentinel-2; Farming β†’ Mowing reads its images here/mnt/disk1/maps/S2
Shared tile storethe per-tile S1 composites and indices INPUTS makes, <tiles>/sar_data/<year>/<tile>/ and <tiles>/indices/<year>/<tile>/ β€” made once and reused by every project whose region lists the tile/mnt/disk1/tiles
World grida FILE: the GeoPackage of the standard 0.5Β° image tiles (tile_id, lon_min, lat_min); PROJECTS β†’ Region lists a project's tiles from it. Saved only when the file existsβ€” (must be set)

How to use it

  1. Type the folder's full path (it must start with /).
  2. Tick create if missing if the folder does not exist yet.
  3. Press Save (or Enter). The line below shows the folder now in use and

the one before it.

What each line tells you

is not writable by it, nothing can be created there.

folder holds. The symlinks are not followed here: their targets may be on NFS servers, and checking them would make this page walk the whole archive over the network. The links are made outside CAPCON.

Changing a folder moves nothing

Whatever is under the old folder simply stops being used. Move the files yourself first, or point the setting back.

When it goes wrong

folder (/srv/capcon) must belong to the service user. On the server: sudo chown gedas:gedas /srv/capcon.

create if missing and save again, or create it on the server and give it to the service user.

but holds no country folders yet.

no <year>/<CC>/ folder for the region's country under Sentinel-2 RGB maps, or it holds no S2_L3B_10m_<date>_RGB832_pic.tif links.