Skip to main content

Teams, workspaces & organizations

EntityFlow organizes an account into a three-level hierarchy. Organizations are top-level divisions that contain Workspaces, which in turn contain Teams. Diagrams live inside workspaces (or stay private to their author until promoted into one).

Account
└── Organization
    └── Workspace
        └── Team
            └── (diagrams)

Each level has its own page in EntityFlow Hub: Organizations, Workspaces and Teams.

Organizations​

Top-level divisions of your account — think departments or business units. On the Organizations page you create, rename and delete organizations. The number of organizations counts against your plan's limits, shown on the Hub's Overview.

Workspaces​

Workspaces are created under an organization and are where diagrams actually live. On the Workspaces page you create, rename and delete workspaces.

Teams​

Teams are created under a workspace and group people for shared access. On the Teams page you create a team, rename it, add or remove members, and delete it.

Why the hierarchy matters​

The hierarchy isn't just organizational tidiness — it drives access. A role granted at a higher level cascades downward: someone given Editor at the organization level is an editor across every workspace and team beneath it, without needing per-team grants.

tip

Plan your hierarchy around how access should flow. Grant broad roles high up for trusted members, and narrow grants lower down for scoped access. See Roles & permissions for exactly how cascading works.