Organizations, groups, and scopes: how a Floxar account is organized
Every Floxar customer has an account — the top-level home for all of a company's people, content, and activity. Inside an account, people and content are organized using organizations and groups, known collectively as scopes. Understanding this structure explains what you can see and do in Floxar, and where the content you create ends up.
The hierarchy: account, organizations, groups
The structure has three levels. The account sits at the top and typically represents your company or a major business unit. Organizations are subdivisions directly under the account — often departments, regions, or business lines. Groups are the most granular unit: teams or functional groups that always live inside an organization. Administrators manage this structure, and account-level settings control whether organizations and groups can be created at all; a group can only exist once at least one organization does.
Access levels
Access in Floxar is granted as a role at a specific level of the hierarchy. From most to least privileged, the roles are: Admin (full management, including user administration), Edit (create and modify content), Engage (run workflows and interact with content), View (read-only access), and Member (belongs to a level but has no access rights on its own). You hold one role per level you are attached to.
Permissions inherit downward
A role granted at one level automatically applies to everything beneath it. Admin on the account means Admin in every organization and group inside it. Edit on an organization means Edit in all of that organization's groups. Grants at lower levels are additive, and when several grants apply to the same place, the most privileged one wins. For example, someone with View on the account and Edit on one organization can read content anywhere in the account, but can create and modify content only within that organization and its groups.
The Member role exists to connect you to the levels above the place where your real access lives. A person might be a Member of the account and a Member of an organization, with an Edit role granted on a single group inside it — meaning they can author content in that group but have no access elsewhere. This is also why someone can appear in the account's user list while holding no meaningful access yet: they belong, but their working role has not been granted.
Content belongs to one place
Content follows the same structure. Every flow, bit, and reference belongs to exactly one place in the hierarchy: the account level, where it is available to everyone in the account, or a specific organization or group, where it is visible to that scope's members. Content does not cross between scopes — scoping is how one department's processes stay out of another department's way while shared, account-wide content remains available to all.
Your working context
Day to day, you work within a selected scope, called your working context. Your working context determines which content appears in listings and which scope newly created content is placed in by default. You can switch your working context from within the app whenever you need to work in a different part of the hierarchy. If your access to the selected scope is ever removed, Floxar automatically falls back to the account level, so you are never left stuck in a place you can no longer see.
Last reviewed: 2026-07-28