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
Team management is handled through the Risicare Dashboard:
- Navigate to Settings → Team
- Click "Invite Member"
- Enter email address and select role
- The invited user receives an email to sign up or log in
Dashboard-only management
Team management (inviting, role changes, removal) is available through the dashboard UI. There is no REST API for team operations — use the Settings → Team page.
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.