Staff Access Grant
What It Is
This retained record is superseded by the User Account concept, which now owns its facets.
A staff access grant records the basis on which a Rhythm employee can work inside a customer's workspace. Rhythm HQ authority manages the platform; it does not automatically turn a staff member into one of a customer's console users. Staff access provides the connection between those two kinds of work while retaining the employee's own identity.
Routine access begins with a request for a customer-appropriate role, a duration and a reason. The request does not provide usable authority while it waits. A customer administrator can approve access or give it directly. Emergency access supports an incident without prior approval under its own safeguards. Standing access supports the recorded authority of Rhythm Administrators and founding super users across customers.
The grant carries its kind, status and relevant dates, together with the people and reasons behind its creation and decisions. An ordinary role assignment provides the resulting application authority. Keeping the access record separate from that assignment lets administrators explain both why staff entered and what they could do.
What It Is Not
The grant is distinct from a staff role and from membership at the customer. It does not impersonate a customer employee: activity remains attributed to the Rhythm person who performs it. A request that awaits a decision is also distinct from active access and cannot be treated as consent already given.
How It Is Used
Support staff request access from Rhythm HQ when customer work requires entry. Authorized customer administrators review the request in Rhythm Access and decide whether the role and duration are appropriate. They can also give access to a named staff member or revoke existing access.
Rhythm Administrators use standing access where it exists and emergency access only where the relevant safeguards allow it. A banner explains the current entry into a workspace. Staff can finish temporary work by ending their own eligible grant, while administrator actions cover appropriate intervention in another person's access. Notifications and security history support review of those decisions.
Its Facets
Approved and given access. Approval resolves a staff request; given access starts with the customer's own decision. Duration and role describe the work authorized.
Emergency access. An incident reason, ticket and short maximum duration distinguish emergency entry. Customer and staff-security notifications provide visibility even though approval is not required first.
Standing access. Role-based or founding authority establishes customer-wide entry without a routine expiry. A deliberately revoked standing grant is not restored by deployment.
Request state. Waiting, decided and ended records explain progress separately from whether the resulting assignment currently allows work.
Reporting. Security history and the emergency report support investigation without treating the employee as a customer member.
Staff standing. HQ roles determine who can request, open emergency access or intervene in another employee's grant.
How It Relates
The record names a staff account and a workspace or customer. Its ordinary assignment uses a role appropriate to customer work. The security context presents reachable workspaces, while signed and cached authorization decisions determine the practical propagation window when access changes.
What It Could Become
The product should communicate that expiry or revocation can take up to the accepted cache bound to affect previously authorized requests. Mandatory staff multi-factor sign-in remains deferred. The product should keep consented, emergency and standing entry distinguishable in access reviews, so customers understand the basis for staff work and the decisions available to them.