Organizations
How an organization is created, who belongs to it, and what it owns.
An organization is the boundary around everything you create in Pentr. The
API and the database spell it organization. This page describes how an
organization comes to exist, who belongs to it, what it owns, and how you sign
in to it.
How an organization is created¶
You do not create an organization by hand. After you register, the first
authenticated request you make โ normally, opening the console โ finds no
Pentr user for your identity and provisions one. In the same step it creates
a new organization, names it after your email address, and makes you its
owner. If the identity has no email address, the identity id is used as the
name instead.
Members and roles¶
An organization has one user: the one it was created for. The product has no invitation, and nothing in it adds a second user to an existing organization. A teammate who registers gets an organization of their own, and neither of you can see the other's engagements.
A user's role is owner or member. Provisioning always assigns owner,
and nothing in the product assigns member. One action checks the role:
attesting to ownership of an asset, which requires owner
(Ownership verification).
Renaming and deleting¶
The product has no way to rename an organization, and no way to delete an
account or an organization. The organization's name appears in one output, the
organization field of GET /api/v1/usage
(Usage and limits).
What belongs to the organization¶
These belong to the organization:
| Record | Described in |
|---|---|
| Engagements, with their findings, reports, evidence lockers and share links | Engagements |
| Assets and their verification logs | Ownership verification |
| Schedules | Schedules |
| Signing keys | Signing keys |
| API keys | Authentication |
| Webhooks | Webhooks |
An engagement that belongs to another organization answers 404, the same as
one that does not exist.
Two things belong to the user rather than the organization: the role
described above, and the plan tier
(Plans and limits). A schedule also records
the user who created it, and the plan cap is read from that user's tier when
the schedule fires.
Signing in¶
Sign-in is by email address and password. No other sign-in method is enabled. A session lasts 24 hours from sign-in. Once it has expired, the console's requests are refused, and loading the console again takes you to the sign-in page.
The Account page in the console's sidebar shows three values from your identity: your email address, your name, and your identity id. It has no fields to edit.
You can change your password at /auth/settings on the console's host. No
link in the console leads there, and the Settings entry in the sidebar is
greyed out, so open the address directly. If the page says
Please sign in again to change your password., sign in and open it again.
If you have forgotten your password, contact Pentr support.
Last updated 2026-09-23