How can we help?

An access denied or insufficient permissions error indicates that a requested resource or operation is not available under the current access conditions. This can occur even when the user is successfully signed in. Authentication confirms identity, while authorization determines which actions are permitted. Common reasons for access errors 1. The user does not belong to the relevant workspace. 2. The assigned role does not authorize the operation. 3. The requested resource belongs to another business environment. 4. The account invitation has not been completed. 5. The resource is unavailable under the current account configuration. 6. An external integration lacks a required permission. 7. The session is no longer valid. 8. A security-related restriction applies. 9. A workflow is attempting an operation outside its authorized scope. How can I troubleshoot the issue? Step 1: Confirm the account. Verify that you are signed in using the intended business or partner account. Step 2: Confirm the workspace. Ensure that you are operating in the correct business environment. Step 3: Identify the affected resource. Determine which page, record, integration, or operation is unavailable. Step 4: Review your assigned role. Ask an authorized administrator to confirm whether your role permits the requested operation. Step 5: Check workspace membership. Verify that your account belongs to the relevant environment. Step 6: Review external permissions. If the error involves an integration, inspect the authorization settings of the connected service. Step 7: Review session status. If the problem appears related to authentication, sign in again through the supported process. Step 8: Record the error. Capture the exact error message and approximate time. Step 9: Contact Support if necessary. Provide the relevant details without including passwords or sensitive credentials. Should I use another employee's account? No. Sharing credentials is not an appropriate solution to an authorization problem. Should an administrator grant full access to fix the error? Not automatically. The correct solution is to identify the specific missing permission and determine whether it should be granted. What if an AI Employee or workflow receives the error? Review the relevant execution context, resource access, and integration authorization. Do not assume that the issue can be resolved by expanding permissions indiscriminately. Recommended practice Investigate the actual authorization requirement before changing access settings.