Skip to main content

Overview

Entitlements decide whether a user or organization can use a capability, and how much of it. They are separate from roles: a role controls what someone may do to a resource, while an entitlement controls whether the capability is available at all. Every entitlement is one of three kinds: Entitlements are evaluated on every request, so changes take effect without restarting anything.

Where To Make A Change

How A Value Is Decided

“Most permissive” depends on the kind of entitlement: Three consequences matter in practice:
  • A group cannot take something away. If base or a plan group turns a feature On, another group setting it Off has no effect. Use an override, or change the group that grants it.
  • An override can lower or raise a value, but never above the license. An override is the final word among groups and overrides, but the license and tenant subscription still cap it.
  • Some keys follow the organization. Keys marked Org decides in the tables below resolve from the organization when the user works in an organization-owned project, and from the user otherwise.

Groups

Open Administration → Groups (/admin/~/groups). The table shows each group’s name and key, who it applies to, who manages it, its active member count, and a summary of the values it sets.

Group Types

You can edit the values of every group, including base and plan groups. Billing never overwrites your edits to a plan group.
Editing base changes the default for every user in the deployment who does not have a more permissive group or an override.

Create A Group

  1. Select New group.
  2. Enter a Key: lowercase letters, digits, ., _, or -. The key cannot be changed or reused, even after archiving.
  3. Enter a Name and an optional Description.
  4. Choose Applies to: Users or Organizations. This cannot be changed later. Organization groups can hold only the keys marked for organizations in the tables below.
  5. Select Create. The group opens for editing.

Edit A Group

Select a group row to open it. The editor has three sections, Limits, Options, and Features, and every row shows:
  • The key, its description, and its catalog default.
  • Effective Value: what members receive from this group combined with base, labeled Set on group, From base, or Catalog default. Other groups a member belongs to are not included in this preview.
  • Group Setting: Catalog default leaves the key unset in this group. For limits, choose Custom limit and enter a number, or choose Unlimited. For features, choose On or Off.
Select Save group to apply the changes. Archiving an admin group stops all of its memberships from counting.

Memberships

Members are added from the member’s own page rather than from the group: open a user or organization, go to its Entitlements tab, choose the group, optionally set an end date, and select Add admin membership. The group’s Members section lists everyone in it. A subject can belong to the same group through several sources at once. Each source is added and removed independently, so removing an admin grant does not remove a billing membership in the same group. Davinci warns users before trials and timed admin grants end.

What You Can Set

The tables below list every key that a group or override can set. The Notes column uses these labels:
  • Users, Orgs, or Both: which kind of group or override can set the key.
  • Licensed: also requires the deployment license or tenant subscription to include it.
  • Full seat: always Off for read-only seats.
  • Org decides: resolves from the organization in organization-owned projects.
  • Self-service: users can opt in from their own settings when no group or override sets the key.

Limits

Options

Product Features

Access And Security Features

The per-user auth.personalAccessTokens value does not override the deployment-wide Enable API Keys switch in System Settings. Both must allow access.

AI And Usage Features

Ownership Features

Rollout Features

Rollout features are temporary switches for features that are still being released. When no group or override sets a rollout feature, the user’s own setting decides. Without one, the deployment’s feature flag in System Settings decides, and then the catalog default. Users can change their own setting only for self-service features. Users who connect Onshape also get rollout.cadObjects.

License-Only Keys

Some keys come only from the deployment license or tenant subscription and cannot be set by groups or overrides. They appear as License only on the Entitlements tab:
  • Seat caps (deployment.seats.full.max, deployment.seats.readonly.max), organization caps (deployment.orgs.max, tenant.orgs.max), and runner caps.
  • Sign-in methods (auth.sso, auth.ldap, auth.oauth, auth.scim).
  • Deployment capabilities such as cloud storage, multi-replica high availability, offline licensing, and shared included usage.
To change a tenant’s seat or organization caps, edit its tenant subscription.

The Entitlements Tab

Each user and organization has an Entitlements tab in its detail view. It lists every limit, option, and feature with its effective value and the source that decided it: When the source is Platform, the reason explains why:

Overrides

Use the Override control on any row that is not License only:
  • Limits: enter a number, or leave the field empty for Unlimited.
  • Features: choose On or Off.
  • Options: choose an LLM profile.
Select Clear to remove an override and return the key to its group or catalog value. Every override change is recorded in the audit log.

Seats

Every active user holds a Full or Read-only seat. Read-only seats can view, download, export, comment, and use Task Cards, but cannot edit, use the AI agent, or run jobs, even on projects they own. Seats count against the license and tenant seat caps. Moving a user into a seat type that is at capacity fails; moving a user out of a seat type always succeeds. When the license is expired or invalid, every user’s effective seat becomes read-only until the license is fixed, while their stored seat type is kept.

Trials

Grant a user a trial of any user group by choosing the group, a duration from 1 to 365 days (14 by default), and an optional one-time credit balance in USD. When the trial ends, the user falls back to their plan or base, and keeps any unspent trial balance. Select Revoke trial to end an active trial early. Tenant trials are managed on the tenant’s subscription.

Common Tasks

Troubleshooting