Polyosync Help Center

How can we help?

Browse help articles or contact our support team.

Request Support

How do permissions work when Polyosync connects to external applications and services?

External integrations allow supported Polyosync functionality to interact with other applications and services. These connections may require permission to read information, create records, update data, or perform other supported operations. Integration permissions are important because they determine what the external service allows the connection to do. What types of authorization might be used? Depending on the integration, authorization may involve: 1. OAuth authorization. 2. API keys. 3. Access tokens. 4. Service account credentials. 5. Provider-specific permission scopes. The available method depends on the external provider and the supported Polyosync integration. What are permission scopes? Scopes define the types of access granted to an application. For example, a provider may distinguish between reading records and modifying them. Not every provider uses the same permission model. Should I grant every permission requested by an external service? Review the requested permissions carefully. Where configurable, grant only the access necessary for the intended business operation. What happens if a required permission is missing? The connection may succeed while certain operations fail. For example, an integration may be authorized to read records but not update them. The exact behavior depends on the provider and integration. Can an integration access information outside Polyosync? An authorized integration may interact with the external service according to its granted permissions. Organizations should review the external account and data scope associated with the connection. Can one workspace use another workspace's integration? An integration should remain associated with its authorized business context. Cross-workspace use should not be assumed unless explicitly supported and authorized. What happens when permissions change at the external provider? The integration may require reauthorization or configuration changes. Administrators should review the provider's current authorization settings. What if integration credentials are compromised? Follow the external provider's credential revocation or rotation procedure. Review affected workflows and contact Polyosync Support if unauthorized activity may have occurred. Recommended practice Use appropriately scoped external accounts, protect integration credentials, and review permissions before enabling automated operations.