Skip to main content
Everything in Pipefort belongs to an organization: repositories, scans, findings, triage states, and rule settings are shared by the organization’s members. Two things stay personal: your Slack notification settings (your channel, your choice) and your GitLab identity.

​
The Settings page

Settings is one pane at a time, deep-linkable as ?section=: Four more sections — Alert rules, API tokens, Audit log and Billing — are listed but greyed out with a soon badge, each naming what it is waiting on. They are shown rather than hidden because an absent row reads as “this product does not do that”, when the true statement is “not yet”.
There is no delete-organisation button, because there is no endpoint behind one. Removing an organisation is a support request today; leaving one is done from Members & roles.

​
Personal and team organizations

Every account has a personal organization, created automatically — if you’ve used Pipefort before organizations existed, all your data was migrated into it and nothing changed. To collaborate, create a team organization from the organization switcher in the header (the building icon), then invite teammates. The switcher also selects which organization the whole app operates on — dashboard, repos, Attacker Mind, rule settings, all of it follows the active organization.

​
Roles

The creator of an organization is its first admin. An organization always keeps at least one admin — demoting or removing the last one is refused.

​
Inviting teammates

  1. Open Settings → Members & roles with the team organization active.
  2. Under Members & roles, enter the teammate’s email and a role, and click Invite.
  3. No email is sent (v1). When someone signs in to Pipefort with that email address, a banner on the Settings page shows the pending invite with an Accept button. Tell them out-of-band.
Invites match on the sign-in email (case-insensitive). Accepting adds the organization to their switcher; their personal organization is untouched. Admins can revoke pending invites from the same card.

​
Leaving

Members can leave a team organization from the Settings page. You can never leave your personal organization — it’s where your account’s own data lives.

​
How access works

  • One organization = one tenant: each org has its own copy of a repository (its own scans, findings, triage). Two organizations that install the same GitHub App installation scan independently.
  • Monitored repos: a push triggers one scan per organization monitoring the repo, and notifications go to every member of that organization who has them configured.
  • Provider credentials follow whoever connected them: scans of a GitLab repo use the OAuth token of the member who linked GitLab, regardless of who clicks Scan.
  • Membership is enforced all the way down to the data layer — you can only ever read data for organizations you belong to.