> 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/organizations-and-access/members.md).

# Members

Organization members are managed on the `Org` page. The `My Account` page holds your own profile, email addresses and password, and nothing there affects other people.

## Who can manage users

Which rules apply depends on your organization's permission system. To find out which one it uses, refer to [Which one does your organization use?](https://docs.pipekit.io/concepts/access-control.md#which-one-does-your-organization-use).

Under [basic permissions](https://docs.pipekit.io/organizations-and-access/basic-permissions.md), members with the admin permission see `ORG` in the navigation. Only they can invite, edit, or remove users.

Under [multi-tenant RBAC](https://docs.pipekit.io/organizations-and-access/rbac.md), the [RBAC policy](https://docs.pipekit.io/organizations-and-access/rbac/publish-rbac-policy.md) decides who can manage users:

* Only an Org Admin sees `ORG` in the navigation and can open the `Org` page. Anyone else cannot open the organization settings page.
* Only an Org Admin can invite users, resend or revoke invitations, and remove users. The basic admin permission no longer applies.
* Nobody edits a user's access on the `Users` tab. To change access, publish a new policy version.

## Adding users to your Organization

Go to the [Org tab in Pipekit](https://pipekit.io/organization) and open `People & Access`. 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.

{% hint style="info" %}
Under multi-tenant RBAC, an invitation alone grants no access. The new user gets access only when a binding in the policy names their email or one of their identity provider groups. After they accept, check their row on the `Users` tab. `No access` means no binding matches them yet.
{% endhint %}

{% hint style="info" %}
Adding an email address under `My Account` adds it to your own login. It does not invite anybody.
{% endhint %}

## Pending invitations

An invitation stays pending until the invited person creates their account and confirms their email address. Pending invitations are listed in a `Pending invitations` table below the users table, with the date you invited the address and the date the invitation email was last sent.

Organization admins get two actions on each row. Click `Resend` to send the invitation email again. The link in the earlier email keeps working, and the `Last sent` date updates. Click `Revoke` to cancel the invitation. Revoking stops the accept link from working, and you can invite the address again later.

## Managing user permissions

Under basic permissions, you grant permissions per user or per group. Refer to [Basic Permissions](https://docs.pipekit.io/organizations-and-access/basic-permissions.md).

## Viewing access under a multi-tenant RBAC policy

Under multi-tenant RBAC, the `Users` tab shows the access each user gets from the policy. The tab is read-only for access.

A banner at the top names the version in force, for example `Enforcing policy v4`, with who published it and from which commit. Click `View policy` to open the policy itself.

Use the search field and the `All groups`, `All workspaces`, and `All roles` filters to narrow the list. The `Access` column shows each user's roles and how many workspaces they reach. A user whose groups match no binding shows `No access`.

Click `Details` on a row to open the `Effective access` table for that user. Each row shows a `Workspace`, a `Role`, its `Scope`, the subject it is `Granted by`, and a `Status`:

* `Applies` means the user has this role.
* `Overridden by <role> from <subject>` means a higher role from another binding takes precedence in that workspace.

If Pipekit cannot load group memberships from your identity provider, the tab shows `Could not load IdP group memberships`. Access that comes through groups shows `Unknown` until you click `Retry` and the load succeeds.

Pipekit internal accounts bypass the policy, so the tab does not show their access.

## Removing users from your Organization

On the Organization's `People & Access` tab, open `Users`, find the user that you wish to remove and click the gear icon on the right hand side. Choose `Delete User` to remove the user from your Pipekit Organization.

If your organization provisions users through SCIM, `Delete User` is disabled. Remove the user in your identity provider instead. You cannot delete yourself.

## Linking Pipekit Users with Git Identities

If you are using [Run/Sync Conditions](https://docs.pipekit.io/using-pipekit/pipes/edit/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](https://docs.pipekit.io/using-pipekit/runs.md). You can do this by navigating to the Organization's `People & Access` tab, opening `Users`, and choosing the option to `Edit Git Mapping`. Under multi-tenant RBAC, the gear icon still offers `Edit Git Mapping` and `Delete User`.

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.
