Seats and members

Everything on the dashboard Team page, and who is allowed to press it.

Where it is

Team appears in the dashboard sidebar under the heading Organization, at /dashboard/team. It is hidden unless your account belongs to an organization.

An organization is created by CADABRA when the Enterprise agreement is set up, with one named owner who must already have a CADABRA account. There is no self-serve way to create one. Enterprise requires a company email.

The page holds up to six cards. Every member sees the organization name and the Seats used and Members counts. Admins additionally see the Members table, Activity, and organization usage. Directory sync, Seats and Single sign-on render for the owner only.

The Members table has four columns: Member, Role, Add-in (the CADABRA version that account last reported, or "Not installed"), and Usage (30d), which is a rolling 30 days rather than the billing period.

What each role can do

Three roles. The owner is always an admin as well, and there is exactly one owner.

ActionMemberAdminOwner
See the member list and organization usageNoYesYes
Add a memberNoYesYes
Remove an ordinary memberNoYesYes
Remove an adminNoNoYes
Grant or revoke adminNoNoYes
Release another member’s workstationNoYesYes
Read the activity logNoYesYes
Change the seat countNoNoYes
Configure single sign-onNoNoYes
Generate or revoke a directory sync tokenNoNoYes
Transfer ownershipNoNoYes

Adding a member

  1. 01

    They sign up first

    They create a CADABRA account with the address you are going to add. Any plan, including Free, is fine.

  2. 02

    Type the address

    On the Members card, the field marked member@company.com sits next to Add member. Both are shown to admins only.

  3. 03

    Press Add member

    The row appears immediately with the role Member. The confirmation reads "Added name@company.com. They were not emailed, so let them know they now have access."

  4. 04

    Tell them

    Their account moves onto the organization plan the moment they are added, so their next sign-in in the panel carries Enterprise entitlement, including Drawings Mode. Nothing needs reinstalling.

When adding is refused

  • "No CADABRA account with that email yet. Ask them to sign up first, then invite again." The address has never signed up. The lookup is on the exact address, so a personal address they signed up with will not match the work address you typed.
  • "That user already belongs to another organization." An account is in one organization at a time. It has to leave the other one first.
  • "Your organization has used all of its seats." Every seat is occupied. Buy seats, or remove someone.

Adding someone straight in as an admin is possible through the API only, and only for the owner. The dashboard always adds an ordinary member, and the owner promotes them afterwards.

Changing a role

Role controls appear on a member row for the owner only, and never on the owner’s own row.

  • Make admin confirms with "Admins can invite people, remove ordinary members, and manage the organization. Only you, as the owner, can take it back."
  • Revoke admin confirms with "They stay in the organization as an ordinary member and keep their plan."
  • Make owner confirms with "They take over control of who is an admin. You stay an admin, but from then on only they can undo this."

Three rules the server enforces whatever the interface offers: the owner is always an admin and cannot be demoted ("The organization owner is always an admin. Transfer ownership first."), the last remaining admin cannot be demoted ("Cannot demote the only organization admin."), and the owner cannot be removed ("The organization owner cannot be removed. Transfer ownership first.").

Removing a member

Remove confirms with "They lose access to the organization and their account drops to the Free plan, whatever plan they had before joining."

That is literal. The account is not deleted, but its plan is set to free, so Drawings Mode, the higher model levels and the organization allowance stop at once. A personal subscription they had before joining is not restored; they resubscribe from Billing.

The seat is freed immediately. The last admin cannot be removed ("Cannot remove the only organization admin.").

Releasing a workstation

Release device on a member row releases every active workstation on that account, not just one. It confirms with "CADABRA stops working on the machine they last used, and they can activate it on a new one. Use this when a computer is replaced or gone."

Members do this for themselves from Workstations. An admin needs the button when the machine is gone and the person cannot reach it.

Buying seats

The Seats card is Enterprise and owner only. An admin who is not the owner sees the count and the line "Only the owner can add seats."

  1. Press Add seats. The form has one field, Total seats, which is the new total rather than the number you are adding, under the note "Seats come down at renewal, not mid-term."
  2. Press Get a price. The quote is computed against your contract term and its negotiated seat rate.
  3. Press Confirm. It finishes with "Seats updated to N. The prorated amount appears on your next invoice."

The line shown before you confirm is exactly this:

The confirmation an owner sees before a seat change

N more seats: $X for the rest of the term, added to your next invoice,
then $Y a year from <renewal date>.

How $X is derived

prorated = added seats
         x the seat rate on your contract, per year
         x seconds left in the term
         / seconds in the whole term

Activity

The Activity card is visible to admins, and only once something has been recorded. It lists the 25 most recent changes, newest first, in two columns, Change and When. Times are relative up to a week ("Just now", "14m ago", "5h ago", "3d ago") and a date beyond that.

It records organization changes, not prompts or CAD work:

  • added, removed, made an admin, revoked admin, made the owner
  • changed seats, with the old count, the new count and the prorated amount
  • released the device, naming it
  • created, switched or turned off a drawing standard, and deleted a file
  • changed the SCIM token, issued or revoked
  • configured single sign-on with the issuer, verified a domain, turned single sign-on off

The actor is a person’s name or email, the literal SCIM when a directory sync did it, or SSO (org:<id>) when a first sign-in provisioned the account.

Next

Stop maintaining the list by hand. Single sign-on creates the account on first sign-in, and directory sync adds and removes members from your identity provider.