Accounts are the primary isolation boundary in Synqly. Every Integration belongs to an Account, and data never crosses Account boundaries — credentials, configuration, and operational data associated with one customer remain completely isolated from all others.
By mapping Tenants to Accounts, Synqly provides a clear and predictable model for authorization, auditing, and data isolation.
Accounts sit between the Organization and its Integrations. The Organization governs all Accounts collectively, while each Account independently owns and manages its own Integrations.
This structure creates clear ownership boundaries and ensures that integrations, credentials, and operational data remain isolated between tenants.
Although the terms are often used together, they represent different concepts:
| Concept | What it represents |
|---|---|
| Tenant | Your customer — a conceptual business entity in your system |
| Account | The Synqly resource that represents that tenant |
The recommended mapping is straightforward — in most cases, each customer in your application is represented by a single Account in Synqly.