How can we help?

Workspace boundaries are important when managing connected business applications and the information they provide. Polyosync organizes business operations within workspaces, and integration access must be considered in the context of the relevant workspace and its authorization controls. Why are workspace boundaries important? Different organizations may connect different external services and authorize access to different business resources. A connection associated with one organization should not be treated as a general-purpose connection available to unrelated organizations. What information can an integration access? The available information depends on: 1. The external account used for authorization. 2. The permissions granted by the provider. 3. The integration's supported operations. 4. The applicable Polyosync access controls. 5. The resources exposed by the connected service. Does workspace membership automatically grant access to every external resource? No such assumption should be made. Workspace membership and external service authorization are distinct concepts. An external provider may impose additional restrictions on the records or resources that can be accessed. Can an integration access information outside its intended business context? This depends on the permissions granted to the external account and the operations supported by the integration. Organizations should carefully review the scope of external authorization. What if one external account contains information for multiple businesses? The external provider's account structure and authorization model become especially important. Organizations should avoid granting unnecessarily broad access and should verify which resources are exposed through the connection. How should businesses evaluate integration boundaries? Step 1: Identify the workspace that requires the integration. Step 2: Determine the external account that will be connected. Step 3: Review the external account's accessible resources. Step 4: Verify the permissions required for the intended operation. Step 5: Confirm the supported integration configuration. Step 6: Test access using controlled business records. Step 7: Review whether the integration exposes unnecessary information. Step 8: Reassess the configuration whenever external permissions change. Are external provider restrictions separate from Polyosync restrictions? Yes. An external provider may restrict access based on account roles, organizations, resource ownership, or other authorization policies. These restrictions are independent of the internal structure of a Polyosync workspace. What if the external account has broader access than the intended workflow requires? Consider using a more restricted account, reducing available permissions, or selecting a narrower authorization scope where supported. Recommended approach Treat workspace access and external account authorization as separate security boundaries. Verify both before allowing an integration to participate in important business operations.