How can we help?

Access to integration management depends on the permissions assigned to the user within the Polyosync workspace and the authorization requirements of the external service. Organizations should ensure that integration management is performed only by appropriately authorized users. What activities may require integration management access? Depending on the supported functionality, these activities may include: 1. Establishing a new connection. 2. Authorizing an external account. 3. Reviewing connection information. 4. Updating configuration settings. 5. Reauthorizing an expired connection. 6. Disconnecting an external service. 7. Investigating integration errors. Who should manage integrations? Integration management should generally be assigned to users responsible for workspace administration, system configuration, or the relevant business operations. The exact actions available to each user depend on the implemented workspace permissions and integration functionality. Are Polyosync workspace roles relevant? Yes. Polyosync uses workspace roles and access controls. However, the presence of a particular role does not automatically mean that every external integration operation is available to that role. The relevant authorization must be verified for the specific action. Do external provider permissions also matter? Yes. A user may have permission to manage part of the Polyosync workspace but lack the necessary authorization within the external service. For example, the external provider may require an administrator or account owner to approve a connection. Can multiple employees use the same integration? This depends on the integration's authorization model and the access controls applied to the connected operation. Some services authorize access at the organization level, while others use individual user accounts. Does connecting a personal external account make it a business-owned integration? Not necessarily. The ownership and availability of the connection depend on the external provider, the account used for authorization, and the integration implementation. What happens when the employee who authorized an integration leaves? The connection may remain active, become invalid, or require reauthorization, depending on the provider and authentication model. Organizations should review integrations associated with departing employees. How should access responsibilities be organized? Step 1: Identify the business owner of the integration. Step 2: Determine which operations are required. Step 3: Identify who should be allowed to configure the connection. Step 4: Verify the external provider's authorization requirements. Step 5: Confirm the relevant Polyosync workspace permissions. Step 6: Review the integration after changes to personnel or responsibilities. Recommended approach Avoid relying on personal accounts for business-critical integrations when an appropriate organization-managed authorization method is available. Maintain clear responsibility for connection ownership, configuration, and ongoing access reviews.