Edit or remove a server
Rename a server, manage tags, tune surveillance thresholds, and safely delete a server in Servor with a retype-name confirmation to prevent mistakes.
Every server has a settings panel where you can rename it, organize it with tags, tune its surveillance thresholds, or remove it entirely. This page walks through each of those, including the retype-name confirmation that keeps you from deleting the wrong server.
Open server settings
Open the server
In Servers, click the server you want to change.
Click the gear icon
The gear icon opens settings. It holds the server's info, its surveillance thresholds, agent repair, and the delete action.
Who can edit
Editing settings and deleting a server require write access. Members can edit server details; creating and deleting servers is an admin-level action. Viewers are read-only. See roles and permissions.
Rename and tag
- Name — give the server a name you'll recognize at a glance. Renaming is safe and takes effect immediately; it doesn't touch the agent or any history.
- Tags — attach tags to group and filter servers (for example
production,staging,db, or a client name). Tags make large fleets easier to scan and filter.
Arrange the fleet into sections
The server list can be split into sections — prod, staging, a customer, a datacentre. An admin creates one with New section, gives it a name and a colour, then drags servers into it by the grip that appears on hover. The sections themselves reorder the same way, by the grip to the left of their heading. Each section folds away with a click on its heading.
Deleting a section deletes no machines
The servers it held simply return to Unsorted. A section is a way of looking at a fleet, not a container: losing a machine because somebody tidied up a heading would be indefensible.
Worth knowing:
- Admins only. Members and viewers see the sections but do not rearrange them: they are shared furniture, and moving one changes what the whole team sees on the screen they open first.
- Folding is personal. Collapsing a section collapses it for you alone.
- Until a section exists, the list looks exactly as it did — headings appear only once the first section is created.
- Tags are still there and do a different job: a machine belongs to exactly one section, but carries as many tags as you like.
Choose who sees which servers
By default the whole team sees every server. An admin can restrict a machine to certain people: the Visibility button above the list opens a grid with servers down the side and members across the top.
Ticking is what restricts
A row with nothing ticked stays visible to the whole team. Only ticking restricts: the server then disappears for everyone who is not ticked. To undo it, untick everyone — which is what “Make visible to everyone” does.
Worth knowing:
- Admins and owners always see everything. They are not in the grid: a checkbox that changed nothing would be misleading, and being able to remove your own access to the grid is a trap.
- The restriction covers everything, not just the list: terminal, files, commands, logs, copilot and local services all refuse a server that is not granted.
- Monitoring keeps running on a restricted server: monitors, alerts and scheduled commands belong to the machine, not to a person.
- Public API tokens belong to the team and see the whole fleet — they inherit nobody's individual grants.
Surveillance thresholds
Surveillance thresholds decide when a server's resource usage counts as a problem. The resource metrics — CPU, RAM, and disk — are collected by the agent, and thresholds set the line between healthy and alerting.
Set your limits
In settings, adjust the CPU, memory, and disk thresholds to values that make sense for this machine. A database box and a small web server rarely want the same limits.
Save
Save your changes. Servor uses these thresholds when evaluating the server's health going forward.
Pair thresholds with alerts
Thresholds define what "too high" means; alerts and notification channels decide how you hear about it. Set both so a crossed threshold actually reaches you.
Delete a server
Deleting a server removes it from Servor along with its history and configuration. To prevent accidents, Servor asks you to retype the server's name to confirm.
Open settings and choose Delete
In the server's settings (gear icon), find the delete action.
Retype the server name
Type the server's exact name into the confirmation box. The delete button stays disabled until the name matches — this is your safeguard against removing the wrong server.
Confirm
Confirm to delete. The server disappears from your list.
Deleting is permanent
Removing a server also removes its command history and configuration in Servor, and this can't be undone. The agent on the machine is no longer managed by Servor. If you only need to fix a broken connection, don't delete — repair the agent instead.
Clean up the agent on the machine
Deleting a server in Servor stops managing it, but doesn't uninstall the agent from the machine itself. If you're decommissioning the box, remove the agent there as part of your teardown.