ITAM / Servers

Edit Server

Keep server records accurate when IPs change, hosts move clouds, or you enter a planned maintenance window.

Real-world scenario

Carlos Reyes · IT Admin at Bluewave Labs

api.workverge.ai is moving to a new Hetzner IP tonight. Carlos updates the IP and sets status to Maintenance so uptime alerts do not wake anyone during the cutover.

Before you begin

  • ITAM license enabled
  • Admin or asset manager role with edit permission
  • Server already exists in the list

Overview

Server records should reflect reality, especially IP, status, and cost. Carlos edits from the servers list drawer; there is no separate full-page edit URL to hunt for. Changes save immediately and appear in filters, exports, and the CMDB.

How to edit

  1. 1

    Find the server in ITAM → Digital Assets → Servers

    Use search if you know the name or IP, e.g. api-WorkVerge-prod or 52.58.14.22.

  2. 2

    Click Edit from the row actions

    The edit drawer opens with current values pre-filled.

  3. 3

    Update the fields you need

    Common changes: status to Maintenance before a patch, new IP after migration, updated monthly cost.

  4. 4

    Click Save

    WorkVerge validates your changes and converts price to org currency if you changed cost or currency.

Editable fields

  • Name. Rename when your naming convention changes
  • Server type. Reclassify when a box takes on a new role
  • IP, username. Update after migration or credential rotation
  • Provider, region. Fix metadata when a VM moves clouds
  • Price, currency, purchase date. WorkVerge recalculates org-currency cost
  • Status. Active, Inactive, or Maintenance
  • Maintenance cost. Optional recurring ops spend separate from hosting
  • Tags, description. Notes for your team and filters

Example

Maintenance window for api.workverge.ai

Carlos opens api-WorkVerge-prod, changes Status to Maintenance, updates IP from 52.58.14.22 to 95.217.8.41, and adds to description: "Cutover 2026-06-10 02:00 UTC. Hetzner fsn1 rebuild." After smoke tests pass, he sets status back to Active.

Cloud-synced servers

If the server came from an AWS or Hetzner integration, the next sync may overwrite provider metadata. For manually managed fields, add a note in description so the team knows what sync should not clobber.

Related articles