Groups, permissions and admitting people
Access is closed by default. A person can do only what a group they belong to allows. Three pages under Settings manage this. Groups holds who is in each group and what it allows. Permissions lists every permission. Admit a person lets a new sign-in join your organisation.
Groups
Open Groups to see one row per group.
| Column | What it tells you |
|---|---|
| Name | The group’s name |
| Members | How many people belong to it |
| Permissions | How many permissions it holds |
Search narrows the list. Select a row to open the group.
Creating a group
- Select New group.
- Enter a group name.
- Select Create.
If the name is blank, nothing is saved.
Inside a group
A group page has a Details panel, a Users panel and a Permissions panel.
- Details shows the name, the member count and the permission count. Select Edit to rename the group.
- Users lists the members with their email and status. Select Add member to add someone. The button is off when everyone is already a member.
- Permissions lists every permission you can grant. Select Grant to give one to the group. Select Revoke to take it away.
Some permissions show Connection only. Only a connection to another system holds these. You cannot grant them to a group.
A grant that can be capped shows a Ceiling column. See authority ceilings.
Permissions
Open Permissions to see every permission in the system. It is a list for reading. You grant permissions from a group page.
| Column | What it tells you |
|---|---|
| Key | The permission’s name |
| Category | The area it belongs to |
| Provenance | Where the permission comes from |
| Held by | The groups that hold it |
A system badge marks a permission that only the system itself uses. You cannot grant it to a group. A connection badge marks one that only a connection holds.
Use the filters above the list.
| Filter | What it shows |
|---|---|
| All | Every permission |
| Catalog | Permissions a person can hold |
| Operations | Permissions that come from account operations |
| System-internal | Permissions only the system uses |
| Connection | Permissions only a connection holds |
If you lack the permission to view groups or permissions, the page says you do not have access.
Admitting a person
A person who signs in to the bank portal for the first time is not yet a member of your organisation. Admit a person finds one of them by their exact email. There is no list to browse: sign-ins are shared by every bank on the platform, and a list would show you other banks’ people.
- Open Settings and select Admit a person.
- Enter the person’s email and select Find. Capitals do not matter; every other character must match.
- Check the name, then select Admit.
A message says the admission was submitted. A second approver must approve it before it takes effect. Its register row is Segregation of duties (maker-checker) — bank. The person who submits cannot approve the same change.
If no one can be admitted with that email, the page says so. Either the person has not signed in to the bank portal yet, or they are already a member. Ask them to sign in to the bank portal once, then find them again.
Only a bank portal sign-in can be admitted. A client portal sign-in is never found here, even with the same email. If you admit one by other means, the admission is refused.
After an admission is approved, add the person to a group. Until then they can do nothing.
A worked example
The development seed sets up groups for a maker-checker demonstration. It is not a template for your organisation. Makers hold every grantable permission except the one that approves. Approvers hold the approve permission only, with the right to read the approval queue and verify a signed decision.
Alex belongs to Makers and stages a change. Alex cannot approve it. Sam belongs to Approvers and approves it. Alex and Sam are never the same person for one change.
What your organisation configures
- Which groups exist and what each allows.
- Who belongs to each group.
- Which people you admit to your organisation.
- Whether a second person must approve a change, and who may.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.