Teams
Teams categorise users in groups, using their Unity ID (i.e. their email).
If a user is signed in and their email is listed as a user of a Hats Team, they are part of that Team. This happens as soon as the Editor is launched. Users can then jump to other Teams if they so wish.
Build on Hats
In addition to using Teams to put users into workspaces, you can also build tools that modify their appearance or behaviour depending on the active Team.
Managing Teams
By going to Project Settings > Hats and scrolling down, you can see the Teams section of Hats. Here you can see which Team you're currently part of.
By default, new users are in "No Team", meaning the Editor is not affected by Teams. After you have created Teams you can join a different one, or even return to No Team.
The Team Catalog
In Hats, available Teams are contained in a catalog ScriptableObject.
This asset is created automatically in 📂 Assets/Settings/Hats the first time the project is loaded. After this, you can add Teams to the catalog by simply selecting the SO and adding to its Teams list:
Individual Teams are sub-assets of the Catalog, and they are automatically managed for you.
Setup a Team
As you add Teams to the Catalog, you can change their properties
Team Workspace
Each Team can have a workspace associated with it. This workspace is applied as soon as the editor starts, and cannot be switched unless one where to switch Teams.
Differently from personal workspaces, Team workspaces are enabled by default for all users who are part of the team. You can think of Team workspaces as an underlying layer: first the Team workspace is applied, then any active personal workspace is applied on top.
Members
Members of a team are emails (Unity ID emails) that are associated to the team. If a user is logged in as that Unity ID upon launching the editor, the team becomes their team and its workspace (if present) is enabled.
Member emails can be tweaked manually, or you can add yours to a team by switching to it.
Last updated