Administration

Everything an admin runs: who gets in, what they can see, what the instance is licensed for, and what happened last Tuesday.

You are an admin if you are an owner or admin of at least one nexus that other people are in. Your own private nexus does not count, so signing up does not make you an administrator of anything. There is no separate super-user account.

Admins get a wrench icon in the rail down the right edge, below their avatar. It opens the Admin panel, which is where all of this lives.

In this chapter

Admin Settings - reaching the Admin panel and what every section does.
Users and Groups - adding people, roles, groups, and space permissions.
Authentication - local accounts, LDAP / Active Directory, and OAuth.
Audit Log - what gets recorded and how to search it.
Licensing - tiers, signed keys, plugin entitlements, moving a license.
Your Account Settings - the per-user panel every account has, admin or not.
LDAP and Active Directory Setup - the step by step guide, with worked examples and troubleshooting by symptom.
Emoji covers the standard set, docu.nexus icons as emoji, and adding and removing custom emoji.
Chat settings - Admin -> Chat: how long notifications are kept, presence by default, who may add custom emoji, who may create channels, archived channels, and renaming or turning off #general.

Before you start

Administration is instance-wide: the panel has no selected nexus. What a nexus admin can change is decided per nexus, and where an action needs a nexus, such as placing a person or importing an archive, the nexus is a field on that action’s own form.

Some settings belong to the instance administrator alone: Licensing, the directory connections on the LDAP tab of Authentication, and anything driven by environment variables (OAuth providers, registration, storage). Only an instance administrator sees licensing and the directory connections. Those are covered in Licensing, Authentication and LDAP and Active Directory Setup.