Administration

Admin Settings

Opening the panel

Click the wrench icon in the rail down the right edge. The Admin dialog opens with a section list down the left.

The controls at the top of that rail (your avatar, Otis where it is licensed, and the wrench) stay usable while the panel is open, so you can send feedback about what you are reading without dismissing it. Notifications are the Notifications channel in Chat, in the sidebar. Pressing the wrench again puts the panel away.

The icon only appears if your account is an owner or admin of at least one nexus that other people are in. The private nexus every account gets does not count towards this. Non-admins never see it, and the panel refuses to render for them.

There is no nexus picker

The panel is instance-wide and holds no selected nexus. A list that holds rows from several nexuses lists them all and names the nexus beside each, and an action that needs a nexus asks for it on its own form. Your own private nexus is managed from its own card on the nexus list, not from this panel.

Sections

The list is grouped: Instance, People & access, Content, Licensing, and finally Plugins when any are loaded.

Group	Section	What it controls
Instance	Nexus	Every nexus, one row each, with its read-only URL slug. Rename a nexus from its row. Each row also has a delete button, which opens a confirmation listing what goes with the nexus (its spaces, pages, versions, comments, attachments, labels and templates) and asks you to type the nexus name before Delete nexus can be pressed. The delete is permanent and nothing goes to the Trash. People keep their accounts. An instance administrator who has joined a nexus as admin also has a Make this nexus a space in another nexus button on its row, described below.
Instance	Appearance	Instance-wide defaults, in four cards: Instance default look, Instance default theme, Container covers, and Profile pictures (the Gravatar lookup switch).
Instance	Advanced	Default member role for invitations, plus the two sharing policies: allow public share links, and require a password on public shares.
Instance	Audit Logs	Searchable record of actions in the nexuses you administer. An instance administrator also sees the instance’s own entries.
People & access	Authentication	Which sign-in methods the instance offers, on the Sign-in methods tab, plus the LDAP tab (the instance’s directory connections, with Test connection and Sync users now) and Single sign-on (GitLab sign-in: which GitLab, its application, who may sign in, and Test). The LDAP tab is shown to instance administrators only, because a directory connection belongs to the instance and to no nexus. See Authentication and LDAP and Active Directory Setup.
People & access	People & Access	One list of people, groups and spaces. Pick one, and the pane beside it shows the account, its nexus roles, its group memberships and what it can reach. Add people to a nexus, change roles, remove them; create, rename and delete groups and change who is in them. The old Members and Groups links open here. A directory is synced from its connection on the LDAP tab, and places nobody into a nexus; GitLab group sync is on the Single sign-on tab. An instance administrator also sees Connections there: pick a connection, and every nexus on the instance is a row with a switch for whether it may use it.
Content	Labels	Manage the nexus label catalog: create, edit, recolor, delete.
Content	Templates	Manage nexus-level page templates.
Content	Document Templates	The cover, header and footer a page wears when it is exported as a PDF or a Word document. Instance-wide, and changed by instance administrators only. See Export and Import.
Content	Import	Confluence import: saved connections, space selection, export-archive upload, live progress, and the deficiency report. Absent unless the deployment sets `ENABLE_CONFLUENCE=true`.
Content	Sync	Confluence sync configuration. Absent unless the deployment sets `ENABLE_CONFLUENCE=true`.
Content	Connections	Saved credentials for external systems, including the Git host credentials private repositories need and the GitLab connections boards reach GitLab through (a GitLab connection also says whether boards act as each viewer or as its own token). A connection belongs to the instance: only an instance administrator adds, edits or deletes one, and Nexus access on its card opens the nexuses that may use it. A nexus admin sees, read-only, the connections their nexuses may use.
Licensing	Licensing	License status, entitlements and which key granted each, the installed keys, and the install fingerprint. Instance-wide, not per nexus.
Licensing	Plugin Registry	Read-only inventory of every loaded plugin and what its manifest declares.

Import and Sync are the two sections the Confluence surface owns, and that surface is off unless the deployment switches it on. On a default install neither section is in the list at all: there is no Off chip and no switch to turn, because the routes behind them are not running. Only ENABLE_CONFLUENCE=true in the deployment’s environment brings them back, and it takes a restart. See Configuration Reference. Everything below describes an instance that has them.

Only some sections can be switched off when an instance does not use them. Seven carry the switch, in the header of the section itself: Appearance, Advanced, Groups, Labels, Templates, Import, and Sync. The other eight have no switch: Nexus, Members, Licensing, Audit Logs and Authentication describe the instance itself and always stay on, and none of Connections, Plugin Registry and Document Templates carries one.

Authentication lost its switch when it stopped being the LDAP-only section: it now also covers email and password sign-in, which no instance can be without, so each sign-in method carries its own switch inside the section instead. An instance that had switched the old LDAP / SSO section off keeps that statement: it is read as “the LDAP method is off”.

A switched-off section keeps its configuration, shows an Off chip in the list, and can be switched back on from the bar at the top of it.

Make a nexus a space in another nexus

A nexus that should have been one space among others can become one. It is an instance administrator’s act, and you must have joined both nexuses as admin (Instance administrators, Join). On the Nexus section, press the Make this nexus a space in another nexus button on its row, and pick the nexus it goes into.

The dialog says what will happen before anything does:

A new space named for the nexus, in the nexus you picked, holds one folder for each of its spaces, with every page in them. Page addresses do not change, and the old addresses of the nexus and its spaces lead to the new space and its folders.
The new space’s access list is the old roster: admins get Full access, members Edit, guests View. Each space’s own access list is removed, and every share link on the pages stops working.
What changes for people, by name, both ways, and who can newly open or can no longer open its sealed pages: the administrators of the nexus you picked can open them without being granted them, and this nexus’s administrators no longer can unless they administer that one too.
Labels, label groups, groups, nexus-wide templates and saved searches move to the nexus you picked. A label whose name that nexus already uses is replaced by its label there.
What goes with the nexus and does not move: agent tokens limited to it, Confluence syncs set up for the whole nexus, and its import records with any repairs still open on them. A connection this nexus may use and the one you picked may not is named, because boards, Git Docs pages and syncs that use it stop until it is allowed there.
The nexus’s audit history is kept at instance scope, naming the nexus, and the nexus itself is deleted. It does not go to the Trash.

It cannot run while a member of the nexus is not also a member of the nexus you picked (the dialog names them), while there are pending access requests or messages in its channels, while any of its spaces is in the Trash, while a group in it grants instance administrator, while its Requirements has a systems tree, mirrored external items or collection templates (which cannot move to another nexus yet), or for more than 20 spaces at once. Type the nexus name, then press Make it a space.

The instance default look

Admin, then Appearance, then Instance default look sets the look for everyone who has not picked one of their own, including the sign-in page. A person’s own choice always wins over it. Standard is the default until you change it.

Pick a row and the check appears beside it; the change is recorded in the audit log. People who follow the instance see it on their next page load, and people who chose a look keep theirs.

Try shows a look in your window only, so you can see it before anyone else does. The bar at the foot of the window switches between the look’s two halves, and Make it the instance default saves it for everyone. Go back returns your window to how it was. On a read-only instance the try still works, and saving is refused with the read-only explanation, as it is for the theme.

The Instance default theme previews show the halves of the instance default look, because that is what the people they affect will see.

Plugin sections

Installed plugins add their own sections under a Plugins heading at the bottom of the list. Each plugin owns its tab and its own settings.

Plugin	Section
Requirements	Capabilities
Kanban	Kanban
Databases	Databases

A locked plugin keeps its section in the list, marked Locked, and both its admin tab and its pages are replaced with a “locked” card. An instance administrator gets an Open Licensing button on it; a nexus administrator, who cannot open Licensing, is asked to have an instance administrator add the key. See Licensing.

Your own settings are elsewhere

Personal settings (Profile, Appearance, Security, Emoji) are not in this panel. They live in the Preferences panel under your avatar, at the top of the same rail. See Your Account Settings.

There is no separate settings URL: /settings and everything beneath it redirect to /nexus. Everything administrative is in the Admin panel above, including Confluence sync, which the panel exposes as its own Sync section on an instance that has the Confluence surface switched on.