Usage

A usage record links one person to one subscription. Its assigned date marks when access was allocated; its last active date supports review of recent activity; its revoked date marks the end of that allocation. The Service Manager can examine these dates alongside the subscription’s licensed seats before discussing renewal or a request for another seat.

Suppose a team asks for additional access to a design application. The Service Technician identifies the subscription and records the person receiving the allocation. At the next review, the Service Manager can see who was assigned and when they were last active. A revoked date on a prior allocation should remain visible so the team can understand why it is no longer current.

• Subscription link. Each allocation belongs to a named application subscription.
• Person link. The user of the application is a person record, separate from the subscription owner.
• Dates. Assignment, last activity and revocation are distinct events in the allocation history.

Decide how the team receives reliable allocation and activity dates. If an identity or application provider supplies them, configure that connection and decide who checks exceptions. A manually maintained allocation should have a clear owner and update rhythm. Do not turn a last active date into an access grant: it is evidence for review, while assignment and revocation describe allocation state.

Agree how a service request leads to an allocation update. A request marked completed should be checked against the corresponding person and subscription. The Service Manager can then review the licensed seat figure in context. If someone moves teams, decide whether the same allocation continues or whether access should be revoked and a new request made.

Start with one subscription and two people. Record one allocation with an assigned date and recent activity; record the other with an assigned date and a revoked date. Ask the Service Technician to find both under the same subscription. Ask the Service Manager to explain which person still appears allocated and why, using the dates on the records.

Then open a submitted service request for the same service. The approval decision belongs on the request. After fulfillment, confirm the usage record references the intended person and subscription. A request for one person should never be satisfied by changing another person’s allocation. This check links the service work to the license record without confusing the two decisions.

• License allocations — People linked to subscriptions with assignment, activity and revocation dates.
• Subscription renewals — Terms and owner for the application being reviewed.

See subscription review and service request handling.