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.
Allowing organizations and groups
Two account settings decide whether new organizations and new groups can be created. An administrator changes them on the Overview tab of Account Settings. Floxar applies them to every create, whoever or whatever makes it: a person in the app, an integration calling the API, or an AI client. While organizations are turned off, a request to create one is refused with a message that names the setting; the same goes for groups. A group also needs an active organization in the account when it is created. The settings only stop new ones: existing organizations and groups stay as they are, and an archived organization can still be restored.
An AI client connected with an administrator's access can create organizations and groups and change these two settings. When it is refused because a setting is off, it tells you which setting to change. If it retries a create after a lost answer, it gets back the organization or group it already made instead of a second one.
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.
- Require review before publishing new flows. An optional review step for flows. When enabled, new flows start as drafts and go through review, where someone with Edit access or above approves or rejects them. When the setting is off (the default), new flows are approved immediately.
- Require approval to publish a bit's draft and Require approval to publish an earlier version again. When on, publishing a bit's draft, or putting one of its earlier versions back into production, creates an approval request instead of going live. Both are off by default.
- Agents may approve promotions. Whether registered agents may approve and reject flow reviews and bit promotions, as people with Edit access can. On by default; turn it off if a person should approve everything that goes live.
These four are on the Authoring tab of Account Settings, under Review and Approval, and apply to the level selected in the context switcher, so an organization or group can differ from the account. Only administrators can change them, because they decide who may put content into production. See Versions, test accounts and promoting content.
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.
Production or test
On the Overview tab an administrator marks the account as a production account or a test account. It is a label only: it changes nothing about how Floxar behaves, and a test label is never a reason for anyone, a person or an AI client, to treat the account's content as disposable. A test account shows a banner so everyone knows where they are.
An AI client connected with an administrator's access can set the same label. It states the value it read along with the one it wants, so a change made in the meantime is not overwritten; asking for the value the account already has changes nothing.
Closing reasons
Closing reasons are the dispositions people choose when they complete or abandon a trail. Administrators set them for the account, for an organization or group, or for a single flow, on the Closing reasons tab; a flow's own set replaces its scope's set rather than adding to it. An AI client with Edit access can create them too, and if it retries a create after a lost answer, it gets back the reasons it already made instead of a duplicate set.
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-10-21