Hats - Workspaces and Teams

🔗 Documentation | Discord | Unity Forums | Support Hats enables the concept of workspaces in Unity. ⛑️ Workspaces Workspaces are a bit similar to layouts – but way more powerful! By switching workspaces, the Editor can be made to load a specialised layout, open one or more scenes, lock objects or folders, switch build target, change the Game View aspect, set filters in the Hierarchy and Project view, and more. Third-party tools can be made to work differently. And you can create custom behaviour as a result of a workspace switch. You can switch to a workspace at any moment to customise the appearance or the behaviour of the Editor according to the task you are performing. 👉🏻 For instance: One could have workspaces for Level Design, Cinematics, Testing... - When the Level Design workspace becomes active, it loads the main game scene and locks the GameObjects that shouldn't be edited. - When the Testing workspace is activated, it loads the Initialisation scene, so the developer can immediately enter Play Mode and test the game from the main menu. - When Cinematics loads, it opens the cutscenes scene, switches the Game View to a cinematic aspect ratio, and loads the Timeline editing layout. Hats can make the Unity Editor more streamlined, so you get focus – whichever hat you're wearing at the moment 🎩 But that's not all... 🧰 What a Workspace can do Hats ships with a set of built-in rules that can be combined freely: - Load an Editor layout or a Scene Overlays layout - Open one or more scenes, or a Prefab - Hide or lock GameObjects (by tag, component, or name) and layers - Lock folders in the Project view, or select/focus a folder - Switch build target - Toggle 2D/3D mode - Set the Game View size or aspect - Apply filters to the Hierarchy or Project search - Move the Scene Camera to a saved position - Highlight specific gizmos - Disable menu items, or execute a menu item on activation 👫 Teams (optional) Teams can be used to group Editor users by 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, and that Team's workspace becomes enabled for them as soon as the Editor is launched. This allows to auto-enable a workspace for users of a certain team – useful, for example, to give designers, artists, or QA a tailored Editor right from the launch. The Teams functionality is optional; and can be turned on and off. 👷🏼‍♂️ Build your own Hats-powered tools In addition to the built-in functionalities, Hats provides a public API to query the current state of Workspaces and Teams, and to register custom rules. This allows you to create smart tools that provide a tailored experience to their users. Two samples are included to demonstrate this: a custom Workspace rule, and an Inspector that changes its appearance based on the active Team. 🈶️ CJK languages support Team and workspace names support CJK languages (中文 / 日本語 / 한국어). 📘 Documentation If you want to learn more before getting Hats, you can browse the documentation website. 💰 Save some money Hats is part of our All Editor Tools bundle. By getting that, you effectively get Hats at 25% off. If instead you already purchased Hats, you get a discount on the bundle.