# Organization

The Organization is the foundational container in Synqly. Every resource, configuration, integration, and identity ultimately belongs to an Organization.

An Organization typically represents the company, product, or platform that is using Synqly. Everything created within Synqly including Accounts, Integration Points, Mappings, Members, Integrations, and related configuration is scoped to a single Organization.


```mermaid
flowchart TD
    org(Organization)
    mem(Members)
    acc(Accounts)
    ip(Integration Points)
    map(Mappings)
    int(Integrations)
    aud(Audit Data)

    org --> mem & acc & ip & map & aud
    acc --> int
```

This hierarchy is more than a structural relationship. It reflects the platform's ownership model: resources do not exist independently, but as part of a larger integration system governed by an Organization.

 Understanding the Organization as the root of ownership, security, and administration provides the foundation for understanding every other concept in the Synqly data model. 

### Why Organizations Exist

The Organization model exists to answer a fundamental question: **who owns this integration ecosystem?**

Without an Organization boundary, resources such as Accounts, Integrations, and credentials would exist in a shared global space making it difficult to enforce security, manage permissions, track ownership, and isolate one customer's environment from another.

The root of everything
Every permission check, audit record, configuration decision, and integration ultimately traces back to an Organization. It is the root authority that owns all resources and establishes the scope within which administrative actions can occur.

### Organizations as Integration Systems

A useful way to think about an Organization is as a complete integration system rather than
merely a container of resources.

An Organization contains everything required to manage integrations at scale:

- Members who administer and operate the system
- Accounts that represent customers or isolation boundaries
- Integration Points that define reusable integration policies
- Mappings that customize data translation and behavior
- Integrations that connect external providers
- Credentials, tokens, and audit records that support secure operation


Together, these resources form a self-contained integration environment.

### Organizations and Multi-Tenancy

One Organization can serve many applications, customers, and tenants.

For example, a SaaS platform may use a single Organization to manage integrations for hundreds
or thousands of customer accounts. Each customer is isolated through Accounts, while the
Organization provides the shared governance layer that manages those Accounts collectively.

This separation is intentional.

Owner vs. tenant
The Organization represents the owner and operator of the integration platform, while Accounts
represent the individual customers, business units, or isolation boundaries within that platform.