How can we help?

Integration permissions determine which users, applications, and authorized operations can access connected external services. When a business connects an external platform to Polyosync, the connection may involve access to business information, customer records, operational systems, or other resources. Understanding and managing these permissions helps organizations maintain control over how connected systems are used. What do integration permissions control? Depending on the external provider and supported Polyosync integration, permissions may determine: 1. Which external resources can be accessed. 2. Whether information can be retrieved or modified. 3. Which operations are authorized. 4. Which account or organization owns the connection. 5. Whether additional authorization is required. 6. Whether access remains valid after changes to the external account. Integration permissions can exist at multiple levels. External provider permissions These are permissions granted by the connected service, such as access to customer records, calendar information, or CRM resources. Polyosync workspace permissions These determine what a user is authorized to access or manage within the Polyosync workspace. Integration-specific restrictions Some integrations may impose additional requirements or limitations. Why are integration permissions important? An external integration may interact with information that is sensitive or operationally important. Appropriate permissions help reduce the risk of unauthorized access, accidental modifications, and unnecessary data exposure. What is the principle of least privilege? Least privilege means granting only the access necessary to perform a specific operation. For example, an integration that only needs to retrieve customer information should not receive permission to modify or delete customer records unless those actions are required. Are all integrations granted the same permissions? No. Different services have different authorization models. The permissions available for one provider may not exist for another. Does connecting an integration automatically authorize every Polyosync user? Not necessarily. External authorization and internal workspace access are separate considerations. A connected external account does not automatically imply that every workspace member can manage the integration or access every connected resource. Can permissions change over time? Yes. Permissions may change when: 1. An external account is reauthorized. 2. An administrator modifies access. 3. A provider changes its authorization requirements. 4. An external user loses access. 5. Credentials expire or are revoked. 6. The integration is disconnected. What should organizations review before enabling an integration? Review the business purpose, requested permissions, external account ownership, sensitivity of the data involved, and operational consequences of authorized actions. Recommended approach Grant the minimum required access, use appropriately authorized accounts, and review integration permissions whenever business responsibilities or connected services change.