> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Teams > Teams group GermainUX users and control their access to dashboards, monitored data, Session Replays, and alerts. Service `Authentication` Availability 8.6.0 or later > [card] [Team Types](#team-types) > > Business or technical visibility > [card] [Add Users to a Team](#add-users-to-a-team) > > Two ways to assign users > [card] [Business and Technical Data Visibility](#business-and-technical-data-visibility) > > How Teams limit data access > [card] [Recommended Practices](#recommended-practices) > > Team setup guidance ## Teams overview Teams group GermainUX users and control their access to dashboards, monitored data, Session Replays, and alerts. Teams make it easier to apply visibility settings to multiple users based on their responsibilities—for example, business users, application owners, support teams, or technical administrators. ## Roles and Teams Roles and Teams control different aspects of access: | Access-Control Object | Purpose | | - | - | | **Role** | Controls which operations the user can perform in GermainUX. | | **Team** | Controls which dashboards and types of monitored data the user can access. | A user may require both the appropriate Role and Team membership to access a dashboard and its underlying data. ## Team Types GermainUX supports two Team types: | Team Type | Data Visibility | | - | - | | **Business** | Designed for users who require access to business dashboards and business-level metrics. | | **Technical** | Designed for users who require access to both business and technical dashboards and their underlying diagnostic data. | The Team type affects the information available when users drill into data through Drill-through and Analysis dashboards. A user who belongs to multiple Teams inherits the Team types and dashboard access associated with all those Teams. ## View Teams Go to: **Germain Workspace -> Left Menu -> Settings → System -> Auth Settings -> Teams** The **Teams** page displays the Teams currently configured in GermainUX. ## Create a Team **1. Go to System -> Auth Settings -> Teams** **2. Click Add New Configuration** **3. Configure the Team fields** **4. Click Finish** | Field | Description | | - | - | | **Name** | Unique name used to identify the Team. | | **Type** | Determines whether the Team provides Business or Technical data visibility. | | **Users** | Users who belong to the Team. | Choose a name that clearly identifies the Team’s function, business unit, application, or data-access scope. ## Add Users to a Team Users can be added to a Team in either of the following ways. ### From the Teams Page **1. Go to System -> Auth Settings -> Teams** **2. Select the Team** **3. Add the required users** **4. Save the Team** ### From the Users Page **1. Go to System -> Auth Settings -> Users** **2. Select one or more users** **3. Use the available bulk action to update their Roles and Teams** **4. Assign the selected users to the required Team** **5. Save the changes** Users can belong to more than one Team. Their resulting access combines the dashboard and data visibility provided by all assigned Teams. ## Grant Dashboard Access to a Team A GermainUX administrator can specify which Teams are authorized to access each dashboard. When configuring dashboard visibility: **1. Select or edit the dashboard** **2. Identify the Teams that require access** **3. Add those Teams as dashboard owners or authorized Teams** **4. Save the dashboard** **5. Test access with a user from each Team** Only grant access to Teams whose members require the dashboard and its underlying data. ## Pinned Dashboards Teams can have pinned dashboards associated with them. When users are added to a Team, they inherit the dashboards pinned for that Team. This provides Team members with immediate access to the dashboards most relevant to their responsibilities. If a user belongs to multiple Teams, the user may inherit pinned dashboards from each Team. ## Business and Technical Data Visibility Team type affects the level of information users can view when investigating a metric. | Investigation Level | Business Team | Technical Team | | - | - | - | | Business dashboards and metrics | Available when authorized | Available when authorized | | Technical dashboards and metrics | Restricted | Available when authorized | | Drill-through business information | Available when authorized | Available when authorized | | Technical diagnostic details | Restricted | Available when authorized | | Analysis data | Limited to the authorized business view | Includes authorized business and technical details | Dashboard access and Team type work together: access to a dashboard does not necessarily grant access to every underlying technical detail. ## Edit a Team **1. Go to System -> Auth Settings -> Teams** **2. Select the Team** **3. Update its name, type, or users** **4. Save the changes** **5. Validate the resulting dashboard and data access** Changing a Team from **Business** to **Technical** may expose additional diagnostic information to every member of that Team. Review the Team’s membership before changing its type. ## Remove a User from a Team 1. Go to **System -> Auth Settings -> Teams** and select the Team, or go to **System -> Auth Settings -> Users** and select the user. 2. Remove the Team assignment. 3. Save the changes. 4. Confirm that the user can no longer access the Team’s restricted dashboards and data. Removing a user from one Team does not remove access inherited from another Team. ## Validate Team Access Test Team configuration with a non-administrator account. Confirm that the user: * Can access the dashboards assigned to their Teams * Receives the expected pinned dashboards * Cannot access dashboards assigned only to other Teams * Can view only the business or technical data appropriate for the Team type * Can access only authorized Drill-through and Analysis details * Loses the relevant access when removed from the Team ## Recommended Practices * Create Teams around business units, applications, responsibilities, or data-access requirements. * Use **Business** Teams for users who do not require technical diagnostic data. * Restrict **Technical** Team membership to users who require detailed troubleshooting information. * Apply the principle of least privilege. * Review Team membership before changing a Team’s type. * Periodically review dashboard ownership, pinned dashboards, and Team memberships. * Test changes with non-administrator accounts. * Remove users from Teams when their responsibilities change or access is no longer required. ## Get Help > [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md) > > The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes. > [card] Can't find what you need? > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.