Licence

What It Is

A licence expresses the commercial basis for using a Rhythm application in a workspace. It can come from the customer’s contract terms or from a recorded Rhythm staff decision. The licence explains commercial eligibility; the application’s readiness and a particular person’s permissions answer additional questions before work can proceed.

A contract-derived licence is represented by an application window associated with a HubSpot company. Several workspaces may read that same commercial identity. A staff override instead addresses one workspace and application with a reason and effective period. Both forms can explain present eligibility, but they have different origins and histories. The licensing capabilities define their precedence and time boundaries.

What It Is Not

A licence does not by itself prepare the application’s data or configuration. For applications requiring commercial coverage, operational readiness remains another input to availability. Always-available applications follow their explicit exception in that decision.

The licence also does not give every person in the workspace every application permission. Individual access derives from the security model. A staff override is a recorded commercial exception rather than an unrestricted administrative bypass. Keeping these meanings separate helps staff explain why an apparently licensed application still cannot be opened.

How It Is Used

Rhythm staff inspect workspace licensing in HQ to understand the decisions behind access. They may grant a trial or bridge a commercial delay, withhold an application deliberately, or withdraw a prior exception. Historical decisions remain relevant to explaining how the workspace reached its present standing.

The contract source reads HubSpot terms and products and derives coverage windows. Synchronization health distinguishes a complete commercial read from a missing configuration or provider failure. The prior snapshot remains available during a failed read, but its known dates continue to govern eligibility. The pinned operating record describes live source activation as pending, so the examined contract behavior rests on code and stubbed evidence rather than a completed real-provider rollout.

Its Facets

Staff override. A grant or withhold records an intentional workspace decision with an explanation and period. Revocation ends its effect without replacing the original decision.

Contract window. Derived application coverage combines eligible terms and renewals. Its end and grace dates help explain upcoming or completed expiry.

Company link and commercial copy. The workspace identifies which company’s contracts apply. Rhythm keeps a read-only copy and synchronization health for diagnosis.

Product map. The declared mapping translates commercial products into application and feature grants. Unknown products need attention rather than silently granting access.

Licence standing. Readable states distinguish ordinary coverage, override coverage, grace, expiry, withhold and absence. Staff retain distinctions deliberately simplified in the customer response.

Export allowance. Customer or workspace allowances bound full data exports and keep a history of replacement decisions. They are a related commercial facet administered through the export owner.

How It Relates

Workspace applications combine licence standing with operational readiness. Security consumes availability and separately evaluates a person’s access. Company-level windows can outlive deletion of one workspace because other workspaces still depend on them. Staff decisions attempt security-history entries and authorization invalidation after commercial writes, with failure gaps recorded for examination.

What It Could Become

The product should reconcile this implemented model with the later governed-entitlement decisions before design proceeds. Renewal warnings are accepted intent but remain missing. Contract synchronization also needs an explicit route from new commercial coverage to missing application setup. A real-provider activation should confirm source properties and compare one known customer’s resulting windows before broader synchronization changes access.