Skip to main content

Account settings and administration

Account administrators keep a Floxar account organized: they shape its structure, manage its people, and set account-wide options. This article gives a conceptual overview of what account administration covers. You need the Admin permission level on the account to do these things.

How an account is structured​

Your account is your company's own space in Floxar. Inside it, you can organize work on two optional levels:

  • Organizations — major divisions, such as departments, business units, or regions.
  • Groups — teams inside an organization, such as a project team or workgroup.

Every flow and bit lives in exactly one place: in a specific organization or group, or at the account level. Content is not shared or inherited between organizations and groups — it stays where it was created, and it is available to the people whose permissions cover that place.

Managing organizations and groups​

From the account administration pages, administrators manage the structure as a tree:

  • Create organizations, and groups inside them. A group always belongs to an organization, so at least one organization must exist before groups can be created.
  • Rename an organization or group at any time.
  • Archive an organization or group that is no longer needed. Archiving an organization also archives every group inside it. Archived items can be restored later.

Names must be unique among neighbours: two organizations in the same account cannot share a name, and neither can two groups under the same organization.

Archiving a place does not remove anyone from the account — people keep their account membership even when an organization or group they were assigned to is archived.

Managing people​

The account's user management page lists everyone in the account with their account-level role and status. From there, administrators can invite new people, change roles, assign people to organizations and groups, and deactivate or reactivate them. A reactivated person returns with basic membership only, so any roles they previously held must be granted again.

The companion article on inviting users, roles, and permissions covers this in detail, including how permissions inherit downward from the account through organizations to groups.

Account-level settings​

Administrators control a small set of account-wide options:

  • Whether organizations and groups can be created. Separate settings gate each level of the structure, so you can keep an account flat if you prefer.
  • Flow review. An optional review step for flows. When enabled, new flows start as drafts and go through review, where someone with Admin or Edit access approves or rejects them. When the setting is off (the default), new flows are approved immediately.

Settings defined at the account level apply across all organizations and groups, unless a specific organization or group has its own value for a setting that supports one.

The working context​

People who belong to several organizations or groups choose which one they are currently working in using a context switcher in the navigation. Places where a person holds only basic membership are not offered as choices, since there is nothing they can do there. If someone's access to their selected place is removed, Floxar falls back to the account level rather than leaving them stuck.

As an administrator, keep the structure aligned with how your teams actually work: grant roles at the level that matches each person's responsibilities, and let inheritance handle the rest.

Last reviewed: 2026-07-28