How can we help?

OAuth authorization errors occur when an external provider cannot complete or accept an application's authorization request. These errors may happen during the initial connection, when renewing access, or when performing an operation that requires additional permissions. Common OAuth-related errors Access denied The authorization request was rejected, cancelled, or blocked by the provider's policies. Invalid scope The application requested a permission that is invalid, unsupported, or not available for the external account. Insufficient scope The existing authorization does not include the permission required for the requested operation. Invalid grant An authorization code or token may be expired, revoked, invalid, or otherwise unacceptable to the provider. Invalid client The provider could not validate the application's client credentials or configuration. Redirect URI mismatch The authorization callback address does not match the address registered with the external provider. Administrator approval required The provider requires an administrator to authorize the requested access. How to troubleshoot OAuth errors Step 1: Identify the error. Record the exact message or error code displayed during authorization. Step 2: Confirm the correct external account. Verify that you are signing in to the intended account or organization. Step 3: Review the requested permissions. Determine whether the account is authorized to grant the required access. Step 4: Check for administrator restrictions. Some organizations restrict third-party application access or require administrative consent. Step 5: Restart the authorization flow. If the authorization session has expired or was interrupted, begin the connection process again. Step 6: Check browser restrictions. Ensure the provider's authentication page and redirect flow can complete. Step 7: Verify external service availability. An outage or authentication incident may interrupt authorization. Step 8: Reauthorize when appropriate. If existing credentials have expired or been revoked, use the supported connection procedure to establish new authorization. Step 9: Test the intended operation. After authorization succeeds, confirm that the required functionality works. Can I fix an invalid client or redirect URI error myself? These errors often involve application-level configuration rather than individual user permissions. If the connection is managed by Polyosync and the issue persists, contact Support. If you are configuring a custom integration, verify the provider's registered application settings. Should I share an OAuth authorization code with Support? No. Authorization codes, access tokens, refresh tokens, client secrets, and other credentials must be kept confidential. What information is useful for troubleshooting? Provide the integration name, error code, approximate timestamp, and the point at which authorization failed. Recommended approach Identify whether the problem concerns user consent, provider permissions, expired authorization, or application configuration before attempting changes.