> For the complete documentation index, see [llms.txt](https://au-dohp.gitbook.io/au-dohp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://au-dohp.gitbook.io/au-dohp-docs/whats-new/integration-of-team-mapping.md).

# Integration of Team Mapping

The map helps display data products, their associated metadata, and the agreements teams have with each other, including the number of data products, data contracts, consumers, and other related details.

**Core Functionality and Architecture**

The Teams Map provides a visual representation of the relationships and agreements between teams, either within the same organization or with external teams. It displays total permissions granted to users, such as the ability to consume, view, or edit data products. The map is built using **React Flow**, showcasing the central team and the agreements with other teams in a node-link format.

***

**Key Components**

* **React Flow for Visualization:** The Teams Map utilizes React Flow to visually represent teams and their agreements. Each team is represented by a node, and agreements are visualized as edges between these nodes, illustrating the types and number of permissions granted.
* **Agreement Types:** Agreements are categorized based on the level of access granted, including:

  * **Consuming the data product**: Permission to ingest the data.
  * **Viewing the data product**: Permission to view the data without modification.
  * **Editing the data product**: Permission to modify the data.

  Only the permissions officially granted to users are counted as agreements, ensuring an accurate representation of access levels.
* **Team Metadata:** Each team’s metadata includes relevant details such as the number of data products, data contracts, and consumers within the team. This metadata is displayed alongside the team's node in the map, offering an at-a-glance view of the team’s activity and connections.

***

**Technical Workflow**

1. **Team Identification:** The system identifies a central team (the team of the user or the team being viewed) and its relationships with other teams based on the permissions granted to users.
2. **Agreement Representation:** The system evaluates the permissions of users within the central team and its agreements with other teams. These agreements are then represented as edges between nodes, with each edge detailing the types of permissions granted (consuming, viewing, or editing).
3. **Visualization and Interaction:** Users can interact with the map to explore agreements between teams, viewing detailed metadata about each team’s data products, contracts, and consumers.

***

**Key Features**

* **Team-to-Team Agreement Visualization:** The map allows users to see the agreements between teams, represented as edges between nodes. This provides a clear, visual understanding of the relationships and permissions granted between teams.
* **Permissions Breakdown:** The map breaks down the types of permissions granted to users, such as consuming, viewing, and editing, ensuring users understand the access granted to their teams.
* **Team Metadata Display:** Each team node displays essential metadata, including the number of data products, data contracts, and consumers associated with the team, giving context to the relationships between teams.

***

**Validation**

* To access the Teams Map, users must have administrative rights. Super Admins, Organization Admins, or Team Admins can view the feature, either through the member management details or via the admin management dropdown.
* For Organization Admins or Team Admins of the affected teams, the Teams Map is directly accessible, providing visibility into team agreements and metadata.

***

**Preview**

* **Image 1:** Example of the Teams Map, showcasing the central team and its agreements with other teams.
* **Image 2:** Example of team metadata, displaying details such as the number of data products, contracts, and consumers.

4o mini


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://au-dohp.gitbook.io/au-dohp-docs/whats-new/integration-of-team-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.