What a group leader sees about their own members — who has lost AI access after a security review, and who is waiting to get it back.

My team answers one question for a group leader: has anyone on my team lost AI access after a security review, and are they waiting on an administrator to give it back. It is the only page in the product written for somebody who runs a team but administers nothing.

What do I need?

Licence: Enterprise
Role: normal_useradmin_userviewer

Prerequisites

You lead at least one tenant group — you own it, you hold the leader role on your membership row, or you are the superadmin.
The installed licence carries risk.llm_review. Everything this page shows is LLM-review state, so it is gated on that tier.

The page carries no role requirement at all. A leader is normally an ordinary user, and demanding an administrator role would either exclude every real leader or hand them the fleet-wide admin surface. Membership is the authorization: you see exactly the groups you lead, and a member of a group you do not lead is indistinguishable from a user who does not exist.

Note

The sidebar entry is not decided by your role. The shell asks the gateway which groups you lead and shows My team only when the answer is at least one — so the item simply is not there for everybody else, and leading nothing is an empty answer rather than a refusal.

Screenshot pendingMy team with one collapsible group section per led group and a member table showing AI access, unlock requests and recent verdicts/assets/screenshots/my-team@0.4.png

Become a leader

Leadership is one of two relations, and only one of them can be set from the dashboard today.

Relation	How it is set
Group owner	The account that created the group is stamped as its owner. Creating a group on Tenant groups makes you its leader
`leader` on a membership row	Set through the group-members API: `POST /admin/tenant-groups/:id/members` with the role, or `PATCH /admin/tenant-groups/:id/members/:tenantId` to promote an existing member
Superadmin	Leads every group, whoever owns it

Danger

The Manage Members dialog on Tenant groups offers Member and Admin, but the gateway accepts only member and leader — sending Admin is rejected as an invalid role. There is therefore no way to promote an existing member to leader from the dashboard; use the group-members API, or make the intended leader the group's owner by having them create it.

Read the overview

Open the page

Select My team at the top of the sidebar.

Every group you lead is a collapsible section. Its header carries the member count, plus an n locked tag and an n pending unlock tag when either is above zero. The first group is open; the rest start closed.

Scan the member table

Read the row per member.

AI access reads Active or Locked; Since carries the time of a lock; Unlock request shows Pending when that person has asked for it back; Recent verdicts shows their last three verdicts as tags; Detections (7d) counts their detections over the last seven days.

Narrow a large team

Use Search groups to filter by group name, and Status to show All members, Locked, Active or Pending unlock.

Both are applied in the browser. A group left with no matching member drops out, and every remaining group opens so nothing is hidden behind a collapsed header.

Note

The overview is deliberately unpaginated: it is one screen about one team. A leader with a group large enough to need paging is an administrator, and belongs on Risk analysis instead.

Look at one member's history

Open the member

Select a row.

Reviews for {member} lists their reviews, newest first, ten to a page — Each row is one deep analysis of repeated jailbreak or prompt-injection attempts.

Read the outcome

Each row carries When, Status, Verdict, Score, Checks and Attempts.

There is no detail drawer, and that is not an omission: the gateway does not send the reasoning to this page, so there is nothing further to open.

Warning

Outcomes only. The analyst's written reasoning quotes what your colleague typed, so it stays with administrators. You see what was decided, not the messages behind it. The gateway enforces that with an allowlist on the response, not with a filter in the browser.

What a leader cannot do here

This page reads. It has no action on it at all.

You cannot unlock a member. Only an administrator can, on Risk analysis.
You cannot approve or deny an unlock request. Pending tells you one exists and that it is waiting on somebody else.
You cannot read the analyst's reasoning or the evidence it cited.
You cannot see a member of a group you do not lead. Requesting one answers 404, exactly as an unknown account does, so the endpoint cannot be used to enumerate other teams.

Fields reference

Group header

Element	Shows
Group name	The tenant group you lead
n members	How many accounts are in it
n locked	Members whose AI access is suspended. Hidden at zero
n pending unlock	Members with an open unlock request. Hidden at zero

Member table

Column	Shows
Member	The account's username, or its id when it has no name
AI access	Active or Locked
Since	When the lock was placed, or an em dash
Unlock request	Pending, or an em dash
Recent verdicts	The member's last three verdicts, or None
Detections (7d)	Their detections over the last seven days

Reviews dialog

Column	Shows
When	When the review was opened
Status	Pending, Analysing, Completed, Failed or Timed out
Verdict	Warn, Lock, Clear or No verdict
Score	The analyst's risk score
Checks	Verified or Unverified — whether the analyst's own verification passed
Attempts	How many attempts triggered the review

Verify

Sign in as the leader. My team appears at the top of the sidebar and lists the groups you lead. If it is absent, you lead none.
The member count in a group header matches the membership on Tenant groups.
Have an administrator lock a member on Risk analysis. Within a refresh, that member's AI access reads Locked and Since carries the time.
Ask the member to request an unlock. Their Unlock request column becomes Pending, and the administrator sees the same request in their queue. The user's request writes UNLOCK_REQUESTED to the audit trail.
Reading this page writes no event of its own, matching every other read endpoint in the gateway. The lock and unlock events you can see the effects of are written by the administrator side.

If it fails

You do not lead a team yet — An administrator can make you the leader of a tenant group; this page then shows that group here. This is the correct answer for a non-leader, not an error, and it is why the endpoint never returns 403.
The page is missing from the sidebar although you own a group — the licence does not carry risk.llm_review, which gates the whole page. See Licence.
A toast naming FEATURE_NOT_LICENSED when you type the address directly — the same cause.
This group has no members yet. — the group exists and is empty. Add members on Tenant groups.
No member matches the search or filter. — the group-name search or the status filter excluded everything. Clear them.
No reviews for this person yet. — nothing has triggered a deep review for that member. It is the normal state.
You were made a leader but the page still shows nothing — check that the membership row actually carries leader. The dashboard's Admin option does not set it, and the gateway rejects that value outright.

Next steps

Tenant groups — where groups and their membership are managed, and where the leader-role caveat above applies.
Risk analysis — the administrator's side: the reasoning behind a verdict, and the only place a lock can be lifted.

My team