For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Adding users to your Organization

Go to the Org tab in Pipekit 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.

Adding an email address under My Account adds it to your own login. It does not invite anybody.

Managing user permissions

On the Organization's People & Access tab, open Users, 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 People & Access tab, open Users, 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 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. You can do this by navigating to the Organization's People & Access tab, opening Users, 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.

Last updated