How can we help?

External integrations can connect Polyosync business operations with other applications and services. These connections may involve authorization credentials, external account permissions, and access to business information. Integration security therefore depends on associating each connection with the correct authorized business environment. What information may be involved in an integration? Depending on the provider, a connection may involve: 1. OAuth authorization. 2. API credentials. 3. External account identifiers. 4. Authorized access scopes. 5. Customer or operational records. 6. Integration configuration. 7. Workflow-related requests and responses. Does connecting an application make it available to every Polyosync customer? No. An integration authorized for one organization should not become accessible to unrelated organizations simply because they use the same platform. Can two companies connect the same external service? Yes, where the integration supports separate customer connections. For example, two organizations may each connect their own CRM accounts. Using the same CRM provider does not mean sharing the same CRM data. Can an AI Employee use any available integration? An AI Employee's access depends on the supported configuration and applicable permissions. An integration's presence in the platform does not automatically establish permission for every AI Employee to use it. What about external provider permissions? The external provider may define which records and operations an authorized connection can access. Organizations should review the permissions granted during integration setup. What happens if the wrong external account is connected? The connection may expose unintended information within the scope of that external account's authorization. An administrator should review the connection and correct it through the supported integration management process. Should API credentials be shared between businesses? No. Organizations should use appropriately scoped credentials and avoid sharing secrets between unrelated business environments. What if an integration appears to access the wrong organization's records? 1. Stop the affected operation. 2. Do not copy or distribute unrelated information. 3. Record the relevant integration and workspace. 4. Notify the responsible administrator. 5. Contact Polyosync Support. 6. Review the external provider's authorization settings. Recommended practice Use separate authorized connections, minimize permission scopes, protect credentials, and verify the intended business association before enabling integration-driven operations.