Roles

Anthara has two roles: admin and developer. This page lists what each role can do.

The two roles

Role	Who gets it	What it can do
`admin`	The first admin, created when Anthara is installed.	Everything a developer can do, plus the admin-only areas below.
`developer`	Everyone who joins through an invitation.	Everything that is not admin-only.

What only an admin can do

Area	Where in the web app
Invite members and revoke invitations	Members
Register models, set tool rules, set data protection, read logs and usage	Every page under Govern
Add, edit, and remove connection apps	Connections, then Manage Apps
Create and delete memory graphs, and delete facts from organization memory	Memory
Turn the workflow LLM gateway on or off	The Admin page
Approve a fix proposed in a Microsoft Teams card	Microsoft Teams

The sidebar hides the Govern section from developers.

What every member can do

Developers and admins can both do the following:

Import repositories and run assessments.
Create, edit, and delete AI Coding Standards packs and rules.
Apply packs to repositories.
Connect their own account to an app on the Connections page.
Create, edit, run, and delete agentic workflows.

Repositories and the dashboard are scoped to the person who imported the repositories. One member doesn’t see another member’s repositories.

How the first admin is created

The installer creates one admin from an email address that is set at install time. That person signs in with a provider that reports the same address.

There is no screen and no API endpoint that changes a member’s role. To add another admin, ask whoever administers your deployment.

Role names you might see

The web app has display names for four roles: Admin, Developer, Lead Engineer, and Compliance Officer. The API defines only admin and developer. No member can be given the other two roles today.