Roles and organizations¶
Who works in the portal¶
The portal has two kinds of users. Platform users work for the provider; organization users work for a client organization.
| Role | Kind | What it does |
|---|---|---|
| Super admin | platform | Every right in the portal: users and roles, settings, every approval and action. |
| Resource manager | platform | Approves new projects (names them, places them on a site and cluster, confirms the resources), resource changes, network changes and deletions; approves new organizations and assigns their platform users; moves a project to another organization. |
| Support engineer | platform | Approves corporate projects when that step is ticked; sets the VLAN of L2 channels, changes the size of internet gateways, runs the platform work. |
| Sales manager (sales rep) | platform | The organization's manager: full rights over the organizations they manage and all their projects (below); approves its new projects and its registration when sales approval is on, and a project moved to its organization. |
| Key account manager | platform | The organization's account contact: the organization is read only to them, except that they invite, lock and unlock its users and manage the resources of its projects (below). Optional. |
| Organization admin | organization | Everything of the organization: orders projects and asks for their changes and deletion, manages its users and gives the project admin role; gets the access details of its new projects. |
| Project admin | organization | The projects given to them: asks for changes of their resources and networks, sees the access details, invites project users. Does not delete the project. |
| Project user | organization | Sees the projects given to them, changes nothing. |
| Read only | organization | Sees every project of the organization, changes nothing. |
A person may hold several roles; holding several, they approve once for all of them.
The sales rep and the key account manager are set on the organization. The resource manager and the support engineer are set on the project: a project without its own takes the organization's.
Each project has one project admin as its contact: a user of its organization, chosen when the project is ordered and changed in Edit project. This person gets the project's access details when it is provisioned.
flowchart LR
subgraph provider ["Platform users — the provider"]
SA[Super admin]
RM[Resource manager]
SE[Support engineer]
SR[Sales rep]
KAM[Key account manager]
end
subgraph client ["Organization users — a client organization"]
OA[Organization admin]
PA[Project admin]
PU[Project user]
RO[Read only]
end
OA -- orders, changes, deletes --> T[(Projects)]
PA -- resources of the projects given --> T
PU -. sees the projects given .-> T
RO -. sees all .-> T
RM -- approves, places, moves --> T
SR -- full rights over its organizations --> T
SE -- L2 VLANs, gateway size --> T
KAM -- users, resources --> T
SA -- every right --> Tflowchart LR
subgraph provider ["Platform users — the provider"]
SA[Super admin]
RM[Resource manager]
SE[Support engineer]
SR[Sales rep]
KAM[Key account manager]
end
subgraph client ["Organization users — a client organization"]
OA[Organization admin]
PA[Project admin]
PU[Project user]
RO[Read only]
end
OA -- orders, changes, deletes --> T[(Projects)]
PA -- resources of the projects given --> T
PU -. sees the projects given .-> T
RO -. sees all .-> T
RM -- approves, places, moves --> T
SR -- full rights over its organizations --> T
SE -- L2 VLANs, gateway size --> T
KAM -- users, resources --> T
SA -- every right --> T
What each role may do¶
The rights over an organization and its projects. The sales rep and the key account manager have them only for the organizations they are set on; the organization admin and the project admin only in their own organization.
| Right | Super admin, resource manager | Sales rep | Key account manager | Organization admin | Project admin |
|---|---|---|---|---|---|
| Add an organization | yes | yes (they become its sales rep) | — | — | — |
| Edit the organization | yes | yes | — (read only) | — | — (read only) |
| Change its sales rep, key account manager or resource manager | yes | — | — | — | — |
| Invite, lock and unlock its users | yes | yes | yes | yes | — |
| Archive its users and bring them back | yes | — | — | yes | — |
| Give the project admin role | yes | yes | — | yes | — |
| Order a project | yes | yes | — | yes | — |
| Add, change or remove the resources of a project | yes | yes | yes | yes | yes (their projects) |
| Delete a project | yes | yes | — | yes | — |
Orders, changes and deletions are requests: they wait for the approvals described on Approvals.
An organization's sales rep, key account manager and resource manager have full rights over its resources: the same actions as a super admin on that organization's projects. From the organization's page they also invite the organization's users and lock and unlock them; the sales rep and the resource manager change their roles there too.
On an organization's page, + Invite user sends an invitation with the roles. While Settings → Customer → Customers → New users ("users can be added before they are invited") is on, + Add user is there too: it records the user (name, e-mail, phone, city) without a sign-in, and the user's row then has Invite, which sends the invitation with the roles when the time comes. Switching the setting off removes adding, not inviting.
Deleting a project is asked for by an organization admin, the organization's sales rep, a resource manager or a super admin. A key account manager and a project admin manage resources, not the project itself, and cannot delete it.
The sales rep and the key account manager see the resource manager's dashboard, for the organizations they are set on and their projects.
At least one active person per role¶
Every role always has at least one active platform user (one who accepted the invitation and can sign in). The portal refuses a change of roles, a lock or an archive that would leave a role without one.
Super admins¶
Super admins. A super admin has every right whatever roles are ticked for them. The roles ticked decide which approvals and notices come to them: a super admin without the resource manager role is not asked to approve as a resource manager (the request is not in "Waiting for me" and no e-mail comes), but may still approve. Nobody is bound to being the first user: every super admin's roles can be edited, their own included.
Giving or taking the super admin role needs other super admins to agree. A super admin ticks or unticks the SA (super admin) box in a platform user's row in Administration → Users → Platform; that opens a request:
- the number of super admins who must agree is fixed when the request is made, from the number of active super admins then (the table below); the super admin who asks counts as one of them;
- every super admin, and the person concerned, is told by e-mail;
- nobody takes the role from themselves, and the person whose role is taken away cannot confirm it;
- the request lapses after 48 hours, and one refusal ends it, even when another super admin's confirmation arrives at the same moment; the role then stays as it was;
- the role is given or taken only once enough super admins have agreed. Giving it is therefore not instant either;
- the portal never takes the role from the last super admin.
| Active super admins | Must agree |
|---|---|
| 1 | 1 (the one asking: done at once) |
| 2 | 2 |
| 3 | 2 |
| 4 or more | 3 |
The requests waiting are shown on top of Administration → Users → Platform with who has confirmed, and Confirm / Decline buttons for those who decide.
Taking the super admin role away from a super admin, B, as asked by another super admin, A:
stateDiagram-v2
[*] --> Requested: super admin A unticks "Super admin" of B
Requested --> Done: enough super admins agreed (≤ 48 h), A counting as one
Requested --> Declined: one of them declines
Requested --> Expired: 48 hours passed
Done --> [*]: B keeps the other roles ticked
Declined --> [*]: B stays a super admin
Expired --> [*]: B stays a super adminstateDiagram-v2
[*] --> Requested: super admin A unticks "Super admin" of B
Requested --> Done: enough super admins agreed (≤ 48 h), A counting as one
Requested --> Declined: one of them declines
Requested --> Expired: 48 hours passed
Done --> [*]: B keeps the other roles ticked
Declined --> [*]: B stays a super admin
Expired --> [*]: B stays a super admin
Acting as a user. A super admin can see the portal exactly as another user sees it: Act as at the top of the dashboard, next to the greeting, lists every user who is not archived. While acting, a banner names the user and Stop acting ends it. Acting is read only: every action can be opened and sent, but nothing is carried out or saved ("Acting as a user is read-only — nothing was changed").
Organizations and their platform users¶
An organization is a legal entity with its country and tax ID (one organization per tax ID in a country; in Kazakhstan the IIN or BIN). Its type is cloud client or corporate; only corporate organizations order corporate projects and the corporate network.
When a resource manager approves a registered organization, they assign its platform users: a resource manager and a support engineer (always required), a sales rep (required for cloud organizations) and a key account manager (optional; cloud organizations only).
- On the organization (Edit organization): the sales rep and the key account manager.
- On the project: the resource manager and the support engineer (the support engineer in Edit project). A project without its own takes the organization's; with neither, any resource manager or support engineer may act.
Once an organization exists, its type, country, tax ID and legal name are fixed. Edit organization changes its short name (only while it has no projects), its sales rep and key account manager, and its notes.
A corporate organization may have a sales rep (optional), who must have an e-mail of a corporate domain (Settings → Customer → Customers); it has no key account manager. A corporate organization may have no users of its own: platform users of a corporate e-mail domain can act as its users. A platform user can be a corporate project's admin, and can be made the organization admin of a corporate organization (Edit organization).
flowchart TB
subgraph cloud ["Cloud client organization, e.g. acme"]
c_sr[Sales rep — required]
c_kam[Key account manager — optional]
end
subgraph corp ["Corporate organization"]
k_sr[Sales rep — optional,<br/>an e-mail of a corporate domain]
k_none[No key account manager,<br/>its admin and users may be platform users<br/>of a corporate e-mail domain]
end
t["Each project: resource manager and support engineer,<br/>its own or the organization's"]
cloud --> t
corp --> tflowchart TB
subgraph cloud ["Cloud client organization, e.g. acme"]
c_sr[Sales rep — required]
c_kam[Key account manager — optional]
end
subgraph corp ["Corporate organization"]
k_sr[Sales rep — optional,<br/>an e-mail of a corporate domain]
k_none[No key account manager,<br/>its admin and users may be platform users<br/>of a corporate e-mail domain]
end
t["Each project: resource manager and support engineer,<br/>its own or the organization's"]
cloud --> t
corp --> t
The organization page has Edit, Archive, Unarchive and + Project in its details. An organization can be archived only when all its projects are archived. Archiving it archives its users too: they cannot sign in, lose their roles and their open invitations. Bringing the organization back does not bring its users back.
A project can be moved to another organization (Edit project → Move to another); the move waits for approval (see Approvals).
Organization users are invited by the organization admin, the organization's sales rep or key account manager, a resource manager or a super admin, or register themselves (see Registering a new organization). A project admin can invite project users to their project. Every project of an organization with users has a project admin; when one is missing, an organization user is made its project admin (the organization admin first).
Every user has a city, typed in (required in every form that creates or edits a user), and a mobile number in international format, starting with "+". A super admin completes a user who has not accepted an invitation yet — e-mail, full name, mobile, city — and sets their roles (organization admin, read only, project admin of chosen projects) from Administration → Users → Organizations.
Users lists¶
Super admins see every user in Administration → Users, with two tabs: Platform and Organizations. An organization admin sees the users of the organization in Organization → Users. Each list shows the e-mail, name, state (active, blocked, invited, inactive, archived) and roles; for organization users also the organization and the projects. In Administration → Users the archived button adds the archived users.
Invite sends an invitation with the roles. Inviting a platform user with the super admin role asks for that role the same way as changing someone's roles: the other roles are given with the invitation, and the super admin role only once enough super admins agree (at once when there is only one super admin). The technical administration pages cannot change anyone's roles. Invitations cannot be made or changed on the technical administration pages. Accepting an invitation never makes someone a super admin by itself: the role is asked for and given once enough super admins agree. Only the first super admin, made from the console when the portal is installed, gets the role with the invitation. The technical administration pages show people and invitations but do not change them: a person's roles, e-mail, sign-in and two-factor authentication are changed only on the portal's own pages. Add (super admins, when Settings → Customer → Customers → New users allows it) makes a record without sign-in, to be invited later. On each user:
- Send invitation / Resend invitation invites someone who has not accepted an invitation yet; Invite back returns an archived user, with only the roles given now. A person invited back signs in normally once they accept the invitation. If their account is blocked after the invitation was sent, it stays blocked. An account brought back keeps its two-factor authentication: when the person accepts the invitation, they set a new password and then enter the code from their authenticator app (or use a passkey), as at every sign-in;
- Lock / Unlock stops or restores sign-in and changes nothing else;
- the roles are the checkboxes in the user's row; ticking project admin asks for the projects;
- Archive removes someone: no sign-in, no roles, no open invitation. Users are never deleted: an archived user is kept for the record and the history of the resources. Archiving a super admin takes the super admin role, so it needs the same agreement as taking the role: the person is archived once enough super admins agree (at once when there is only one super admin). The technical administration pages cannot block, archive or delete users.
The portal refuses to lock or archive the last active holder of a platform role (give the role to someone else first). Nobody locks or archives their own account.
The Organizations list shows each organization's tax ID, type, users and projects, the approvals waiting, its sales rep and key account manager, and "registration waiting" for an organization not approved yet.
Read on: Ordering and provisioning, Approvals, Project lifecycle.