How can we help?

External integrations require authorization so that Polyosync can interact with supported applications and services on behalf of an authorized business account. The permissions required depend on the external provider and the specific operations supported by the integration. Not every integration requires the same level of access. Why are permissions necessary? External applications protect their information and functionality through authentication and authorization mechanisms. When connecting an integration, the provider may require approval before another application can access data or perform operations. For example, an integration that retrieves records may require read access. An integration that updates records may require additional write permissions. The actual permissions requested depend on the provider and integration implementation. What authorization methods may be used? OAuth authorization Some external services provide a secure authorization process in which you approve access through the provider's own interface. API credentials Other services may require an API key, token, or another supported credential. Additional configuration Certain integrations may require account identifiers, workspace selections, or other provider-specific information. The available method depends on the integration. How should I review requested permissions? Before approving a connection: 1. Confirm that you are connecting the intended external service. 2. Verify that the account belongs to the correct business or organization. 3. Review the permissions displayed by the provider. 4. Determine whether the requested access is appropriate for the intended business operation. 5. Confirm that you are authorized to approve access. 6. Avoid granting unnecessary administrative privileges. Does connecting an integration give every employee access to the external service? Not automatically. Workspace access, integration configuration, and external service permissions are separate considerations. The exact access available to individual users or AI-powered operations depends on the implemented authorization controls. Can an AI Employee perform any action supported by the external service? No such assumption should be made. An AI Employee's available actions depend on its configuration, the integration's supported capabilities, and the relevant authorization boundaries. What happens if permissions are insufficient? An operation may fail or return an authorization error. In that situation, review the external account's permissions and the requirements of the specific integration. Do not grant unrestricted access simply to bypass an error. Can permissions change after a connection is established? Yes. External providers may allow administrators to modify or revoke access. Changes to permissions can affect previously functioning integrations. What if I approved the wrong account? Review the integration configuration and the external provider's authorization settings. Where supported, disconnect the incorrect connection and establish a new one using the appropriate account. Security recommendation Apply the principle of least privilege. Grant only the access necessary for the intended operation and periodically review whether the integration still requires those permissions. Never share passwords, API keys, or access tokens through support messages or other unsecured communication channels.