Sign-in and roles¶
Who can see and change what in the app, and how a sign-in works.
Sign in¶
Signed out, the app shows only its sign-in page (Sign in to see the platform's workers, worlds and scenarios.) and a Log in button. Log in sends you to the organisation's identity provider (Pocket ID on medusa); after you sign in there you come back to the page you started from.
- A sign-in lasts 12 hours by default (
VIRTUFIN_APP_SESSION_HOURSon the server); after that the app asks you to log in again. - The header shows your name, a badge and Log out. Log out ends the session.
- If the provider takes longer than 10 minutes to send you back, the sign-in is refused (the sign-in took too long or was not started here; sign in again): log in again.
Roles: who may write¶
| You are | You may |
|---|---|
| Signed in (any member) | Read everything: every view, every list, every stream. The badge says read only; buttons that change something are disabled, with the tooltip Only admins may …. |
A member of the admin group (virtufin-admins by default, VIRTUFIN_APP_ADMIN_GROUP on the server) |
Also write: start, stop, create, delete, tag, schedule, share, halt, … The badge says admin. |
The app server enforces this, not only the buttons: a write from a non-admin is refused
with 403 only admins may write whatever sends it (a view, a script, the assistant). See
Architecture for how the server tells a
read from a write.
Your admin membership is read when you sign in: after a change in the provider's groups, log out and in again.