> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/pipekit/organization/user-management.md).

# Managing Users

## Adding users to your Organization

Go to the [Org tab in Pipekit](https://pipekit.io/organization). You will be presented with the Users tab.

To invite additional users, enter their email address in the `Invite User` field and click on the `Invite` button. The user will receive an email with a link to join your Pipekit Organization.

## Managing user permissions

On the Organization's Users tab, find the user whose permission you wish to manage and click the gear icon on the right hand side. You will be presented with a list of permissions that you can grant to the user.

## Removing users from your Organization

On the Organization's Users tab, find the user that you wish to remove and click the gear icon on the right hand side. You will be presented with a `Remove User` button. Click on the button to remove the user from your Pipekit Organization.

## Linking Pipekit Users with Git Identities

If you are using [Run/Sync Conditions](/pipekit/pipes/managing-pipes/run-sync-conditions.md) to trigger Pipe Runs, you will need to map each user's Git identity with their Pipekit identity so that Pipekit can understand and display the name of the user who triggered a [Pipe Run](/pipekit/runs.md). You can do this by navigating to the Organization's Users tab and choosing the option to `Edit Git Mapping`.

Git identities of users who have recently interacted with your synced repositories will be available to map to each user. A Git identity can only be mapped to one Pipekit user.

CI/robot (service) accounts are not pre-existing mapped identities. To map a CI/robot (service) account's Git identity, first create a Pipekit account for the CI/robot account, then map its Git identity.


---

# 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://docs.pipekit.io/pipekit/organization/user-management.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.