Skip to content

Settings — Access Levels

The Settings ▸ Access Levels page is where admins control the platform’s role + permission model for their tenant. Two sections: a reference card that documents what each role can do, and a team list with per-user role + HR-add-on controls.

Owner-only actions are also gated server-side, so any change here respects the same permission rules as the rest of the platform — admins cannot self-promote past their permissions, and last-Owner demotion is blocked.

Settings Access Levels — Acme Financial Group demo tenant

PageHeader with the title Access Levels and a one-line description.

Section header “What can each Access Level do?” followed by a 2-column grid with one card per role:

  • Role icon + name
  • Capability list (checkmarks for what the role can do)
  • Capability list (red x for what the role cannot)

The card is informational only — it documents the platform’s seeded permission catalogue. Per-action overrides (when needed) are configured server-side.

Section header “Team” followed by a per-user row:

  • Avatar + display name + email
  • Role dropdown — current role, with disable rules for lockout protection
  • HR add-on toggle — only on Manager / General users

Changes save inline; no batch-save button.

Athenty’s role model is fixed in code. The four roles ship with documented default capabilities:

RoleCapabilities
OwnerFull platform + billing + dangerous deletions
AdminSettings + team management; no billing
ManagerMatter-responsible work; team management within reporting line
GeneralDay-to-day verifications and envelopes

The reference card on this page is generated from the same permission catalogue that gates server-side authorization, so it stays in sync with the actual enforcement.

A boolean per-user flag that grants HR access (employment data, compensation, health, IDV review under Settings ▸ Team) without elevating to Admin. Use cases:

  • HR specialists who need people-data but not platform-admin powers
  • Office managers who handle onboarding/offboarding records
  • Compliance staff who track credentials + IDV status

Add-on toggle behaviour:

  • Visible only on Manager + General users
  • Settable by any Owner / Admin
  • Persists independently of the role; promoting later doesn’t toggle it
  • Audit-logged separately as user.hr_role_granted / _revoked

The platform refuses two transitions to prevent admin lockout:

Refused transitionWhy
Demote yourself from OwnerPrevents accidental self-lockout
Demote the last Owner (any actor)Tenant must have ≥ 1 Owner

To rotate ownership, promote a new Owner first, then demote the old one.

RoleViewSet rolesToggle HRDemote Owner
Owner✓ (any → any)✓ (not last)
Admin✓ (not Owner)
Manager
General
Viewer

/settings/access-levels is admin-only via RoleGuard.

ActionEvent
Role changeuser.role_updated (with old + new role)
HR grantuser.hr_role_granted
HR revokeuser.hr_role_revoked

Events surface in Settings ▸ Audit Log.

SymptomMost likely causeFix
Cannot demoteTarget is last OwnerPromote another Owner first
Owner role disabled in dropdownActing role is AdminHave an Owner make the change
HR toggle missingTarget is Owner / AdminThey already have HR via role
Role change not applyingUser session cachedUser signs out + back in
Capability missing on the referencePlan tier exclusionVerify in Settings ▸ Billing