> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/getting-started/adding-uses-to-your-account.md).

# Inviting Team Members

After signing up for a BugSplat account, it’s important to add your team members to your company so that they can access the team's crash data. Crash reporting is better with friends.

## Add Team Members to all Company Databases 🏀

To add a team member to all your company's databases, simply add them via the [Company](https://app.bugsplat.com/v2/company) page. They will receive an email providing a prompt about setting up their account.

## Adding Team Members to Specific Databases ⚽

Only need to add a team member to a specific subset of databases? Select the desired database, then navigate to its [Users](https://app.bugsplat.com/v2/database/users) page in Settings.

![Adding Team Members](https://976110677-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LBMgmIcgkIXSUfnXDSv%2Fsync%2F2738367f8d40b6dc8f6b29229c2d4b8012286c66.png?generation=1631200982718582\&alt=media)

Once you've navigated to the Users page for the right database, click the `Add Users` button. This will prompt you to insert an email address of your team member. Once invited, they will receive an email allowing them to set up their account.

Repeat this process for all desired databases.

{% hint style="info" %}
**Managing User Permissions**: Looking for a doc about limiting a team member's permissions inside of a BugSplat account? Click [here](/administration/user-management/user-permissions.md).
{% endhint %}


---

# 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://docs.bugsplat.com/getting-started/adding-uses-to-your-account.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.