Skip to content

Roles and the workflow

Who does what in Claugine, from a new organization to an archived project. Each step is described in detail on its own page:

Page What it covers
Roles and organizations Every role, super admins and the 48-hour removal, organizations and their platform users, users lists
Ordering and provisioning Registering an organization, ordering, approval, automatic provisioning, every e-mail sent
Approvals Who approves what, the matrix of who can do what, registration requests, changes, project moves and deletion
Project lifecycle Statuses, the one automatic change, expiration notices

The whole journey

From a person registering an organization to a running project, in three steps: the organization, its project and the project's life.

1. The organization

flowchart TB
  REG[Person registers the organization<br/>legal name, country, tax ID, contact] --> CHK{Checked}
  CHK -- automated --> NO[Nothing made, log only]
  CHK --> CONF[Confirms the e-mail<br/>within 48 hours]
  CONF --> ORM{Resource manager approves,<br/>assigns platform users}
  ORM --> OSR{Sales rep approves<br/>cloud, when sales approval is on}
  OSR --> OREG[Registered:<br/>org admin signs in]
  ORM -- refuses --> OX[Deleted, person told why,<br/>the log keeps it]

2. The project, ordered by the organization's admin once it is registered:

flowchart TB
  ORD[Order: resources, connections,<br/>project admin, notes — a POC] --> TRM{Resource manager<br/>names, places, confirms}
  TRM --> TSR{Sales rep<br/>cloud, when on}
  TSR --> APP[Last approval]
  TRM -- rejects --> TX[Rejected, org admins told]
  APP --> PROV[Provisioning starts by itself]
  PROV --> DEP[Deployment on the platform]
  DEP -- failed --> AGAIN[Provision again] --> DEP
  DEP --> MAIL[Access details to the project admin<br/>and the organization admins,<br/>then the platform users]

3. The project's life, from the moment its access details are sent:

flowchart LR
  OK[ok] --> PA[paused] --> SU[suspended] --> SA[saved] --> AR[archived]

Two kinds of users

Kind Who Roles
Platform users the provider's staff super admin, resource manager, support engineer, sales manager (sales rep), key account manager
Organization users a client organization's people organization admin, project admin, project user, read only

One e-mail is one account: a platform user or an organization user. In a corporate organization, a platform user can also be its organization admin or a project admin. Every user uses two-factor authentication. Every platform role always has at least one active platform user. The sales rep and the key account manager are set on the organization, the resource manager and the support engineer on the project.

Guides per role