How can we help?

An Enterprise Organization may operate through multiple workspaces representing different departments, business units, or operational environments. Users may require access to more than one workspace, depending on their responsibilities and the supported organization configuration. However, access to one workspace should not be interpreted as unrestricted access to every workspace in the Enterprise Organization. Workspace membership Workspace membership identifies the business environment to which a user has been granted access. A user should only be able to perform operations within environments for which they have the appropriate authorization. Role assignment The user's role determines the applicable level of access within the relevant authorization context. A role does not automatically establish membership in every other workspace. Why are workspace boundaries important? Consider an organization with three operational environments: 1. Finance. 2. Customer Support. 3. Sales. Each department may handle different business information and require different administrative responsibilities. A Customer Support employee may need customer-related information without requiring access to unrelated financial records. Similarly, a Finance employee may require billing-related information without needing administrative access to customer support workflows. How should access to multiple workspaces be managed? Step 1: Identify the employee's responsibilities. Step 2: Determine which workspaces are relevant. Step 3: Review the available membership management functionality. Step 4: Grant access through the supported authorization process. Step 5: Assign the appropriate role or permissions. Step 6: Verify that the employee can access the intended environment. Step 7: Confirm that unrelated environments remain inaccessible. Step 8: Review access when responsibilities change. Does organization-level administration remove workspace isolation? Not automatically. Organization-level management and workspace-level authorization are separate considerations. Any organization-wide administrative capability must be explicitly supported and enforced by the platform. Can a user access information from another workspace through an integration? External integrations must also respect their applicable authorization and configuration boundaries. Administrators should not assume that an integration automatically provides access to unrelated business environments. Can AI employees access multiple workspaces? Cross-workspace AI operations must be supported and authorized by the relevant platform configuration. They should not be assumed to be available simply because the workspaces belong to the same Enterprise Organization. Recommended approach Grant access according to operational need, verify workspace boundaries, and periodically review memberships. This helps organizations maintain separation between business environments while supporting legitimate cross-department responsibilities.