> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Knowledge

Every engineering organization has unique tribal knowledge: the unwritten rules, naming conventions, query patterns, and debugging heuristics that experienced engineers carry in their heads. Teaching this knowledge to Resolve improves the quality of both chat responses and alert investigations. The more context Resolve has about your systems, the faster and more accurate its analysis becomes. Iteratively add Knowledge to teach Resolve best practices for different types of issues.

## Teams

Start by creating a **Team**, which represents a logical group within your organization (ex. Infra, Payments).

Teams have a few key sections:

1. **Knowledge**: Define best practices for querying observability tools and investigating incidents. This includes Resolve.md, runbooks, dashboard guidance, docs, and skills.
2. **Configuration**: Settings to help Resolve understand when this team's knowledge is relevant to pull in to an investigation.
   * **Alerts**: Use the Alerts page to filter alerts, enable auto-investigation, and attach runbooks.
   * **Workplace Collaboration Tools**: Connect Slack or MS Teams channels for alerts, change events, or general chat.
   * **Resources**: Define ownership by selecting applications, services, or clusters managed by the team.
   * **Dashboards**: Add dashboard guidance to help Resolve interpret and analyze observability data correctly.

<p align="center">
  <img src="https://mintcdn.com/resolveai-0e94a547/TSKPziqa8xE8YA7n/images/teams_1.png?fit=max&auto=format&n=TSKPziqa8xE8YA7n&q=85&s=46ea5ae97097364a4e48439bcc03f370" alt="Overview diagram of Teams" width="50%" data-path="images/teams_1.png" />
</p>

***

## Create Your First Team

1. Open [app0.resolve.ai](https://app0.resolve.ai/)
2. Open the left sidebar and click **Teams**
3. Click **Create Team**
4. Enter a name, description, and click **Create Team**
5. Set up knowledge, alerts, workplace collaboration tools, and dashboards

The **Default Org** lets you add guidance for company-wide defaults and best practices.

***

## How Resolve Uses Knowledge

Knowledge is how you guide Resolve’s reasoning. Resolve uses a **two-tier knowledge model** — every knowledge type can exist at both the organization level and the team level:

| Knowledge Type     | Organization Level                           | Team Level                             |
| ------------------ | -------------------------------------------- | -------------------------------------- |
| Resolve.md         | Company-wide defaults for all investigations | Team-specific overrides and context    |
| Alert Runbooks     | Org-wide runbook guidance                    | Runbooks scoped to this team’s alerts  |
| Dashboard Guidance | Default guidance for shared dashboards       | Guidance for dashboards this team owns |
| Docs               | Company-wide reference documents             | Team-specific service and system docs  |
| Skills             | Org-wide procedures and templates            | Team-specific procedural workflows     |

* **Alert investigations**: Resolve examines all knowledge associated with the alert and its owning team(s), pulling mapped runbooks and relevant team and org knowledge.
* **Chats**: Resolve pulls in skills and relevant knowledge sections quickly to keep conversations responsive.
* **Skills**: Activated dynamically when their `description` matches the task, or invoked directly via slash commands. Available to alert investigations and chats. See [Skills](/skills) for the format and examples.
* **Alerts owned by multiple teams**: Resolve fetches relevant knowledge from all owning teams.
* **Priority**: Resolve searches org and team knowledge together, surfacing the most relevant information for the investigation. Team-level guidance is prioritized when it's a closer match.