Skip to main content

How roles and capabilities work in 360Player

Understand how Admin and Staff roles, group inheritance, and top-level capabilities determine what a user can do.

Overview

On the 360Player platform, two roles can manage others: Admin and Staff. A third visible role, Player, covers users who participate but don't manage. Roles are assigned per group, and they're inherited down the group tree.

Admin

  • Can create, update, and view all records within their group and its subgroups.

  • Has access to Settings and user management.

Staff

  • Can create, update, and view all records within their group and its subgroups.

  • Cannot view or manage users or settings.

Player

  • Can view their own activity, register for events, and interact with their group.

  • Cannot manage other users or settings.

Example:

  • An Admin can invite new teammates, manage their access, and create calendar events.

  • A Staff member can create calendar events, but cannot invite or manage users.

Roles are per-group. A user can be an Admin in one team and a Player in another. There is no single "global role" toggle. Need to change a role? See Change a user role.

The organization tree

Roles in 360Player are inherited. If you are assigned a role in one group, you automatically have that role in every subgroup below it.

  • If an Admin is in Academy, they are also an Admin in Boys, Girls, and every group beneath them (e.g. G15, G14).

  • If an Admin is only in Girls, they are an Admin in G15 and G14, but not in Boys or Academy.

To add a user to one or more groups (and pick their role in each), see Add users to groups.

Top-level groups and capabilities

The top-level group of an organization includes features that don't exist in subgroups. At this level, additional tools become available:

  • Payments

  • Registrations

  • Scheduling

  • Relation Manager

Being Admin or Staff doesn't automatically grant access to these areas — they're gated by a separate capability system. You manage capabilities in Settings → Users.

⚠️ Important: Any Admin at the top level can assign capabilities to other users. Choose top-level Admins carefully.

Assign capabilities to a user

  1. Open the top-level group of your organization.

  2. Go to Settings → Users.

  3. Find the user in the list, click the three-dot menu, and choose Capabilities.

  4. Tick the capabilities you want to grant, then save.

By default, a user who is Admin or Staff at the top level can see the Management tab; granular tools (Payments, Registrations, Scheduling, Relation Manager) require explicit capabilities on top.

What each capability unlocks

Payments

  • Manage products, prices, tax rates, and discounts.

  • Create and update invoices, subscriptions, and installments.

  • Access payment reports and individual payment data.

Note: This does not allow changing another user's billing details (unless the user is also an Admin).

Registrations

  • Create and manage registration forms.

  • View form submissions and registration reports.

Scheduling

  • Manage resources, locations, and scheduling templates.

  • Publish schedule templates and create subgroup events.

  • Manage bookings.

Relation Manager

  • View and update parent–child connections.

  • Create new connections between accounts.

Custom roles

In addition to the built-in Admin, Staff, and Player roles, top-level Admins can define custom roles with their own capability sets. Custom roles let you express things like "treasurer" or "registrar" without granting full Admin rights.

  • Go to Settings → Roles at the top level.

  • Click Create new, give the role a name, and toggle the capabilities you want it to include.

  • You can mark a custom role as the default for a role type — new users assigned that type get the custom capability set automatically.

Custom roles inherit and behave like built-in roles otherwise. They're assigned the same way (see Change a user role).

Related how-tos


Ongoing updates

We are continuously adding new capabilities so organizations have more granular control over user access. This article is updated as new features are introduced.

Did this answer your question?