User management is where you invite teammates to ClarityQ, set what each person can do, and remove access when someone leaves. The page lives under Settings → User Management.
Inviting Users
If your organization signs in with email/password or Google, click Invite User and enter the email address. The invitee receives an email and is added to the organization once they accept.
If your organization uses SSO, the Invite User button is hidden — the SSO Enabled badge appears instead. New teammates are provisioned automatically the first time they sign in through your identity provider.
Roles
Every user has an org-wide role that applies across all workspaces by default. You can override a user’s role per workspace when their responsibilities differ in different parts of the business.
Roles are fixed — they can’t be renamed or customized. If your organization needs a different mix of permissions, assign the closest fit or reach out for guidance.
Context Builder Access
Editing the Context Layer happens in the Context Builder, which requires write access to the Semantic Catalog. By default the following roles can open the Builder, hold the lock, and deploy changes:
- Admin
- Analyst Contributor
Analyst, Integration Manager, and Business User can read the published Context Layer but can’t open the Builder. Per-workspace overrides apply here too — a user can have Builder access in one workspace without having it across the org.
The Builder is also gated by a feature flag per workspace. If the Context Builder entry doesn’t appear in your sidebar even though your role permits it, contact ClarityQ to enable it for the workspace.
Per-Workspace Overrides
When a user’s role differs between workspaces, edit their row and assign a per-workspace role. The User Management table shows +N overrides next to anyone with non-default roles in some workspaces.
Removing Users
Deleting a user removes their access immediately. Their conversation history and private content are permanently deleted — there’s no recovery.
Transferring Their Dashboards
If the user owns public dashboards, the delete dialog tells you how many and offers to transfer ownership to someone else. Pick a person, or choose to delete the dashboards along with the user.
Transfer only covers dashboards the new owner can already access. Anything they can’t access is transferred to you instead, so no dashboard is left without an owner. The dialog spells out the split before you confirm, and the confirmation tells you exactly what moved where.
Everything else still cascades. The user’s conversation history and their private dashboards and items are permanently deleted, whether or not you transfer their public dashboards. This can’t be undone.
API Keys
For programmatic access — for example, calling ClarityQ from your data pipeline — generate an API key under Settings → API. Keys are scoped to a single workspace and inherit the permissions of the user who created them. You can create new keys, see when each was last used, and revoke any key at any time. 
