Teams and organizations
Membership, invitations, roles, shared credits, and the Enterprise controls — SSO, SCIM, and custom roles.
Organization controls are role-gated, and Enterprise organizations can carry a customized role catalog. If a control is missing, confirm your active organization and role before assuming the action failed. See Roles and permissions.
An organization groups people under one license, one credit pool, and — where configured — shared integrations and policies. Your account can belong to more than one; the picker in the header decides which one is active, and every permission question is answered against that one.
For who can do what, see Roles and permissions. This page is the mechanics.
Creating one
An individual with a self-service subscription can create an organization to move onto a team plan. The creator becomes the owner. Team plans carry a seat minimum, so the first thing checkout asks for is how many seats you are buying.
Inviting people
Open Members
Members in the left navigation. Admins and owners see it; members do not.
Invite by email
Search for or type the address and pick the role they should hold. Get the role right at this point — it is what they land on.
They accept
The invitation goes to that address. Until they accept, the member list shows them as Pending: the account exists, has no password, and cannot sign in.
Confirm
After acceptance, check they appear under the right organization with the right role.
Invitations expire. The member list shows expired ones and offers Resend invite; Revoke invite withdraws one that should not have been sent. A revoked invitation cannot be accepted afterwards.
If your organization has an auto-join domain policy, people signing up with your email domain may join without an invitation. That is a deliberate setting, so check it before assuming an unexpected member is a mistake.
Managing members
The member list carries each person’s role, status, and last activity. From it an admin can change someone’s role, deactivate an account, or remove the membership.
Three things to know before you act:
- Only an owner can grant or revoke the owner role. An admin can promote someone to admin, not to owner.
- Deactivating is not removing. A deactivated member keeps their membership record but cannot sign in. It is the reversible option.
- Removing can cut access to organization resources, including documents on the organization drive. Confirm any handoff first.
Shared credits
On a team plan the credit allowance is pooled: the monthly grant is calculated from the seat count and drawn down by whoever uses it. One person running many RealityCheck passes spends the same pool everyone else draws from.
The credit balance and the ledger are visible on the usage screen, and owners and admins can buy top-up credits when the pool runs low. Monthly credits are consumed before purchased top-ups, so a top-up you paid for is not burned while a free monthly grant sits unused. See Billing.
Shared drives and policy
Document retention is the organization-wide policy that lives in Settings: the ceiling on how long uploaded documents are kept, which is one hour by default and seven days at most. See Settings and Plans and licenses.
Organization drive sharing is not currently exposed as a control. Members connect their own drives from Integrations.
Enterprise controls
Enterprise organizations get identity capabilities the other tiers do not:
Single sign-on
Sign-in through your own identity provider, so BriefCatch access follows your directory.
SCIM provisioning
Accounts created, updated, and deactivated automatically from the directory. Joiners and leavers stop being a manual list.
Custom roles are not Enterprise-only. Any organization admin can open Roles in the left navigation and define roles beyond member, admin, and owner, built from the same permission vocabulary. Which permissions a role may be granted still depends on what your plan includes. See Roles and permissions.
Setting these up is covered in Identity management, which also explains the order they depend on: verify a domain, connect SSO, then enable SCIM.
With SCIM in place, the member list becomes a reflection of your directory rather than something you edit directly. Removing someone from the directory group is what removes their BriefCatch access; deactivating them by hand in BriefCatch will be undone at the next sync.
Leaving or being removed
Losing a membership means losing whatever the organization’s license granted. Documents you stored personally stay with your account; documents on the organization drive do not travel with you. If you hold another license — your own individual subscription — the account falls back to that.
Related
- Roles and permissions — what each role can do
- Identity management — SSO, SCIM, and automatic membership
- Subscription — seats and plan changes
- Usage and credits — pooled team credits