People and Vaults

These screens sit under Identity & Access in the sidebar, with Vaults directly below the group.

Users

The list of every account on your node, with the count beside the heading and a note when a filter is narrowing it.

Search takes part of a name, or an exact address, id or referral code. Filters narrow by sign-in method, plan band, subscription state, how the person arrived, providers only, trust and verification scores, and by when they were created, last seen, or due to renew.

Selecting a row opens a detail panel with tabs: Subscription, Access, Sessions, Devices, Connections, Notifications, Tags and Activity. Most carry a count. The panel has a control to expand it to full width.

What you can do from here on your own node: send a password reset email, send a magic link, reset a user’s magic-link rate limit when they have exhausted it, and add or remove tags. Each of the first three asks you to confirm.

Invite User is the button to add somebody. Enter an address and the node mints a one-time invitation. Because your node is federated, the result is shown as a QR code encoding a one-time invite link, so you can have the person install the app and scan it; there is a copy control for the link. The code carries an invitation token, never a credential, and the modal shows its expiry date. If an invitation for that address is already pending you are asked to either Keep Existing or Resend Invite.

The other buttons on this screen — Test User, Clean Tests, Import, and the destructive per-user actions — are refused on a node. See Roles and permissions.

Sessions

Headed Session Management. Four counts across the top: Total Sessions, Active, Revoked, and Expired (not cleaned). Search by email or device name.

You can revoke a session from its row. That signs that device out; it does not touch the account.

When the expired-not-cleaned count is above zero, a refresh control appears in the corner of that card that runs a cleanup pass over the expired rows.

A session row also opens its login origin, showing where the sign-in came from and the fraud signals stored with it.

Login History

Every sign-in, with counts for the total, today, the last seven days, and a breakdown by method. Search by email or name. A row opens the stored origin and fraud signals for that sign-in.

Blocked Attempts

Sign-in attempts your node refused as spam, disposable addresses or suspicious patterns. Counts for the total, today, the last seven days, disposable addresses and spam domains. Search by address or pattern, and open a row for the full detail.

One control on a row runs a MaxMind minFraud lookup for the address’s IP. It is labelled with its cost, because it is a paid call to an outside service. It only works if you have wired a MaxMind key.

Organizations

Your organisations, with a total and a breakdown by type. Search by name or slug, and filter by type. Selecting one opens its detail with its roles listed by Role, Product, Default, Permissions and Members.

New Organization creates one, and editing an existing one saves. Deleting an organisation and Provision Business Org are refused on a node.

Vaults

Every vault on your node. Filter by status — Active, Deleted, Orphaned — by type, Private or Group, and by language. Search across them, and open one to see its members.

This screen is a view. It lists what exists and who is in it. It does not show you the contents of a vault.