Team Management

Manage your team members, roles, and access from Settings → Team Members. Cracken uses role-based access control to govern what each team member can do within your tenant.

At a glance

• What it is — Role-based membership management for a tenant: who belongs, what role they hold, and a per-tenant model-training privacy preference.
• When to use it — Invite or remove a team member, change a member's role, or control whether workspace prompts/responses may contribute to model training.
• Inputs — An invitee email and role (Owner, Admin, Member); for the training preference, an improve_model_training boolean.
• Outputs — Tenant membership records with access changes that take effect immediately; for privacy, outbound model requests marked for redaction when training is disabled.
• Related objects — Realms
• Common actions — Invite User, change role, Remove.
• API / tool links — managed in the UI (Settings → Team Members); the supported programmatic surface is MCP.

Inviting team members

Step-by-step instructions

To invite a new member to your tenant:

1. Navigate to Settings → Team Members
2. Click Invite User
3. Enter the email address
4. Assign a role
5. The invitee receives an email with instructions to join

Roles

Roles control what actions a team member can perform. Each member is assigned exactly one role within a tenant.

Role	Capabilities
Owner	Full access — manage team, billing, realms, and all settings
Admin	Manage realms, operations, Tentacles, and configuration
Member	Run operations, view data, and manage artifacts within assigned realms

Changing roles

To change a team member's role:

1. Navigate to Settings → Team Members
2. Find the member in the list
3. Select a new role from the role dropdown
4. The change takes effect immediately

Removing team members

To remove a member from your tenant:

1. Navigate to Settings → Team Members
2. Find the member
3. Click Remove
4. Confirm the removal

Removed members lose access to all tenant data immediately.

User profiles

Each user can update their own profile information:

• Username — display name shown in the UI
• Profile details — personal information and preferences

Profile changes apply across all tenants the user belongs to.

Model Training / Privacy

The Model Training card on Settings → Team Members controls whether the current workspace can contribute prompts and responses to Cracken model improvement.

• Location — Settings → Team Members, the Model Training card.
• Behavior — when the toggle is enabled, workspace prompts and responses may contribute to model improvement. When it is disabled, outbound model requests are marked for message redaction, so request content is not retained for training.
• Plan gating — whether model training is a self-serve toggle depends on how your plan is priced.
  • On self-serve plans that support the toggle (Pro and Team), you can turn it on or off from the card.
  • On usage-priced self-serve tiers (Trial and Starter), the preference stays enabled and read-only — those tiers are priced on prompt contribution — and the card surfaces an Upgrade link. Attempting to change it is rejected with Model training is only configurable on Pro and Team plans.
  • On sales-managed plans (Business, Enterprise, and Custom), model training is off and not configurable: data handling is fixed by your Cracken agreement rather than by a self-serve toggle. The card shows "Model training is governed by your Cracken agreement. Contact support to change it." and never offers an upgrade. Attempting to change it is rejected with the same message.

When training is disabled, outbound model requests are marked for message redaction so request content is not retained for model improvement. The card is read-only unless your plan allows the change and your role can change tenant settings. Exactly one reason is shown, in this order: a sales-managed agreement, then a temporary unavailability note shown when the plan can't be resolved right now, then a plan upgrade prompt, then a workspace-owners-only restriction, then a pending subscription confirmation.

On self-hosted / on-premises deployments the Model Training card is not shown, and model training is off for the deployment — prompts and responses are not used for Cracken model improvement.

Tenant switching

Users can belong to multiple tenants. Switch between tenants using the tenant selector in the sidebar. Each tenant has its own team, realms, and settings — switching tenants changes the entire context.