Managing Users
The Users page is where you create and manage your application's end users β HCPs, Organizations, Patients, and Devices. Each is a data owner; creating one in Cockpit provisions both the data-owner entity and the User account that logs in as it. For the entity types themselves see HCP Β· Patient Β· Device and Organization.
Where the Users page livesβ
- Single-tenant project β the project's Users page.
- Multi-tenant project β each tenant has its own Users tab; a user belongs to one tenant.
See Managing Tenants.
Adding a userβ
Add offers the four user types β Healthcare professional, Organization, Patient, Device β each with its own form:
| Type | Identity | Contact | Parent organization |
|---|---|---|---|
| HCP | First name + Last name | Email, Mobile phone | optional |
| Organization | Name | Email, Mobile phone | optional |
| Patient | First name + Last name | Email, Mobile phone | required |
| Device | Name (+ Serial number) | optional |
A Patient can't be created without a parent organization β it's the party they share data through. See Organization.
To create many at once, use Import β see Bulk Import.
An email address identifies a user within the tenant. Creating a user with an address that is already taken fails with "This email address is already used by another user." β nothing is created, not even the data owner.
On the Free plan each user type is capped per project (10 healthcare professionals, 10 devices, 100 patients) and each entry of the Add menu is disabled on its own once its cap is reached. See Limits.
The Users tableβ
Each row shows the user's Type, Name, Email, Enrolment status, and Account Status. Search by name, email, or phone (min. 3 characters) and filter by user type. The β― menu on each row holds the actions; expanding a row reveals the details and the per-user collections you can manage.
On narrow screens some columns (Email, Account Status, Enrolment status) are hidden instead of making the table scroll sideways β their values move into the expanded row under the same labels.
Loading, searching and filteringβ
The table loads 20 users at a time and fetches the next page as you scroll towards the bottom; there are no page controls. Search runs on the server and is paged the same way.
The Filter by User Type popover (the filter icon) offers User, Hcp, Device, and Patient; each active filter shows as a removable User type: tag. Two details to keep in mind:
- Hcp covers both healthcare professionals and organizations; User means a login with no linked data owner at all.
- The filter narrows the users already loaded. While a filter is active Cockpit keeps fetching further pages on its own; after scanning 300 users it pauses and shows Load more matches so you can continue. The empty state "There are no users of this type in this tenant." therefore only means nothing matched among the loaded users.
The User breakdown badges on a project's or tenant's Overview open this table with the matching type filter already applied β see Project Overview & Configuration.
Account status vs enrolment statusβ
- Account status β whether the user can sign in: Active, Registering, or Disabled. (A Critical issue tag overrides it if the user references a parent organization that no longer exists.)
- Enrolment status β whether the data owner's private key is initialized. Until it is, the user can't create or read encrypted data. See Recovery & Private Keys.
Overflow menu actionsβ
The β― menu on each row acts on the user as a whole:
- Edit β change the user's details, roles (Roles & Permissions), or parent organization.
- Initialize Private Key (HCP, if uninitialized) β set up the key for your own test/admin HCP only; real users initialize their own keys via your app. The action is greyed out while the account is Disabled ("Enable the account before initializing its private key."). See Recovery & Private Keys.
- Activate / Disable β toggle whether the account can sign in (its Account status).
- Inspect β¦ JSON β view the raw entity.
- Delete β remove the user and its linked data owner. Deletion cascades: the linked HCP / Organization / Patient / Device is deleted first, then the User shell itself. There is no undo in Cockpit, so the account and its data owner stop appearing in the Users table. See the caution below.
Delete removes the data owner, not just the login. Because the linked HCP / Patient / Device is deleted alongside the User, any auto-delegation pointing at that data owner is now broken β other users who systematically share with it can no longer do so. Cockpit flags a deleted delegate in the target user's Auto delegations list. Delete a user only when you intend to retire the data owner itself, not merely to block sign-in β for that, use Disable instead.
An HCP that is the parent of other HCPs can't be deleted. When you open the delete confirmation on an HCP, Cockpit first checks whether other healthcare parties have it as their parent organization. If any do, Yes stays disabled and the dialog explains: "This healthcare party cannot be deleted: N HCP(s) have it as their parent Organisation and would be left broken." β listing the children by name. Change those users' parent organization first, then delete. The check covers child HCPs only, not patients or devices.
Expanded row actionsβ
Expanding a row shows the user's identifiers β the data owner's id (Healthcare party ID / Patient ID / Device ID), the User ID, the Parent ID and Parent organization (flagged in red if the parent no longer exists), and contact details β followed by its Roles and Permissions, and three per-user collections you can manage:
Rolesβ
The Roles row lists the user's role tags and carries a Default or Individual tag telling you whether the user follows the project's default roles for its type or has its own assignment. You manage the roles right here, without opening the Edit modal:
- + opens Modify user's roles: pick the Assigned roles or Reset to default (Cockpit lists what Will be removed and Will be added before you confirm).
- The delete button on a tag removes that role, after a confirmation that spells out the consequence β removing a role from a Default user switches it to an Individual configuration, and removing the last Individual role resets the user to the defaults. The only role of a Default configuration can't be removed (adjust the project's default roles instead).
- The parentheses icon on a tag (Inspect the role JSON) shows the raw role. A role that no longer exists is shown as invalid with a prompt to remove it.
Changes apply immediately. See Roles & Permissions for the Default vs Individual model.
Permissionsβ
The Permissions row shows what the user can effectively do, derived from its valid roles: one tag per business area (Scheduling, Patients, Medical records, Billing, β¦), each with a tooltip giving the permission count and the roles that grant it. Inspect permissions opens the User permissions modal β a tree of every Effective permission with the role(s) that grant it. A user with no valid role reads "No permissions: this user has no valid role assigned."
Custom propertiesβ
Typed keyβvalue metadata attached to this user β the same model as a project's/tenant's Custom Properties, just scoped to the user. Add, edit, or delete an Identifier + Value with a declared Type (Boolean, Integer, Double, String, Date, Clob, Json). Use it to store your own data about the user that isn't part of the standard schema; your application reads it back from the entity.
Authentication tokensβ
Long-lived tokens for programmatic / API access as this user β distinct from interactive login. Generate authentication token takes a Token name and an Expiration date and time; the token's value is shown only once, so copy it immediately. You can delete tokens you no longer need. See Authentication.
Auto-delegationsβ
The set of other data owners this user automatically shares with whenever it creates new data. The most common case is the parent organization: with auto-delegation in place, data the user creates is shared with the parent, so others under the same parent (e.g. HCPs in the same clinic) can access and decrypt it. Registration authentication processes can set this up automatically for users they create; here you can see and adjust it per user; removing one asks for confirmation. See Auto-delegation for the full picture.
Where to go nextβ
- HCP Β· Patient Β· Device and Organization β the entity types in depth.
- Bulk Import β create many users from a spreadsheet.
- Roles & Permissions β what each user can do.
- Recovery & Private Keys β initializing and safeguarding keys.
Cardinal SDK reference: Registering users β creating
Users and their data owners from the SDK.