Guide for administrators
Run the organisation from the system console — members, access, Marketplace, billing, audit, security and integrations
Administrators run the organisation from the System console: its people, who may do what, its settings, installed modules, integrations, the audit trail and billing. The console belongs to one organisation and shows nothing of any other.
Your role
The console appears among your apps if you are the organisation's owner or an administrator, or hold a delegated administrator role (for example a read-only or people administrator). Inside it you see only the pages your role lets you open.
- The owner holds every permission.
- An administrator holds every permission except billing.
- A delegated role sees only its rows: a role that carries only
org.moderate, for example, sees Reports and nothing else.
Find your way in the console
/admin.members, invitations, roles, audit or marketplace.
Encrypted rooms are absent from every console list on purpose: the server cannot read them, so the console cannot show them. The overview only counts how many rooms are end-to-end encrypted.
See Administration.
Members and invitations
Invite somebody. System console → Members → Invite somebody sends an invitation by email. Each link is single-use and carries the team the person lands in and the role they arrive with.
People without a work mailbox. Use Create from names: each person gets a username and a temporary password on a printable sheet. To print new sheets, tick accounts that are not set up yet in the roster and choose Print new passwords.
Change a grade. From a member's row menu or page, choose Make an administrator or Demote to member.
See what somebody holds. ⋯ → See what they hold lists every role, team, group, module role and project the person reaches, and how each one reaches them.
Help or stop somebody. On the member page: suspend, sign out everywhere, send a recovery link or reset the second factor.
Remove from the organisation. Row menu or danger zone. The person leaves every room, team and group; their account row stays, so history still names them.
Only a hash of an invitation link is stored, so a lost link cannot be shown again: withdraw it under Invitations and send a new one. Invite somebody is not offered while sign-up is closed.
Guests (/admin/guests) are people from outside invited into individual private rooms. They
take no seat on the plan and see only their rooms. See
Members — the roster.
Access and roles
Access has three levels, and each one decides something different:
- Organisation — the grade and organisation roles open the console; module roles open modules. None of them puts anybody in a channel.
- Team — being in a team puts you in its public channels; team roles decide what you may do there.
- Private channel — only the people added to it, by hand, through a group, or through a role or person the channel allows.
Run a team without joining it. Access → Teams, open a team, and add or remove members, groups and team roles. You are never seated in the team yourself.
Grant a module role. Access → Roles, tier Modules. A person holds at most one role per module per scope, so choosing another role replaces the first.
Compare permissions. Access → Matrix shows which role carries which permission. Ticking a box saves the role at once.
Answer "why can they?" Access → Explain access: choose the person and what they tried to do. The answer comes from the server. Use the what-if to add or remove a role; nothing is saved.
Nobody can write a role that carries a sensitive permission they do not hold themselves.
See Access and roles.
Marketplace and bundles
Open System console → Marketplace. Filter by All, Installed, Available or Needs attention. Bundles install the modules an organisation of one kind usually starts with, plus whatever they need.
Choose Install on a module's card or page. Modules it needs are listed under What it needs and installed with it. A module that needs configuration shows Needs setting up: fill in Settings on its page and apply them.
Under Who gets it, choose Everyone, Selected people (granted a role under Access → Roles → Modules) or On request.
Change Settings later as a draft and apply it. Every applied configuration is kept under History, so you can undo a change.
Decide what members asked for under Requests.
Suspend stops a module and keeps its configuration and data. Remove stops it now and starts a countdown, after which its configuration is deleted. Resume restores it only while the countdown runs. Read what the page says will happen to the module's data before you remove it.
See Marketplace.
Billing
Billing is for the owner only (org.manage_billing). Administrators do not see it.
For plans and prices see enclessa.app. To move billing to somebody else, the owner hands the organisation over under Members → ⋯ → Hand the organisation over. See Billing.
Audit, compliance and moderation
- Audit log (
/admin/audit) records who changed what, in plain language, one time window at a time. Every change made in the console is written there. - Compliance (
/admin/compliance) holds the retention policy for each team and room, the compliance export of the managed rooms, and the audit log as a file. - Reports (
/admin/reports) is the moderation queue. Each entry keeps a snapshot of what the member saw; closing it does not delete the message.
See System.
Security settings
Open System console → Settings, pane Sign-up and security, to decide who may join and how people sign in. The open pane is part of the address, so you can link straight to it.
Set branding, legal texts, email and the other organisation-wide settings in the other panes of Settings. Each pane saves on its own.
For programs, create Bots (/admin/bots): a bot signs in with a token that carries only the
scopes you give it, and reaches only the rooms somebody added it to. The token is shown once.
To send events to a URL you run, add Webhooks (/admin/webhooks). Deliveries are signed,
retried and kept in a log for thirty days.
A recovery link always goes to the address on the account and is never shown to you.
Integrations
GitHub. System console → Marketplace → GitHub, switch it on (Boards must be on too), connect a GitHub App or a personal access token, and set up the webhook. Prefer a GitHub App for a team. See Connect GitHub.
GitLab & Forgejo. System console → Marketplace → GitLab & Forgejo, enter the host and an access token, Test, and copy the webhook address into the forge. See Connect a forge.
MCP. System console → Marketplace → MCP sets, per tool, whether a connected agent may use it Off, Ask first or Without asking. See Set what agents may do.
Companion. System console → Marketplace → Companion sets the organisation's ceiling for the built-in assistant. See Companion.
Linking a board to a repository is a team decision made on the board, and needs manage boards in that board's team.
Who can do what
| Destination | Permission |
|---|---|
| The console, Overview, Access overview, Teams, Roles, Matrix, Marketplace | org.view_console |
| Members, Invitations, Guests, Accounts, Bots, Explain access | org.manage_members |
| Groups, Import | org.manage_teams |
| Organisation profile | org.manage_settings |
| Settings | org.view_settings |
| Reports | org.moderate |
| Audit log, Compliance | org.view_audit |
| Install, configure and remove modules; Webhooks | org.manage_modules |
| Billing | org.manage_billing (owner only) |
Seeing a screen does not mean you can change everything on it: a button you may not use is left out, or the server refuses it. Module settings are under Settings → Features or Module settings on the console overview.