Skip to content

Give someone a role

Everyone is a user: they use the models their teams allow. A role adds reach on top, on something specific and, if you like, until a date. Give Finance the cost, a department lead their team, a data protection officer the policies, and nobody more than their job needs. Anyone widening their own access waits for a second admin.

Before you start

  • Organisation admins give any role. Group admins give roles within the teams they run.
  • Some roles are Enterprise: Compliance officer, and roles for service accounts. What Enterprise includes depends on the features your licence includes.

Steps

  1. Open Roles & access and choose Give a role.
  2. Who: a person (or, on the Enterprise edition, a service account), by name or email.
  3. Role: each says in one line what it gives.

    Role On Gives
    Organisation admin The whole organisation Changes everything
    Organisation viewer The whole organisation Sees everything, changes nothing, holds no keys
    Finance The whole organisation Every cost; prices, markups, billing periods, cost exports
    Compliance officer Enterprise The whole organisation Policies, guardrails, risk and evidence; sees what a viewer sees
    Group admin of a team A team That team and every team inside it
    Owner of an agent, application or service account An agent, application or service account Looks after it and its keys or tokens
    Content reader The organisation, a team, an agent or an application Reads what calls sent and got back there, and nothing else
    Permission: Approve budget overrides, Permission: Approve guardrail overrides, Permission: Manage approved destinations The whole organisation That one permission (organisation admins give these)
  4. Choose what it's on: the team, what they'll own, or for a content reader Where. Organisation-wide roles have nothing to choose.

  5. Optionally Until a date and Why. The reason is kept with the role and in the audit log.
  6. Confirm.

Giving Amélie Laurent the Finance role, step by step

Check it worked

Roles & access lists it: who, the role in words with what it's on, Given by, Since and Until. The How filter shows how each role came: set up with the installation, given by an admin, came with making something, or from single sign-on.

Good to know

  • Roles add up. A person holds every power of every role they have, each on what it was given on.
  • Prompts are private by default. Nobody reads what calls sent and got back without Content reader, not even an organisation admin. Every read, and every refused try, is recorded.
  • Giving yourself more access waits for a second admin, and so does giving a service account a role. It appears under Approvals. The sole organisation admin is never stuck: until there's a second one, such changes go ahead, and Home suggests adding one.
  • Add person sets only organisation admin or viewer; give the other roles once someone is added.
  • The last organisation admin can't lose the role.
  • Remove on a row ends a role at once; their teams and everything they did stay.