CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken in a support session, so the top of the screen shows a bar you will not see. Each grey box marks a screenshot still to come.
What the three team grades are
CupixWorks has three grades at team level: Super Admin, Admin (Team Admin) and Member (Team Member). They are the widest scope in the product — a grade held here reaches every workspace and every project underneath it.
Two spec sheets agree on this list. CWV5-AC-11 gives the grades, and IA5-SET-AC-14 states the same vocabulary from the invite dialog's side: “Team — Super Admin · Admin · Member”.
Super Admin is displayed but never offered
There is exactly one thing that makes Super Admin different from every other grade: you cannot grant it. It is shown wherever someone holds it, and it appears in no dropdown — not in the invite dialog and not in Change Permissions.
IA5-SET-AC-14 is explicit about why: a grade that can be handed out is not the top of the tree. Super Admin moves only by transfer.
Admins reach downward without being on the list
A Team Admin or Super Admin can open every project below them without appearing on that project's member list. So a project's roster is not the same thing as everyone who can see the project.
This is worth knowing before you audit access. If you are checking who can reach a project, the project's own member list is only part of the answer.
Nobody can leave a scope without an administrator
Removing, deactivating or demoting the last administrator of a scope is not refused — it is interrupted. A Transfer Admin dialog asks you to name a successor first, and then promotes the successor and completes your original action in one step.
Three things about that dialog are worth stating plainly, all from IA5-SET-AC-17:
Demotion counts. Super Admin down to Admin goes through the same rule where it would leave the seat empty — a demotion that empties the seat has the same outcome as a removal.
Promotion and removal are one action. Doing them separately would leave a window with two administrators or none, and an interruption in the middle would leave the team in whichever of those states it had reached.
Cancel abandons your original action too. Declining to name a successor is not agreement to remove the administrator anyway.
The rule fires only on the last one. With two administrators present, removing one is an ordinary removal.
Removing a member and deactivating one are different
Removing takes the person off the scope. Deactivating keeps their record and their permissions and suspends their access; reactivating returns it. Both are confirmed first, and removal is presented as the destructive one.
A deactivated member stays in the permission matrix with their permissions shown. The matrix answers how permissions are distributed in this team, not who can act today — a permission that disappeared from view when someone was suspended would make the matrix unreliable for exactly the audit it exists for.