How can we help?

Enterprise access control determines which users are authorized to access specific business environments and perform particular operations. In Polyosync, access decisions may involve several factors, including workspace membership, assigned role, operation-specific authorization, and relevant security controls. Understanding these factors helps administrators investigate access problems and configure appropriate responsibilities. Role-based permissions A user's assigned role is one component of their authorization. Different roles are intended to support different types of operational and administrative responsibilities. However, a role name should not be treated as a complete description of every permitted action. Workspace membership A user must have appropriate access to the business environment in which an operation is performed. Belonging to an Enterprise Organization does not automatically establish permission to access every child workspace. Operation-specific authorization Some operations require particular permissions regardless of whether a user can access the surrounding interface. For example, being able to view a configuration page does not necessarily mean that the user can modify its settings. Why might two users see different functionality? Possible explanations include: 1. Different assigned roles. 2. Different workspace memberships. 3. Different organization configurations. 4. Different enabled Enterprise capabilities. 5. Operation-specific access restrictions. 6. Recently changed permissions. 7. An outdated user session. Does access to a page mean every action on that page is permitted? No. Viewing a page and performing an administrative operation are different authorization decisions. Can a user have permission to view information but not modify it? Yes, where the implemented authorization rules distinguish viewing from modification. Can administrators bypass permission checks? Administrative role assignments should not be interpreted as permission to bypass security controls. All operations remain subject to applicable platform authorization. How should administrators investigate permission issues? Step 1: Identify the affected user. Step 2: Confirm the relevant workspace. Step 3: Review the assigned role. Step 4: Identify the exact operation being attempted. Step 5: Check whether the relevant Enterprise capability is enabled. Step 6: Review recent membership or role changes. Step 7: Test the operation using an appropriately authorized account. Step 8: Contact Polyosync Support if the observed behavior does not match the intended access configuration. Why is backend authorization important? An interface may hide or disable functionality for users without sufficient permissions. However, secure access control must also be enforced when operations are processed. Organizations should not rely solely on whether a button or menu is visible. Recommended approach Treat access control as a combination of workspace membership, role assignment, and operation-specific authorization. Review the complete access context when granting permissions or investigating unexpected behavior.