Skip to content

How licensing works ​

Two separate controls decide whether a person can open an HCM application. A person needs both.

ControlSet byDecidesWhere
LicencePlatform administrator (the vendor)What your organization has bought: edition, term, features, limitsPlatform administration console
AccessYour Tenant Owner, Tenant Admin or Security AdminWhich of your people may use what you have boughtApplication Access in Studio

The server checks both on every request. Hiding a menu in the browser is never the protection.

Editions ​

Your organization has one licence with one edition. Each edition includes the features of the one before it.

EditionAdds these featuresUsersBranchesAPI callsDevicesConcurrent sessions
CommunityDashboard Designer, Form Designer, API511,00011
StarterEntity Designer, Workflow25310,00035
ProfessionalHCM, CRM, Inventory, Permission Designer, Print Designer10010100,0001025
EnterprisePayroll, Manufacturing, Accounting, POS, Report Designer, Offline Sync1,0001001,000,000100250
UltimateAI Assistant, Mobile AppUnlimitedUnlimitedUnlimitedUnlimitedUnlimited

The numbers are the defaults when a licence is created. A platform administrator can change an individual feature or limit for your organization. A limit of -1 means unlimited.

New organizations start on a four-week trial of the Professional edition, with no credit card. The trial ends 28 days after registration, with no grace days. A platform administrator then sets the purchased edition and term. Organizations created before 16 October 2026 started on Community and keep their licence.

Status ​

StatusMeaningCan people work?
TrialEvaluation licence.Yes, until its end date.
ActivePaid and current.Yes.
Grace periodPast the end date but inside the grace days set on the licence.Yes.
ExpiredPast the end date and the grace period.No.
SuspendedStopped by the platform administrator.No.
RevokedCancelled.No.
InvalidThe licence signature does not verify.No.

A licence with no end date does not expire. Every licence is signed by the platform; a licence that was changed by hand fails the signature check and is treated as invalid.

What a plugin needs ​

Every plugin (and so every HCM application built from plugins) declares a licence tier:

  • free: installs on any edition.
  • an edition (starter, professional, enterprise, ultimate): installs only when your edition is that high or higher.
  • a per-plugin grant: for subscription, per-user or per-tenant pricing, the platform administrator grants the feature plugin:<plugin id> to your organization. Example: HCM Communications is on the standard tier and needs the feature plugin:hcm-communications.

If the licence does not cover a plugin, the install is refused with a message that says what is missing, for example: plugin "hcm-communications" requires license feature "plugin:hcm-communications", not granted for this tenant.

The same check runs every time a page of an installed plugin is opened. If your edition is lowered later, pages of plugins the new edition no longer covers stop opening, even though the plugin stays installed.

What the launcher shows ​

An application tile appears only when:

  1. its plugins are installed for your organization,
  2. its feature switch is on, and
  3. your Tenant Admin has not denied the person that application in Application Access.

So two people in the same organization can see different launchers.

Who changes what ​

I want to...WhoHow
Buy or change a plan, extend the term, change a limitPlatform administratorLicence console
Turn a licensed application off for one personTenant Owner / Tenant Admin / Security AdminApplication Access: Deny
Turn it back onThe sameApplication Access: Allow
Find out why a page refuses meAnyoneThe message names the missing licence feature or the denied application

Current limits of the system ​

  • User and usage limits are recorded but not yet enforced. The licence stores a Users limit (and the others in the table above) and platform administrators can see it, but adding user number 6 on a Community licence is not blocked yet. Treat the limits as contract terms until enforcement is switched on.
  • Expiry is all or nothing. After the grace period a licence is treated as expired; there is no separate view-and-export mode yet. Renew before the end date, or ask for grace days on the licence.
  • Access is per schema, not per HCM application. Denying hcm in Application Access blocks all five HCM applications for that person; you cannot allow Core HR and deny Talent yet.
  • Self-hosted installations use the same signed licence, validated with the platform's public key. Ask your vendor for the licence file.