An institution in FYTT allows you to manage multiple teams under one organizational umbrella. For example, a university olympic sport department might create an institution to manage all the teams it is responsible for.

Below is a description of the all the features available for institutions.


You can invite any number of managers to be a part of the institution. Institution managers can invite other managers, they have complete access to all teams under the institution, and they can perform any action within those teams.


Each team under an institution is an independent entity with its own separate roster, calendar, programs, etc. Team coaches, trainers, and athletes only have access to the teams they have been explicitly invited to.


Each institution maintains a database of programs, sessions, workouts, exercises, KPIs, and KPAs that are available for use by all teams within the institution. This enables you to prescribe training across your various teams from a common library of content.


Teams can enable the "private database" option to maintain a team-specific database of programs, sessions, workouts, exercises, KPIs, and KPAs. (You can toggle this option in the team's settings.) With this option enabled, the team still has access to all the institution-level data, but it also has the ability to create its own data that are only available within that team's context.


Exercise metadata (descriptions, videos, KPI derivatives, etc.) at the institutional level are applied to all teams by default. If both the team and the institution have data for the same exercise, the team's settings will override the institutional settings.


If a team opts for a private database, you must select which KPIs you want to use for the team. Only your selected KPIs will be shown when building workouts and tracking athlete data.


Similar to KPIs, once a team turns on the private database setting, you need to select which KPAs you want to use for the team.

Did this answer your question?