How can we help?

An access denied or insufficient permissions error means that the requested operation is not available under the current authorization conditions. This may occur even when you are successfully signed in. Possible causes 1. Your assigned role has changed. 2. Your workspace membership has changed. 3. The resource belongs to another business environment. 4. The operation requires a different permission. 5. The relevant account configuration has changed. 6. Your authentication session is no longer valid. 7. An external integration lacks the necessary authorization. 8. A workflow is attempting an operation outside its permitted scope. How can I identify the cause? Step 1: Confirm that you are signed in using the correct account. Step 2: Verify that you are working in the intended business environment. Step 3: Identify the specific resource or operation being denied. Step 4: Ask an authorized administrator to review your membership and assigned role. Step 5: If the issue involves an integration, review the external provider's permissions. Step 6: If the issue involves a workflow, inspect the relevant execution details where available. Step 7: Record the exact error message. Step 8: Contact Support if the reason remains unclear. What if the operation worked previously? A change in permissions, workspace membership, integration authorization, or account configuration may explain the difference. Compare the current configuration with the expected access requirements. Should I request full administrative access? Not automatically. The appropriate solution is to identify the specific permission required. Granting broad administrative access may introduce unnecessary security risks. Can this error indicate that workspace isolation is working? Yes. An authorization rejection may be the expected result when a user attempts to access a resource outside their permitted environment. What if I believe I should have access? Ask an authorized administrator to verify your role and membership. Do not attempt to bypass the restriction. Summary Access denied errors should be investigated by checking identity, workspace membership, role permissions, and the requested operation.