Team
Invite teammates, assign roles, and remove access.
Risicare is in closed beta
Access is by invitation. The link in your invitation email opens the sign-in page — start there rather than from the addresses on this page. The link does not sign you in by itself: sign in with the same email address the invitation was sent to, or it is not accepted. If a step here does not work for you during the beta, write to support@risicare.ai.
Everyone in a Risicare organization has one of four roles: owner, admin, member or viewer. Owners and admins manage the team from Settings → Team in the dashboard.
How People Join
Access is by invitation
There is no self-serve sign-up, and signing in without an invitation is refused. The first person in a new organization is set up by the Risicare team, who email them an owner invitation. Everyone after that is invited from Settings → Team.
- An owner or admin opens Settings → Team, enters the teammate's email address and role, and sends the invitation.
- The invitation email links to the sign-in page. The teammate signs in with GitHub, using the account whose email matches the invitation — the public email on their GitHub profile if one is set, otherwise their primary email. That match is what accepts the invitation.
- The teammate becomes a member of the organization with the invited role.
- The invitation is recorded whether or not the email arrives. If the email is lost, ask an owner or admin to resend it from Settings → Team — during the beta that link is how you reach the sign-in page.
- Already signed in with a different account? The sign-in page shows who is signed in and lets you sign in again with the invited account.
- Already a member of another organization? Signing in keeps you in that one. The sign-in page lists your organizations, so you can open the new one from there.
- Invitations expire after 14 days. Invite the person again to issue a new one.
- Joining an organization that already has a project creates no API key for you. Owners and admins create one in Settings → API Keys; a member asks an owner or admin for a key — see API Keys.
Roles
| Role | What it can do |
|---|---|
| Owner | Everything an admin can, and give someone the owner role |
| Admin | Manage the team, create projects, rename a project, and create and revoke API keys |
| Member | Create and change datasets, add scores, and pause or delete alert rules |
| Viewer | Read-only access to traces, sessions, agents and other data |
Permission Matrix
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View traces, sessions and agents | Yes | Yes | Yes | Yes |
| Create and revoke API keys | Yes | Yes | No | No |
| Create and change datasets; add scores; pause or delete alert rules | Yes | Yes | Yes | No |
| Create projects | Yes | Yes | No | No |
| Rename a project | Yes | Yes | No | No |
| See and manage the team | Yes | Yes | No | No |
| Invite or promote someone to owner | Yes | No | No | No |
Roles apply to API keys too: a key acts with the role its creator holds in the organization. Running evaluations and requesting diagnoses are held for the beta for every role. There is no way to delete an organization in the product — see Deleting your account or organization.
Managing the Team
Only owners and admins see the team on Settings → Team; members and viewers see a note that only owners and admins can manage it.
-
Invite — enter an email address and a role. You can invite up to your own role, so only an owner can invite an owner.
-
Delivery status — each invitation shows what happened to its email:
Status Meaning Email sent Handed to the mail provider. That is not proof it arrived Email failed The provider refused it; the reason is shown Email not sent No email went out — for example, email is not configured Email may not have been sent The outcome is not known -
Resend — at most once a minute; the button shows how long to wait.
-
Revoke — a pending invitation stops working. No email tells the person it was revoked.
-
Change role — up to your own role.
-
Remove — the person loses access to every project in the organization immediately, and API keys they created in the organization stop working. Allow up to a minute for a key that is already sending spans.
-
The last owner of an organization cannot be demoted or removed.
Team management and API keys
Listing members and creating, resending or revoking invitations require someone signed in to the dashboard with the owner or admin role; requests authenticated with an API key are refused. Changing a member's role and removing a member are different: they also accept an API key whose creator is an owner or admin, so guard such keys as you would any admin credential. Manage the team from Settings → Team.
Authentication
Sign-in
Sign in to app.risicare.ai with GitHub. Google sign-in is not enabled during the beta.
Some actions need a recent sign-in — within the last 15 minutes: creating or revoking an API key, and creating a project. If you are asked to re-authenticate, sign in again and retry.
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, GitHub sign-in is the only authentication method. Contact us at support@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.