Pause a workspace and restore access¶
Intended journey from Tenant Admin
06 Final Screens. The frontend is still work in progress: the inspected lifecycle page uses sample data, and confirmation changes local preview state without submitting a real suspension or restoration. Use the steps to understand the intended experience; use your authorized support route for a real change until the connected journey is available.
A pause affects the whole workspace's ordinary product access. Confirm that this is the intended scope before proceeding. For one person, use the member-access guide; for an inactive account, use account recovery.
Prepare the change¶
You need current workspace-administrator authority and an eligible active account and membership. Being an organization head, appearing in a governance count or seeing a preview button is not sufficient authorization. Platform staff use their separate authorized support process.
Before an actual pause:
- Confirm the workspace name and its identifying address or slug, especially if you belong to several workspaces.
- Agree the reason, affected work, responsible administrator and condition for restoring access.
- Review outstanding work and arrange any necessary continuity steps with its owners. A pause does not guarantee that every background activity or external operation stops.
- Check whether this is an administrator pause, billing suspension or support restriction. Payment and qualifying capacity recovery can restore billing suspension; they do not lift a manual or support pause.
- Keep an incident or change reference and a contact route available. Do not put passwords, verification codes, access tokens or sensitive investigation details in the reason.
If the requirement is permanent closure, account deactivation, subscription cancellation, data deletion or a legal hold, resolve that separate process before using lifecycle controls.
Review the workspace¶
In the intended Tenant Admin experience, select the correct workspace and choose Lifecycle in the navigation. The page title is Workspace Lifecycle.
Review the workspace name, current status and available dates. The People Impact area summarizes people affected by the change, and the action area shows the available next step. The illustrated people, administrator and request counts are examples; a preview does not establish actual membership or authority.
An active workspace offers Pause access in the inspected design. Its suspended view offers Restore access, with the alternative action unavailable. The newer backend restricts administrator restoration according to the recorded suspension type; that designed button is not proof that restoration is allowed. The intended screens still need matching billing and support recovery explanations. Close workspace is a separate permanent action and is not part of temporary recovery.
Refresh details is intended to reload the workspace information. A refresh must not itself pause, restore or open a confirmation for a different operation. The current Figma prototype contains a destination discrepancy for this action, and the frontend refresh returns to its preview route; neither establishes a verified real-state refresh.
Pause access¶
When the connected journey is available and the actual workspace is active:
- Choose Pause access.
- Read the Pause workspace access? confirmation. Verify the workspace context and the displayed people and pending-request summary.
- Enter a short, nonempty Reason for pause. Record enough context for authorized recovery without including secrets.
- Choose Cancel to leave without submitting, or choose Pause access to confirm the intended change.
- After a real successful submission, refresh the workspace's actual state and confirm that access is paused. Ask an appropriate test user or administrator to verify a new ordinary product request, without disrupting live work unnecessarily.
The reason is required. The inspected frontend displays Enter a short explanation before pausing access. when it is blank. Filling it in only satisfies the preview's validation; it does not submit the backend request.
The intended confirmation retains the workspace and its membership context. Ordinary product access is restricted while paused, but account sign-in and authorized recovery are separate. Do not interpret the design's broad sign-in wording as a promise that all identities, sessions or integrations have been disabled.
If a real request times out or its result is unclear, read the actual workspace status before trying again. A repeated request is not guaranteed to behave as a harmless duplicate. An already-paused state may mean the earlier request succeeded.
Restore access¶
Before restoration, resolve or explicitly accept the condition that caused the pause and check the permitted recovery route. An administrator can restore only a pause recorded as allowing administrator restoration. For billing suspension, follow billing recovery and confirm that the payment has been verified and applied; for a support restriction or older pause without that permission, contact authorized support. A provider return page, paid-looking preview or notification alone is insufficient.
When the connected journey is available, the actual workspace is suspended and administrator restoration is permitted:
- Open Lifecycle for that workspace and review the paused state.
- Choose Restore access.
- Read Restore workspace access? and check the workspace and people summary. The intended restore confirmation does not request a new pause reason.
- Choose Cancel to keep the workspace paused, or choose Restore access to submit the intended reinstatement.
- Refresh the actual workspace state and confirm it is active. Verify access with a fresh workspace selection or product request as appropriate.
- Check any affected member separately if access remains unavailable. Review account activity, membership and branch status, product licenses, capacity, permissions and workspace access policy.
Restoration does not automatically admit waiting join requests or override an inactive account. Eligible license restoration depends on capacity and current eligibility. Do not promise every person immediate access solely because the workspace is active.
Accepted renewal or a qualifying capacity change can also restore a billing suspension. It does not lift a manual or support pause. Check the actual state and recovery permission before submitting another restoration.
If you are an affected member¶
Confirm which workspace is affected and retain the visible message, approximate time and action you were trying to perform. Contact its administrator through your organization's usual channel. Explain whether the problem affects all products, one product or only your account.
Do not create another account or make another payment solely to work around a pause. A suspension may have a non-billing reason, and a restored workspace can still have individual access restrictions. You may remain able to sign in or use another eligible workspace; neither proves that access to the paused workspace has returned.
If you are an external participant, contact the person or organization that granted your access. This guide does not grant access to Tenant Admin or its recovery actions.
Resolve common problems¶
| What you observe | What to check or do |
|---|---|
| Lifecycle is missing or an action is unavailable | Confirm the workspace, your current administrator role and whether the connected experience is available. Use authorized support if necessary. |
| A preview changes to paused or active | Treat it as a demonstration. Verify through the real authorized service before communicating a completed change. |
| The reason is rejected | Enter a short, nonempty explanation; avoid secret or sensitive values. |
| An action fails because the state changed | Refresh the actual state. Another administrator, renewal or capacity recovery may already have changed it. |
| A request times out | Check the current state and incident reference before retrying. Do not repeatedly submit an uncertain mutation. |
| A payment completes but access remains unavailable | Check that it was verified and applied to the intended workspace, whether a separate manual/support pause remains, and individual access. See the Billing guide. |
| The workspace is active but one person is blocked | Investigate that person's account, membership, branch, licenses, permissions and access policy. |
| You cannot reach the recovery controls | Ask an eligible administrator or authorized support operator to investigate; do not bypass access checks. |
| The workspace is closed | Restore access is not a reopening procedure for a permanently closed workspace. Escalate through the closure process. |
No fixed recovery duration is established by this guide. Cached context, background processing, identity availability and the underlying cause can affect when a fresh request reflects the change.
Confirm and communicate the outcome¶
Administrators should retain the workspace identity, reason, action taken, observed result and any remaining individual access problems. Share a clear update through the organization's agreed channel after verifying the actual result. Automatic delivery of a message to every affected person is not established.
Managers should confirm that critical work can resume and that unresolved access issues have an owner. Business owners should review any separate commercial, continuity or data-handling obligations. Support should distinguish workspace suspension from an account, membership, license or policy problem before recommending a new purchase.
For the business rules and automatic-recovery limits, see Pause and restore workspace access.