How can we help?

If Polyosync displays an access denied message or certain features are unavailable, the issue may be related to your workspace membership, assigned role, permissions, or subscription configuration. Polyosync separates access between business workspaces and applies authorization boundaries to help prevent users from accessing resources outside their permitted scope. What should I check? 1. Confirm that you are signed in with the correct account. If you use multiple email addresses or accounts, verify that you are using the identity associated with the intended business. 2. Confirm the correct workspace. Make sure the resource belongs to the workspace you are currently authorized to access. 3. Review your assigned role. Different users may have different administrative or operational responsibilities. Your role may not include permission to view or modify the requested resource. 4. Contact your workspace administrator. If you believe your access should be different, ask an authorized administrator to review your permissions. 5. Check whether the feature is available under your account configuration. Some capabilities may depend on subscription entitlements or Enterprise-specific configuration. 6. Sign out and sign back in if your access was recently changed. This may help refresh session-related information, although it does not replace the underlying authorization process. What should I do if another employee can access the feature? Compare the relevant roles and authorized permissions rather than sharing credentials. What if I receive access denied when opening a direct link? A link does not grant permission by itself. Even if another user shares a URL, you must still have authorization to access the associated resource. Can Support bypass workspace restrictions? Access restrictions should not be bypassed simply to resolve a convenience issue. Changes to access must follow the appropriate authorization process. When to contact Support Provide the affected feature, the error message, your expected access level, and whether the issue occurs across multiple pages. Do not include another user's credentials or confidential authentication information. Security boundaries are intentional platform protections and should be preserved during troubleshooting.