Skip to main content

Inviting and seats

You add people to your organisation by email invitation, and on paid plans some tiers are licensed per seat. This page covers the invite flow, how seats are counted, and what happens when a tier is full. For a first-run walkthrough see Invite your team.

Inviting a member​

On the Members & roles page (Admin area), enter the person's email, pick their role from the tier dropdown, and press Invite. Requires the Administrator tier (T7) or above.

  • The invitee receives an email with a link to join your organisation.
  • Until they accept, they appear as a greyed pending row in the member list with an Invited badge and the tier you chose.
  • When they accept, they land in the organisation with that role already assigned -- no second step.
  • A second invite to an address that already has one pending is refused.

To withdraw an invitation, press Revoke on its pending row. The invitation stops working and its seat is freed immediately.

How seats are counted​

Depending on your plan, some tiers are billed per seat. For each such tier the Members & roles page shows a usage bar like Builder 45/50: seats in use against seats allowed (seats included in your plan plus any you have bought).

Two things occupy a seat:

  • an active member assigned to that tier, and
  • a pending invite into that tier.

Counting pending invites is deliberate: a burst of acceptances can never push you past the limit, because the seats were held from the moment the invites went out. Revoking an invite releases its seat; an acceptance simply converts a pending seat into an active one.

Tiers that are not billed on your plan are uncapped -- invite freely.

Hitting a seat limit​

When you invite (or reassign) someone into a full tier, Flynt does not fail silently. You get a consent prompt: all seats at that tier are in use, and adding one more adds the seat price to your monthly bill. What you can do next depends on the organisation's over-limit policy:

  • Owner only -- only the Owner can add seats. Admins see that the tier is full and must ask the Owner.
  • Admins request, owner approves (the default) -- the prompt files a seat request. The Owner sees pending requests on the same page and approves or denies them; approving applies the purchase immediately, after which the invitation can be sent.
  • Admins self-serve -- the prompt buys the seat and retries the invitation in one step. The Owner can set an optional cap on how many extra seats admins may add beyond what the Owner last set.

The Owner changes the policy in the Over-limit policy panel on the Members & roles page. Requires the Owner tier (T8); changing the policy is a billing control.

Seat management​

Owners see a Seat management panel listing each billed tier with its price, seats in use, seats included, and the period's peak. Requires the Owner tier (T8); admins under the self-serve policy can raise counts as described above, but reductions are always Owner-only.

  • Raising the purchased count takes effect (and bills) immediately.
  • Lowering it is refused below the seats currently in use -- members plus pending invites. Remove or reassign users first, then reduce.
  • A seat stays on your bill even if the person occupying it leaves. Removing a user frees the slot for someone else; it does not shrink the bill until you explicitly reduce the purchased count here.

How reductions and mid-month additions are charged is covered in Plans and billing.

Good to know​

  • Every invite, revocation, seat change and policy change is recorded in the audit log.
  • Roles and what each tier can do are described in Members and roles.