Set customer seat limits. Track your own plan capacity.
Each license has a seat limit. Your plan counts distinct users per organization and project: one person on two licenses uses two seats but counts once.
See organization-user pricingSet the terms of each company’s access.
Premium for a team. A course library for a department. Choose the features, seats and dates for each agreement.
One customer. Explicit terms of access.
A License connects an Organization to included features, seat capacity and access dates. Each company can hold several licenses.
This is an access record, not a signed contract or invoice. Keep agreements and payments in your chosen systems.
See how feature access worksKnow when the agreement can provide access.
Set a start date and optional end date. Access applies while the license is valid; revocation preserves its history.
- Scheduled
- The validity window has not started.
- Active
- Within the validity window and not revoked.
- Expired
- The configured end has passed.
- Revoked
- Explicitly withdrawn; history remains.
These states are not a mandatory sequence. You can revoke a license before its planned end.
A seat records the allocation. Access follows the agreement.
Assign seats to existing users. Your backend checks current access when they use a feature.
Seats can outlast an expired license. Releasing one seat may leave access through another valid license.
Read how access is decidedBring the team in after the deal.
Assign users from a roster, or offer invitations and codes. Customer admins handle onboarding within the features and seats you agreed.
Hand everyday access to the customerTurn the next agreement into access people can use.
Start with one company, one feature and one user. Then bring in the team.