Skip to Content

Roles

A role is the access you assign when you add a team member. It appears as a badge on their card on the Members page.

Roles versus user type

When you invite or create a team member, ACCESS has two required fields. You must choose User Type first. The role list loads after that.

FieldWhat it is for
User TypeChosen first. Helper: Select a user type to load its available roles.
RoleChosen second. Only the roles for that user type appear

A user type is the grouping. A role is the access that appears on the person’s card after you add them.

User types

On Invite a new member, open User Type to see the list.

Invite a new member with the User Type list open

The User Type options are:

  • Admin
  • Staff
  • Trainer

Roles for each type

After you pick a user type, open Role.

When User Type is Staff, Role can be MANAGER or STAFF:

Invite a new member with User Type Staff and Role list showing MANAGER and STAFF

When User Type is Trainer, Role shows TRAINER (this example is on Create a new member):

Create a new member with User Type Trainer and Role TRAINER

The Role list for Admin is not in these screenshots. Use the Role dropdown after you select Admin.

Roles shown on the Members page

These role badges are visible on team member cards:

RoleWhere it appears
AdminRole badge on a member card
StaffRole badge on a member card
TrainerRole badge on a member card

There is no Owner badge on the Members cards.

Roles versus permissions

  • A role is the named set of access you assign (for example Trainer or Staff).
  • A permission is a single action or area, such as whether someone can raise or decide on a request.

Fitnez Studio has an Approval Requests page where managers review requests raised by the team. That is one way limited roles can still get work done. See Approval Requests.

There is no screenshot yet of a permission list for Staff, MANAGER, STAFF, or TRAINER. The ADMIN permission set is documented on Checking What You Are Allowed to Do. Approvals → Permission Requests is documented on Approval Requests.

Why someone may not see a button

If a team member cannot see an action that you can see, their role may not include it. A button can also be unavailable for another reason — for example Invite Member stays unavailable until required fields are filled.

Do not assume every hidden or disabled button is a permissions issue.

Last updated on