> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/configuration.md).

# Settings overview

The article provides an overview of settings to ensure your data is accurate in Swarmia and links you to further reading and the related settings in the Swramia app.

Data quality is crucial for building trust in engineering intelligence tools and ensuring sound decision-making. Teams often work differently—using Scrum, Kanban, or other practices—which can lead to inconsistencies. Issues like mismatched user identities, inconsistent issue tracking, or conflicting label usage can impact data reliability. That’s why we prioritize accurate and transparent data by showing what's behind each metric, automating the setup whenever possible, and offering tools to close any quality gaps that might remain.

## Organization settings

At the Swarmia organization level, you integrate your tools, configure global settings, and organize your authors into Swarmia teams. At the team level, you ensure the right issues and pull requests are assigned to teams.

* [**Creating teams**](/settings/organization/managing-teams.md)**.** To see your data in Swarmia, you need to organize authors into teams. You can sync teams from GitHub, use Swarmia API, or create teams manually. [Teams & members settings](https://app.swarmia.com/settings/teams).
* [**Authors**](/settings/organization/contributors.md)**.** Ensure work items are assigned to the right people. Swarmia automatically merges the identities across the systems people work in. Make manual adjustments as needed. [Authors settings.](https://app.swarmia.com/settings/authors)
* [**Issues: projects, types, statuses**](/settings/integrations/issue-trackers.md)**.** Select projects to sync. Swarmia maps issue types and statuses automatically and you can make adjustments if needed. [Issue tracker settings](https://app.swarmia.com/settings/issue-trackers).
* [**Pull request exclusions**](/settings/organization/pull-request-data-quality.md#pull-request-exclusions-at-the-organization-level)**.** By default, pull requests from all synced repositories are visible in the Swarmia metrics. Create filters to exclude specific pull requests automatically. [Pull request settings](https://app.swarmia.com/settings/pull-requests).
* [**Issue linking**](/settings/organization/pull-request-data-quality/linking-pull-requests-to-issues.md)**.** Swarmia automatically links pull requests to issues and offers ways to do it manually when a pull request contains too little information to link automatically. Configure AI-powered matching and GitHub issue-link comments in [Issue linking settings](https://app.swarmia.com/settings/pull-requests/issue-linking).
* [**Investment categories**](/settings/organization/investment-balance.md)**.** Use Swarmia default settings or define rules on how to group pull requests and issues into investment categories. [Investment category settings](https://app.swarmia.com/settings/investment-categories).
* [**Deployments**](/settings/organization/configuring-deployments-in-swarmia.md)**.** Configure deployments to track DORA metrics. Swarmia supports multiple setup options to match your needs. [Deployments settings](https://app.swarmia.com/settings/deployments).

## Team settings

Once the organization-level settings are ready, you and the teams can proceed with team-level settings to ensure the right issues and pull requests are assigned to each team.

* [**Mapping issues to teams**](/settings/integrations/issue-trackers/jira/jira-setup.md#map-issues-to-teams)**.** Assign issues to teams to make them visible in Swarmia. Swarmia automatically suggests a project for each team. If multiple teams use the same project, you can assign the issues with, e.g., labels or custom fields. [Team issue settings](https://app.swarmia.com/settings/team/issues).
* [**Team PR exclusions**](/settings/team/team-pr-exclusions.md)**.** By default, Swarmia associates everyone's pull requests with all the teams they belong to. You can create rules to exclude specific pull requests from your team. [Team PR exclusions](https://app.swarmia.com/settings/team/pull-requests).
* [**Team notifications.**](/settings/team/team-notifications.md) Slack and Microsoft Teams notifications make work visible and provide a feedback loop to stick to working agreements to create lasting habits. [Team notifications settings](https://app.swarmia.com/settings/team/notifications).
* [**Inviting team members**](/settings/organization/inviting-team-members.md)**.** Invite team members to collaborate in Swarmia and enable their personal notifications. [Swarmia home.](https://app.swarmia.com/)
* [**Improving categorization rate**](/settings/organization/investment-balance.md#improving-categorization-rate)**.** A high categorization rate (more than 80% of work categorized) is essential to have good visibility into where engineering time goes. You can find the items the categorization rules didn't catch and assign the right category in the [Investment balance](https://app.swarmia.com/investment).
* [**Configuring sprints**](/settings/team/sprints.md)**.** Swarmia automatically selects a Jira board that has Sprints and enables sprint activity tracking. You can change the board in [Team issue settings](https://app.swarmia.com/settings/team/issues).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/settings/configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.