Using the Admin Panel

The Administration page shows up for admins and the owner. It has four panels: Server Management, User Management, Device Management and the Console.

Screenshot of the Administration page

Server settings

The left of Server Management is a live editor for serverconfig.conf. Saving writes the file and updates the running server, so every change takes effect immediately for every client that connects. No restart.

Section	Settings
Identity	Organization name, timezone. The name is what shows next to the globe in everyone's menu bar.
Network	Client port and web access port.
Limits	Max devices per user, and the online window in seconds that decides who reads as online.
Scope	Who can see the members list and who can see availability.
Naming	Whether cross-OS-safe file names are enforced, and how long staged uploads survive.
Invite codes	Turn project invite codes off entirely.
Visibility	Enable organization features, and hide the owner account from the user list.

Projects and invite codes

Server Management also manages projects and the members within them: create one, delete one, and handle its codes. Each project has a permanent code you can switch on or off and a temporary code you can regenerate whenever you want to cut off whoever has the old one.

Users and roles

User Management lists every account with its role.

Role	Can do
Member	Normal work: their own projects, their own devices.
Admin	Everything a member can, plus the Administration page, user management and force-unlock.
Owner	Everything. The role is fixed — it cannot be changed from here, including by the owner.

Disabling a user drops their sessions and keeps the handle reserved; adding that handle again reinstates the account rather than creating a second one. You cannot disable the owner or yourself.

Devices

Device Management lists registered devices and what each one currently holds. Removing a device releases its locks and invalidates its session, which is the clean fix for a lost laptop that is holding the rig file hostage.

Force-unlocking

A stale lock that its holder cannot release — wrong machine, someone on leave — comes off with a force unlock, from the file tree's context menu or the CLI:

cambium unlock -f //Assets/player.fbx

The -f is mandatory; without it the command refuses. The holder's client notices and tells them it happened, rather than letting them find out at submit time.

Shutting the server down

Server Management has a Shutdown button. It stops the process cleanly and that is all it does — the server will not come back on its own unless you have a restart policy or a service unit that brings it back. It is a way to cycle the process or to apply a port change.