Understand your account and workspaces¶
Your account identifies you. A workspace identifies the organization in which you are acting. A product supplies a particular area of work, and its permissions determine which actions you may perform.
Keeping those boundaries clear helps you solve the right problem when access fails or information appears out of date. This guide links to the intended screen journeys rather than introducing separate recovery controls.
Draft and availability: The detailed guides follow the newer final-screen designs and explain current frontend differences. Connected operation, environment availability and reader acceptance remain under review.
What changes when you change context¶
| Context | What it contains | What it does not grant by itself |
|---|---|---|
| Personal account | Sign-in identity, shared profile and account-level security | Membership in every organization |
| Workspace membership | Your relationship and assigned access within an organization | Every product permission or an active application in the environment |
| Product context | The selected area of work within its access rules | Authority to perform every operation on every item |
| Organization administration | Authorized responsibility for that workspace | Platform staff access or unrestricted information access |
| Platform staff context | Separately authorized platform operations | Automatic permission to read raw customer content |
Use profile and product access and membership and permissions for the detailed model. Platform staff administration explains the separate staff boundary.
Changing workspace does not move the first organization's records or permissions into the next one. Confirm the organization name before taking an action or asking someone to change access.
Personal information and organization information have different owners¶
Use the profile guide to change supported personal details. The shared profile is available at account level; organization-specific workforce information belongs to People.
A personal name, country or timezone change does not change the organization's plan, hosting location or membership permissions. The current profile form also has partial-save and value-removal limitations. Reopen it and check the actual saved values when a result is uncertain.
Optional account email choices have their own notification guide. They do not remove business responsibilities, change workspace access or control every service-message category.
Know which verification you are completing¶
| Verification purpose | What it establishes |
|---|---|
| Account activation | Verification of the new account's email and establishment of its password through the activation flow |
| Sign-in verification | Completion of the extra check for that account login attempt |
| Extra-verification setting change | Confirmation of the requested account-security setting |
| Workspace entry verification | Completion of the relevant workspace's entry challenge, while membership and policy still permit access |
| Password recovery | Completion of the separate credential-recovery process |
Use the newest code for the same account, attempt and purpose. Requesting replacements can invalidate earlier messages. A valid code does not reactivate a workspace membership, approve a pending join request or make an unavailable application ready.
Follow sign-in and extra verification, account activation, workspace verification or password recovery, according to the step that failed. The guides retain current resend-control and error-wording limitations.
When the expected workspace is missing¶
First confirm the account email and the exact organization. If you were invited, check whether that invitation was accepted. If you asked to join, confirm whether the organization approved the request.
The invitation and join-request guide explains the different lists and their limits. A disappeared invitation can have several causes, and the join-request list is not a complete history.
If you recently joined, refresh workspace access and follow the canonical recovery guidance. The current chooser can depend on saved sign-in information. Ask the administrator to confirm current membership if the display remains inconsistent.
Do not create a duplicate account or a new workspace to repair a missing entry.
When the workspace appears but does not open¶
A workspace can be visible while its account, membership, branch, email policy, verification or lifecycle checks prevent entry. An administrator label or a saved Ready badge does not override those conditions.
Use workspace-entry recovery. Give the organization administrator the affected workspace and visible message. They should investigate the actual failed condition rather than infer it from a generic error.
A paused workspace and an account deactivation are different. Workspace lifecycle explains access recovery for the organization; account lifecycle explains recovery of the person’s account.
A payment-related message is not proof that every suspension can be fixed by starting checkout. The authorized owner should establish the real suspension reason and consult the original Billing record.
When the workspace opens but a product does not¶
Read the product choice's message and the product-choice guide.
- A missing or revoked product assignment needs review by the authorized administrator.
- An environment-disabled frontend needs confirmation from the rollout owner.
- An application marked not ready has an implementation limitation.
- A denied action inside an available product needs that feature's permission and state checks.
Visible cards can outlast a licence change in the current frontend. Their presence is not permission. Likewise, a licence cannot enable an application that has not been delivered.
Use the capability map to find the relevant feature's availability and recovery explanation.
Changing account access does not change every other responsibility¶
Sign out ends the described device session. It does not certify revocation of every session elsewhere.
Account deactivation, changing a workspace membership and pausing a workspace affect different scopes. None should be assumed to cancel every business task, payment commitment or retained record.
Where a change affects ongoing work, involve the responsible organization administrator or process owner. Use the specific feature's rules to establish the consequence instead of treating account state as a universal cancellation.
Ask for help with useful, limited information¶
Tell the authorized support route which environment and workspace are affected, the action you attempted, the approximate time, the item or request reference when available, and the visible error.
Do not include passwords, one-time verification codes or browser-session credentials. Follow Support ID guidance when an authorized support person asks for that identifier. It participates in guided support and should not be posted publicly.
Refreshing the Support ID does not end an already active support session. The intended End guided help control is not connected in the current profile; the guided-help instructions explain the required operator follow-up.
Return to Getting started for the overall entry path, or the user starting page for your next business task.