Skip to main content
GitHub

Admin

Platform administration and team management.

Manage your Risicare organization, projects, and team.

Overview

Organization Structure

Organization
├── Projects
│   ├── Project A (production)
│   │   ├── API Keys
│   │   ├── Settings
│   │   └── Data
│   └── Project B (staging)
│       ├── API Keys
│       ├── Settings
│       └── Data
└── Team
    ├── Owners
    ├── Admins
    ├── Members
    └── Viewers

Roles

Every member of an organization has one role, and it is enforced on every request. See Team for the full permission matrix.

RolePermissions
OwnerEverything an admin can, and give someone the owner role
AdminManage the team, create projects, rename a project, and create and revoke API keys
MemberCreate and change datasets; add scores; pause or delete alert rules
ViewerRead-only access

Quick Actions

Create Project

Owners and admins create projects from the project dropdown in the top nav → New Project. The project's first API key is shown once, in the Project Created dialog. Creating a project needs a sign-in from the last 15 minutes; the dialog does not say why a creation was refused, so if Create Project does nothing, sign out, sign in again and retry.

Invite Team Member

Owners and admins invite teammates from Settings → Team — enter an email address and a role. The first person in a new organization is invited by the Risicare team; there is no self-serve sign-up. See Team.

Create API Key

Owners and admins create keys from the dashboard's Settings → API Keys page. A key is shown once, when it is created, and creating one needs a recent sign-in. There is no Bearer rsk-... path for key management. See API Keys.

Billing

Coming Soon

Risicare is in private beta and is free for all participants. Self-service billing — subscription management, invoice downloads, and plan upgrades — ships after beta. During beta, contact us at support@risicare.ai for usage questions or limit increases.

Usage Limits

Coming Soon

Usage tiers (Free / Pro / Enterprise) are not yet enforced during beta. All beta projects share a single shared-resource quota. Per-project plan tiers and metered billing ship after beta.

Next Steps