License Management

Activate your license and assign seats to the people who need them.

License Management in the Identity Portal is where your organization’s license is activated and its seats are assigned. This is the authoritative, organization-level view of what you’re entitled to and how it’s allocated.

Keeping license activation and seat assignment in the Identity Portal rather than in-product is deliberate: entitlement is an organizational fact, not a project setting. The person who owns the commercial relationship needs one authoritative place to see what’s been purchased, how it’s allocated, and when it expires — independent of any single project. Because the portal previews what a license file grants before you commit and records an activation history, there’s a clear, auditable trail of what your organization is entitled to over time.

Activating a license

You activate by providing a license key or by loading a license file — the portal shows a preview of what the file grants before you commit, so you can confirm the edition, seat counts, and expiry are what you expect. Once activated, the license status shows as licensed, along with its details and when it expires, and a license history records what’s been activated over time.

Assigning seats

Licensing is seat-based, and you assign seats to users from your available allocation. Seats come in three classes:

  • Creator — author within purchased modules; may initiate formal reviews. Named or floating.
  • Reviewer — when invited as a deciding participant in a formal review, can approve, reject, and e-sign; project read for context. No authoring or import; cannot initiate reviews. Named or floating.
  • Stakeholder — oversight: project read and comment without authoring; may comment in a review when invited. Cannot approve, reject, or e-sign. Named only (a floating pool cannot be assigned to a Stakeholder).

Reviewers and Stakeholders both read the live project — seats are not gated to “published only.” A named seat is dedicated to one person; a floating seat is drawn from a shared pool at sign-in and released when idle. Managing seats here means you control precisely who consumes a licensed seat — assigning them to active users and reclaiming them when someone no longer needs access.

For the public comparison table, see Pricing — Seats. The in-application view is covered in License management.

Staying ahead of limits

Because the portal shows your seat usage against your allocation and your expiry date plainly, you can plan renewals and capacity before they become urgent. This portal area remains the organization-level control over activation and seat assignment.

Was this helpful?