Skip to Content
Learn by roleAdministrator

Administrator guide

As an Administrator, you manage organization access and configuration. Governance, compliance, and business decisions still require the appropriate accountable owner.

Establish ownership

Identify who owns access, applications, keys, governance, privacy, evidence, billing, and support before changing the settings they rely on.

Keep enough active administrators to support recovery and separation of duties.

Configure access

  1. Review the member’s job responsibilities.
  2. Assign the standard role with the required access.
  3. Add application-specific responsibilities when needed.
  4. Verify the member can reach the intended records.
  5. Remove access when responsibilities change.

Role preview shows another role’s layout, not its actual access. Ask the member to sign in and confirm access to the intended records.

Configure applications

Use separate applications and keys when environments need independent access or evidence records. Issued keys belong in an approved secret manager.

After setup, ask the application owner to send a representative test session and confirm reporting health.

Review organization controls

Confirm each setting with its accountable owner before saving it. Important areas include:

  • sign-in and recovery;
  • application keys and package access;
  • sensitive-data handling and retention;
  • governance policies and alert thresholds;
  • human-review routing and callbacks;
  • audit engagements and exports; and
  • subscription, budgets, and value assumptions.

Operate safely

  • Review access and key status on the organization’s schedule.
  • Test recovery and callback paths with non-production data.
  • Record changes that affect evidence or authorization.
  • Use Inbox for assigned follow-up and decisions.
  • Escalate security and privacy events through approved channels.
Last updated on