Administration overview
A page for administrators. This is a map of the whole Admin section: which pages exist, what each one configures and where it is described in detail. Useful when you know what you want to change but not where it lives.
How the section is arranged
There are two ways in, and they lead to the same place:
- the Admin dropdown in the top bar — a quick jump to any section;
- the left menu inside the section — the full list of pages.
The order in the left menu is not accidental: the product's own pages come first, then the ones brought in by enabled features. That way you can tell what belongs to the core from what arrived with a feature and will disappear if you turn it off. Some entries are hubs: Storage and Mail have nested entries, each configuring one particular storage or transport.
Half of these pages may not exist for you
Menu entries appear together with features. If the list below mentions a section you do not have, the corresponding feature is disabled or not part of your package; see Plugins.
The whole section is available to the global administrator role only.
Built-in pages
| Section | What it configures | In detail |
|---|---|---|
| Users | Accounts: creation, role, disabling login, password and reset email, ending all sessions, lifting a sign-in lock, 2FA status, issuing an API token on someone's behalf, the seat counter. | Users & permissions |
| Security | Password policy, lockout on password guessing, mandatory two-factor authentication. | Users & permissions |
| Groups | Grouping people so access is granted to a group instead of a dozen individuals. | Users & permissions |
| Global perms | The “global role × capability” matrix: what each role means in your organisation. | Users & permissions |
| Project roles | The catalogue of in-project roles beyond the four built-in ones. | Users & permissions |
| Permission schemes | Named sets of permissions applied to projects; rights can also go to an issue's reporter and assignee. | Users & permissions |
| Priorities | The priority scale: colour, name, order, default. | Project configuration |
| Issue types | Types of work: colour, icon, order, the default type, the subtask flag. | Project configuration |
| Brands | The shared catalogue of brands used by release waves, with card fields — contacts and more. | Project configuration |
| Plugins | The feature registry: enabling, statuses, adding your own. | Plugins |
| API tokens | Every personal token of every user, with the option to revoke. | AI & API access |
| MCP | The endpoint for AI assistants: switches, the tool list, the call log. | Features & settings |
| Storage | An overview of connected file storages, their assignments and a connection check. Nested entries configure each storage. | File storage |
| A summary of transports and assignments, purpose priorities, the outgoing queue, a test message, the delivery log. Nested entries configure each transport. | ||
| Webhooks | Inbound webhooks: addresses for external systems, sender verification, a call log with the request body. | Webhooks |
| Secrets | Tokens and passwords for {{secret.NAME}} substitution in automation webhooks and notification gateways; the value is never sent back to the browser. | Features & settings |
| Backup | Backup policies, the dump storage, a manual run, the run log. | Backups |
| Audit | The system-wide activity log with filters and control over what is collected. | Features & settings |
| Settings | Default language, the registration and login switches, attachment storage, system mail, the danger zone. | Features & settings |
Slightly apart stands Workflow — an entry in the same Admin dropdown leading to the Statuses and Schemes pages: the states an issue moves through and the transitions allowed between them. See Project configuration → Workflow.
Pages that features bring in
They appear in the same section once the corresponding feature is enabled.
| Section | Feature | What it configures | In detail |
|---|---|---|---|
| Access permissions | advanced-permissions | Grants on a single object, explicit denies, an access check. | Users & permissions |
| Service Desk | service-desk | General help-desk settings: the transport for customer mail, customer access to the portal. | Agent guide |
| Request types | service-desk | What a customer picks from on the portal and which fields they fill in. | Agent guide |
| SD Queues | service-desk | Saved sets of requests for agents to work from. | Agent guide |
| SD Customers | service-desk | Portal customer accounts. | Customer portal |
| SD Approvals | service-desk | Approval steps for requests and who takes part in them. | Agent guide |
| SD Knowledge base | service-desk | Self-service articles and how they map to request types. | Agent guide |
| CSAT SD | service-desk | Customer ratings and their summary. | Agent guide |
| SLA | sla | Target policies: working hours, goals, the statuses that start and stop timers. | Project configuration |
| Automation | automation | Rules, rule templates, the run log, the transport for rule email. | Automation |
| Outbound calls | webhooks-out | Outbound webhooks: address, events, secret, test and delivery log. | Webhooks |
| Notification gateways | notifications | Delivering notifications to external systems, the transport for notification email and the templates for its subject and body. | Features & settings |
| Notification gateways → Messenger types | messengers | A reference for messenger and SMS gateway types: what goes into the settings and into the profile field. | Features & settings |
| Custom Fields | custom-fields | Extra issue fields. | Project configuration |
| Profile fields | user-fields | Extra fields about people and how firmly they are requested. | Project configuration |
| Wave schemas | release-waves | Brand sets and cell statuses for release waves. | Reports & analytics |
| Worklog | worklog | The summary report of logged time for a period, CSV export, timer settings. | Reports & analytics |
| Archive | archive | Restoring and permanently deleting archived issues and projects. | Features & settings |
| Import | import | Migrating data from Jira with project and field mapping. | Features & settings |
| Data transfer | import | Moving data between instances: by files or over the network. | Features & settings |
| “Create” menu | quick-create | Entries of the Create menu in the top bar and their visibility conditions. | Features & settings |
| Single sign-on | sso | OIDC and SAML 2.0 providers and account matching rules. | Single sign-on |
| Storage → S3-compatible storage | storage-s3 | Bucket credentials, an access check, cross-origin rules. | File storage |
| Mail → SMTP / JMAP / AWS SES / SendGrid / Google Workspace / Platform gateway | mail transports | Access to the mail provider, a connection check, a test message; JMAP also receives mail. |
Where to start on a new instance
A sensible order for the initial setup:
- Plugins — enable what you are going to use.
- Storage — connect and assign it, otherwise there are no attachments.
- Mail — enable a transport and assign it at least to system mail, otherwise password reset does not work.
- Users & permissions — roles, groups, permission schemes.
- Issue types, priorities, workflow — to match your process.
- Backup — make sure dumps are taken and leave for the storage.
- Settings — default language, registration and login.
Next
- Plugins — the feature panel and the full catalogue.
- Users & permissions — access.
- Features & settings — instance parameters.
See also
- Installation → After installation — the same steps from the point of view of whoever deploys the instance.
- Configuration → Required in production — what is set at deploy time and cannot be changed from the interface.
- Single sign-on — the section that appears with the
ssofeature. - Agent guide → Configuration — what the Service Desk pages set up.