GOVERNANCEOS / LICENCE & FEATURES

Licence & features

Review the installation’s feature entitlement. User permissions and operational write restrictions apply independently.

Current licence

Feature access

Command Centre

Checking

Evidence-led programme and project oversight.

Status reporting

Checking

Approved status, completion and reporting-date comparisons.

SteerCo reporting

Checking

Programme evidence selection and executive reporting.

Governance workflow

Checking

Case, lifecycle, reconciliation and recovery reviews; existing operator and write gates still apply.

Administration tools

Checking

Discovery, schema, coverage and supporting source inspection.

White-label attribution

Checking

Separately signed allowance to remove standard product attribution.

Sponsor Portal

Checking

Separately licensed read-only executive access to explicitly assigned responsibilities.

Plan feature matrix

Working feature allocation for this release. No prices or project/seat quotas are established here. Signed customer allowances may differ from the standard plan.

Feature	Starter	Professional	Enterprise	Enterprise Private
Command Centre	Included	Included	Included	Included
Status reporting	Not included	Included	Included	Included
SteerCo reporting	Not included	Included	Included	Included
Governance workflow	Not included	Not included	Included	Included
Administration tools	Included	Included	Included	Included
White-label attribution	Not included	Not included	Not included	Not included
Sponsor Portal	Not included	Not included	Not included	Not included

Licence check & support

Review an offline check alongside the current server status, then prepare a support snapshot.

Run an offline licence check

Your administrator runs this from the extracted release folder with its dependencies installed:

npm run licence:check -- --config-file /private/config.env

For a JSON file to import here, run:

npm run --silent licence:check -- --config-file /private/config.env --json > licence-check.json

The command reads the selected configuration and its configured licence document, using this package’s bundled publisher trust. It makes no network calls or changes. Relative licence paths resolve from the command’s working directory, which must match the application’s working directory. Exit code 1 means a blocked check; review the JSON even when the command exits with 1.

It cannot confirm runtime overrides, deployed-build trust, real sign-in, billing or hosting readiness. Configuration values and file names are omitted from the report.

Import offline licence check (JSON, up to 64 KiB)

Offline file content is not independently verified or linked to this running installation. It cannot grant access. No credentials, tenant/site identifiers, licence documents, issuer keys or local paths are included. Live identity, permissions, billing, usage limits and hosting readiness require separate validation.

Changing access

Your licence administrator supplies a signed licence for the configured organisation and SharePoint target. A browser setting, plan name or feature flag cannot grant access. Upgrades and downgrades take effect on the next server request after the signed document is replaced; refresh this page to update the display.

Entra access, operator authorisation and existing workflow/bootstrap/recovery gates remain necessary. An entitlement does not enable writes. Billing, project/seat metering and remote activation are not provided by this page.