Team
Manage team members and roles.
Manage who has access to your Risicare organization.
Roles
Roles during beta
Beta deployments operate in a single-role model: every signed-up user is an Owner of their own organization. The role descriptions and permission matrix below describe the planned post-beta model. Per-role enforcement ships after beta.
| Role | Description (planned) |
|---|---|
| Owner | Full access; can delete org |
| Admin | Manage projects, keys, and team members |
| Member | Read/write data, create evaluations and fixes |
| Viewer | Read-only access to all data |
Permission Matrix (planned)
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View traces | Yes | Yes | Yes | Yes |
| Create evaluations | Yes | Yes | Yes | No |
| Manage fixes | Yes | Yes | Yes | No |
| Create API keys | Yes | Yes | No | No |
| Manage team | Yes | Yes | No | No |
| Manage projects | Yes | Yes | No | No |
| Delete org | Yes | No | No | No |
Managing Team Members
There is no way to add a team member
Inviting members is not built. Nothing in the product creates an invitation — the dashboard's Settings → Team page renders a "Coming soon" placeholder with no invite flow, and no API or server action inserts an invite. Every account therefore self-provisions as the sole Owner of its own organization, which is why the role matrix above never comes into play.
Two team endpoints do exist and work, but they can only act on a member who is already present — which today never happens:
| Endpoint | Purpose |
|---|---|
DELETE /api/v1/team/members/{user_id} | Remove a member (revokes their org access immediately) |
PATCH /api/v1/team/members/{user_id} | Change a member's role, never above the caller's own |
Both require an owner or admin role. There is no endpoint to list or
invite members. During beta, control project access by issuing and revoking
per-project API keys.
Authentication
OAuth Providers
Risicare supports:
- GitHub
SSO (Enterprise)
Coming Soon
Single Sign-On (SAML 2.0, custom identity providers, just-in-time provisioning) is on the post-beta roadmap. During beta, OAuth via Google or GitHub is the only authentication method. Contact us at hello@risicare.ai if SSO is required for your beta evaluation.
Team Limits
Coming Soon
Per-plan team-size limits ship with the post-beta billing system. During beta, all organizations share a single resource quota — there is no team-size cap.