Inviting users, roles, and permissions
Every person in a Floxar account has a permission level that controls what they can see and do. This article explains what each level means, how new people join an account, and how access flows through the account's organizations and groups.
Permission levels
Floxar uses four permission levels, plus a basic membership status:
- Admin — Full management of the account: account settings, user administration, and full access to all content.
- Edit — Create and change content, including flows and bits.
- Engage — Use content: start and work through flows, filling in the interactive elements (forms, checklists, and similar) along the way.
- View — Read-only access: see content without changing or running it.
- Member — Belonging without access. A Member appears in the account's user list but cannot see or do anything until a role is granted. This status is normal for people whose real role is granted on a specific organization or group, and for people who were just added and are waiting for a role.
A higher level always includes the abilities of the levels below it — anyone with Edit, for example, can also do everything Engage and View allow.
Inviting someone to your account
Administrators bring new people in by invitation:
- An administrator creates an invitation with the person's email address and a permission level — Admin, Edit, Engage, or View. If no level is chosen, View is used. The invitation can also target a specific organization or group, so the person's access starts exactly where it should.
- The person receives an invitation email with a link.
- When they create their Floxar sign-in using the same email address the invitation was sent to, they join the account automatically with the assigned access — no extra approval step.
While an invitation is still pending, administrators can resend it or revoke it. Once accepted, an invitation can no longer be revoked; manage the person's access directly instead.
Administrators can also add someone before that person has ever signed in, by entering their email address in the account's user management area. When the person later creates their Floxar sign-in with the same address, their access is already in place.
Where a role applies
An account can contain organizations (major divisions such as departments), and each organization can contain groups (teams). A permission level can be granted at any of these levels:
- on the whole account,
- on one organization,
- or on one group.
Administrators assign people to organizations and groups, and set their role there, from the account administration pages.
Permission inheritance
Permissions flow downward. A role granted on the account applies to every organization and group inside it, and a role granted on an organization applies to every group inside that organization.
Grants only ever add access:
- When several grants apply to the same place, the most permissive one wins.
- You cannot reduce inherited access by granting a lower level further down. Someone with Edit on the whole account keeps Edit everywhere, even if they are also given View on one group.
A common pattern: a person is a Member at the account level and has Edit on a single group. They can work only inside that group — and the account's user list shows them as "Member", because that is their account-level status.
Changing and removing access
Administrators can change a person's role or deactivate them from the account's user management area. Deactivating removes access but preserves everything the person created. If they are reactivated later, they return with basic membership only — any roles they previously held must be granted again.
You cannot change your own role, deactivate yourself, or remove yourself from the account; another administrator has to make those changes. This protects accounts from accidental lockouts.
Finally, a person can belong to more than one Floxar account, with different permission levels in each. Access and content never carry over between accounts.
Last reviewed: 2026-07-28