Screens / Knowledge and setup

Admin: roles and data controls

Say who can do what, bring people in, and show what happens to the account's data.

For: Account owners and admins.

Markdown

3 ways to lay it out

1. Members and roles

Pick it when: The default: who is in, and what each of them can do.

A members table with roles, pending invites below, and an invite button.

Members tableProMembers, their role on each environment, and invites still pending.
Invite membersProInvite people by pasting any list of emails.
Access requestProAsk for a role you don't have on an environment.

Install members and roles

Pro and Premium items need a licence key; free ones install as they are.

2. Role matrix

Pick it when: Deciding what each role may do before assigning anyone to it.

Roles across the top, actions down the side, each cell a dot where allowed.

Role matrixProWhat each role can do, as a matrix.
RACI chipProWho is responsible, accountable, consulted or informed.

Install role matrix

Pro and Premium items need a licence key; free ones install as they are.

3. Data controls page

Pick it when: People ask where their data is and how long it's kept.

Sections for region, retention and the account's data, each with its own action.

Data controlsProHow the data is used, an export, deleting thread history, deleting the account.
Data regionProWhere data lives and is processed, service by service.
Data retentionProHow long each kind of data is kept, and what happens after.
Type to confirmProDeleting is confirmed by typing a name.
SSO setupProSingle sign-on through the identity provider.

Install data controls page

Pro and Premium items need a licence key; free ones install as they are.

Rules that matter most here

A control that can't be used says why
An action your role doesn't allow stays visible and says which role does.
Say what can and can't be undone
Deleting the account or history states what is removed and that it can't be undone, and asks to type the name.
Unknown stays unknown
A region or retention the service can't confirm says so, not a default.

Already covered elsewhere

Builds the whole screen with an agent route and a store: Audit data controls (Premium), with a -claude twin for the Claude Agent SDK.

Brief for a coding agent

Paste this into the agent that builds the screen. The docs MCP server returns the same text from get_screen.

Build admin screens with Candor UI for roles and data controls.
Members: MembersTable with role per environment and pending invites; InviteMembers takes any pasted list of emails; AccessRequest lets a person ask for a role.
Roles: RoleMatrix shows what each role can do; an action your role doesn't allow stays visible and says which role does.
Data: DataControls, DataRegion and DataRetention state facts from the service; if the service can't confirm one, show it as unknown, not as a default.
Deleting history or the account uses TypeToConfirm and says what is removed and that it can't be undone.
Add SsoSetup when the account signs in through an identity provider.
The audit-data-controls block has the routes and store for export and deletion.

Start from the "Members and roles" layout: A members table with roles, pending invites below, and an invite button.
Candor items: members-table (https://candor.themethodic.com/docs/members-table.md), invite-members (https://candor.themethodic.com/docs/invite-members.md), access-request (https://candor.themethodic.com/docs/access-request.md).
Install: npx candor-ui add members-table invite-members access-request
Read each item's docs before using it and take its props from there; don't guess them. Pro and Premium items need the person's licence key, which they add with `npx candor-ui key <key>`; don't ask for it.