Skip to main content

Operator admin

Runs the operator’s own instance. Decides which organisations exist, who is seated in each, and what a role is allowed to reach, so a new event can be stood up without anybody being handed access nobody chose to give them.

Persona
Operator admin
Side
Internal Works for the organisation running the events.
Reference
operator-admin

Where they work

Across the whole instance rather than inside one event: the organisation list, the user list, roles, and the settings every project inherits.

What they are responsible for

That a new event can be stood up quickly, and that nobody ends up with access somebody chose not to give them. They decide which organisations exist, who sits in each, and what a role can reach.

What they can do

  • Create organisations and projects, and set the defaults new projects start from.
  • Invite people, assign them to organisations and projects, and remove them.
  • Define roles and decide what each one can see and change.
  • Turn modules on and off for a project.
  • Sign in as another user to reproduce a problem, where that is permitted and recorded.

What they cannot do

  • Quietly widen their own access without it being visible in the record.
  • Do the event work itself — they set up who can, and hand over.

Journeys they take part in

These are the end-to-end chains of work that name them — the steps they own, and the ones that only affect them.

Journey pages need an operator sign-in to open.

Stand-up

  • Who sees whatStaff and client access is correct at organisation and project level.

Pages that relate to the Operator admin

Was this page helpful?