Roles and Access for Schedule Management

Schedule items (games and events) can be created from a number of different levels in TeamSnap. In this article, we will go over where scheduling can be done and who can edit and adjust games and events depending on their level of access. For more information on member types and how to grant access check out the Member Types article. 

Scheduling at the organization (org) level requires you to create locations at that level. Locations created at the org level will appear and be available for all divisions and teams within your organization. All scheduling requires locations. You can not have an event or a game in space, it needs to happen somewhere even if that somewhere is TBD. If you create locations at the org level (commissioner access required), anything scheduled for those locations will populate on the org calendar. If locations are not created at the org level and your team owners and managers (or divisional commissioners) create their own locations, events scheduled on those locations will not populate on the org calendar. Here's the breakdown of who can do what, and where:

Commissioner Scheduler, League Level, Division Level, Team Level Can Edit, Adjust and Alert from All Levels
Divisional Commissioner Division Level, Team Level (within Division) Can Edit, Adjust and Alert from Division and All team within Division. Cannot edit or adjust events created at the League Level.
Team Owner/Manager Team Level Can Edit, Adjust and Alert from Team Level. Cannot edit or adjust events created at the Division or League Level.
Roster Member N/A N/A

Commissioners have the highest editing access. If a commissioner creates an event at the org level, only commissioners will have access to manage and edit that event. Meaning a team admins (owner or managers) will not be able to change the time of  that  event on their own team level. If a commissioner creates an event at the team level, team admins will be able to edit that event. 

Did this answer your question? Thanks for the feedback! There was a problem submitting your feedback. Please try again later.