Eniyan Docs

Team, roles & access

The Team & Access page at /dashboard/team is where admins manage who can open your Eniyan dashboard and what they can do: invite members, assign one of seven org roles, place people on the seniority ladder, and deactivate accounts without losing their history. Non-admins see the same page read-only.

Inviting a member

  1. On /dashboard/team, click + Invite Member (admins only). The Invite Team Member dialog opens.
  2. Fill in Email address, pick a Role from the role cards (Developer is preselected), and set a Temporary password of at least 8 characters. They’ll use this email and password to log in — share the password securely, and have them change it after first login.
  3. Click Send Invite (or Cancel). The new member appears in the team table immediately.

Eniyan also emails the new member a verification link — they must confirm it before they can be approved as a verified operator. Until then their row shows an Email pending badge. Once they apply for operator status the badge becomes Operator pending with a Review → link to the approvals queue on /dashboard/operators; approved operators show Operator ✓.

The seven org roles

Role guide cards at the top of the page describe each role; the same cards appear as the Role picker inside the invite dialog:

  • Admin — Full access — manage team, API keys, and all resources
  • Developer — Create sessions, issue credentials, manage API keys
  • Viewer — Read-only access to dashboard and analytics
  • Sustainability — Manage the org’s carbon footprint score and offset submissions
  • Role Admin — Create and edit the org’s agent role definitions
  • Role Manager — Assign agent roles and run recertification, optionally scoped to specific operators
  • Agent Approver — Approve or reject agent scope-exception requests

The last three are the agent-governance trio — see Agent RBAC: admin roles for what each one can and cannot touch.

Changing a member’s role

As an admin, click any member’s role badge in the Role column of the team table, pick the new role from the dropdown, and it applies immediately (a Role updated toast confirms). Your own row is marked (you) — you cannot change your own role or deactivate yourself.

Deactivating and reactivating

Each row’s Status column shows Active or Inactive. Admins see a Deactivate action on active members; confirming the dialog removes their dashboard access, but their history is preserved and an inactive member’s row keeps a Reactivate action to restore access later. Deactivation is how you offboard — nothing on this page permanently deletes a member.

Org chart — seniority levels

The Org chart — seniority levels card below the team table holds your org’s ranked ladder. Higher rank = more senior; agent access rules can require a minimum level or restrict below one, and members without a level never pass a seniority gate. Admins add rungs with the Level name and Rank fields plus Add level, then place each member using the Level dropdown in the team table (No level clears it). Deleting a level (the Delete action on the card) drops its holders off the ladder — they fail seniority gates until re-leveled.

Personal accounts: one seat

The Personal plan is strictly single-seat — the dashboard is yours alone, so this is where the rule bites: inviting a teammate requires a Team, Business, or Scale plan. Personal orgs that added a second member before the one-seat rule keep that member’s access; only new invites are blocked. Everything else on this page — roles, the seniority ladder, deactivation — works the same on every plan.