User Roles & Permissions: TeamSnap for Business
Attention: This article is for organization administrators on TeamSnap for Business. Check your version at the bottom of your organization screen.
This article explains the TeamSnap user roles and permissions for each role.
In this article
General User Types
You may see terminology used to describe different users. These are ways we describe types of users and are not official roles that are set for user access in TeamSnap products.
Member: This refers to any person who has a TeamSnap account, including players rostered to a team, non-player members, player contacts, and all administrative members who have accepted an invite to access a team.
Registrant: This refers to the person who is filling out a registration form to register participants for a program or event.
Participant: This refers to people that have been registered by a registrant and have not been assigned to their teams yet.
Staff roles and permissions are added under the Staff tab.
Organization Owner: This role is auto-assigned to the main account contact for TeamSnap upon account creation. This role is tied to the billing of the organization's TeamSnap account plan and is the only TeamSnap account with the ability to pay for the organization's account subscription and grant the organization admin role to other members. Currently, there can only be one designated organization owner per organization. Organization owners have full administrative access across the entire organization including the ability to grant the admin role to other members. There can only be one organization owner per organization.
Organization Admin: Assigning a staff member the Organization Admin role grants them access to all areas of the organization account plus full administrative permissions to manage information and settings. There can be as many organization admins as desired.
Program Admin: Assigning a staff member the program admin role grants them access to only the specific programs selected, with full administrative permissions to manage information and settings within their designated program(s). This role may access the Financials tab but does not have access to financial settings within their assigned program(s). There can be as many program admins as desired.
Program Coordinator: Assigning a staff member to the program coordinator role grants them access to only the specific programs selected, with limited administrative permissions to manage the program and view registration information. This role does not have access to the Financials, Invoicing, or Registration tabs within their assigned program(s). There can be as many program coordinators as desired.
Division Coordinator: Assigning a staff member to the division coordinator role grants them access to only the specific divisions selected, with limited administrative permissions to manage the information and settings within their designated division(s). This role does not have access to the program or season level unless given additional roles for those product areas. There can be as many division coordinators as desired.
Team Administrative Roles
Team administrative roles are added under the Members tab.
Team Owner: Assigning a member as the owner of a team grants them access to all areas of the team site, including the ability to grant the manager role to other members, to set up the deposit account for team-level invoice payments from members, plus all the permissions available to team managers and full administrative permissions to manage information and settings. There can only be one team owner assigned per team.
Team Manager: Assigning a member as the manager of a team grants them access to all areas of team site, with full administrative permissions to manage information and settings within the team. This includes managing the schedule, roster, and creating invoices. There can be as many team managers as desired.
Non-administrative roles are often referred to as members or roster members in our help articles and communications.
Player: This is the default role given to any person added as a non-administrative roster member in a TeamSnap product. Players are able to mark availability for games and events, complete health checks, send and receive messages, etc. They have no administrative capabilities.
Contact: Contacts are a player's parent or guardian, family member, etc that is added under a player's roster profile. Contacts can be invited to access the player's team.
Non-Player: Roster members who need to be excluded from a team's availability count can be designated as non-players. This role can be set in addition to an administrative role if desired. This is typically used for members like a coach, team mom, team manager, etc.
User Roles and Their Permissions
|Permissions||Player or Contact||Team Manager||Team Owner||Division Coordinator||Program Coordinator||Program Admin||Org Admin||Org Owner|
|Manage personal account and profile information|
|Receive team communication||N/A||N/A||N/A||N/A||N/A|
|Set team event availability|
|Subscribe to team schedules *must be added to team|
|Submit invoice and registration payments|
|Manage team schedule(s)|
|Manage team roster|
|Manage team tracking items, statistics, invoicing|
|Grant/revoke team manager role|
|Manage program members|
|Manage program schedule|
|Manage program invoices and registration|
|Manage organization program(s)|
|Manage organization staff & members|
|Manage organization invoices and registration|
|Send/receive organization messages|
|Manage organization settings|
|Grant/revoke program administrator roles|
|Grant/revoke organization administrator roles|
|Manage TeamSnap plan account billing|