Roles and Permissions
The table below illustrates the permissions of roles which can manipulate organizations and their membership.
| Action | Organization Owner | Organization Member |
|---|---|---|
| Add Organization Owner | x | |
| Add Organization Member | x | |
| View Organization Members | x | x |
The table below illustrates the permissions of roles which can manipulate groups and their membership.
| Action | Organization Owner | Group Owner | Group Member |
|---|---|---|---|
| Create Group | x | ||
| Rename Group | x | x | |
| Set Group Priority | x | ||
| Delete Group | x | x | |
| Add Group Owner | x | x | |
| Remove Group Owner | x | x | |
| View Group Owners | x | x | x |
| Add Group Member | x | x | |
| Remove Group Member | x | x | |
| View Group Members | x | x | x |
The table below shows group roles and their ability to manipulate group and user scoped resources such as secrets, storage volumes, and compute resource definitions.
| Resource | Action | Group Owner | Group Member |
|---|---|---|---|
| Group Scoped Resource | Create | x | |
| Update | x | ||
| Delete | x | ||
| Access | x | x | |
| User Scoped Resources | Create | x | x |
| Update | x | x | |
| Delete | x | x | |
| Access | x | x |
Node provisioners are defined by cluster administrators in central config. They cannot be created, updated, or deleted through the organization hierarchy. What organization and group roles control is which of the cluster’s node provisioners their users may schedule onto, through compute policy.
| Action | Organization Owner | Group Owner | Group Member |
|---|---|---|---|
| View node provisioners | x | x | x |
| Set organization compute policy | x | ||
| Set group compute policy | x | x |
An organization’s compute policy grants a set of node provisioners to the whole organization. A group owner can then narrow that set for their group. A group can only be granted provisioners the organization already holds.
A workflow definition is a named Fuzzfile stored on the server and kept as numbered revisions. It belongs to the group that was selected when it was created, and it is not visible from any other group. Workflow definitions are currently available through the API only.
| Action | Group Owner | Definition Creator | Group Member |
|---|---|---|---|
| Create workflow definition | x | x | |
| List and view workflow definitions | x | x | x |
| List and view revisions | x | x | x |
| Copy a workflow definition | x | x | x |
| Save a new revision | x | x | |
| Rename or change the description | x | x | |
| Delete workflow definition | x | x |
Any member of the group can read a definition and copy it into a new one that they own. Changing or deleting a definition is limited to group owners and to the user who created it.
A name is unique within its group and case-sensitive. Deleting a definition removes it from the list and frees its name for reuse. Its revisions remain readable by ID.
In the next section, we will walk through an example which ties the concepts of organizations, groups, and users together.