Service Inventory

Keep a register of the business and IT services your organisation runs, each one labelled with how critical it is, so that everyone names the same service the same way when they write up a risk, an incident or an audit scope.

A service here is something your organisation provides or depends on — a customer portal, a payroll system, an internal API. It lives in the CMDB (Configuration Management Database — the record of the technology you operate) beside machines, software, information assets and external services. The Service Inventory is the lightest of those registers. A service is a name, a criticality, an optional type, an owner and a service-level target, and you fill it in by hand, one service at a time. That is deliberate: this is the compliance-facing list of services that matter for your posture, not a copy of your IT operations catalogue.

Who uses it

The CMDB module must be switched on for your tenant. While it is off the ASSETS (CMDB) entries are left out of the left menu and the underlying requests are refused. After that, what you can do depends on your role:

What's on this screen

Open /cmdb/services. The page is headed Service Inventory with the subtitle Manage business and IT service assets in the CMDB., and the primary action, Add Service, sits at the top right. Under the header is a slim filter bar holding three controls: a Search services... box, its Search button, and an All criticalities dropdown.

Below the filter bar is the table. Its columns are Name — with the description in smaller grey text under the name, where one has been entered — then Criticality as a coloured badge, Type, SLA Target, Owner and Actions. Rows are ordered by name and are not clickable: there is no service detail page, so the only row action is the Edit link in the last column. In the Type, SLA Target and Owner columns a value that was never filled in shows as - rather than an empty cell; a service with no description shows nothing under its name.

Under the table sits the pagination row — Showing 1-2 of 2 on the left, and Previous, Page 1 of 1 and Next on the right, both buttons greyed out when there is only one page. The page holds twenty services at a time. In the capture the register has two entries: AI service (High, type AI client access) and Test portal (Critical, type Client access, carrying the description Test under its name). Both show 99.95% as their SLA target and both are owned by Test Admin 1 on a staging tenant. The round violet button at the bottom right is the app-wide AI assistant, not a service feature — this screen has no AI of its own.

The four numbered circles on the figure below mark what to find first, in the order the steps walk them.

  1. In the left menu, open the ASSETS (CMDB) group and select CMDB Services. The group stays expanded and the entry stays highlighted while you are on this page, so you can move between the sibling registers without losing your place.
  2. Check the account name in the top bar before you judge what is missing. That account's role decides whether the Add Service button and the whole Actions column are drawn — the capture is signed in as Test Contributor 1, so both appear.
  3. Each row ends with an Edit link. Select it on the AI service row and the Edit Service Asset dialog opens over the table, already filled with that service's stored values.
  4. The same link on the Test portal row opens the same dialog for that record. Aegis builds the dialog fresh for whichever row you chose, so opening a second row never shows you the first row's details.
The Service Inventory with two services recorded, captured as a Contributor — /cmdb/services.
The Service Inventory with two services recorded, captured as a Contributor — /cmdb/services.

Add a service

There is no separate page for creating a service. It happens in a dialog over the list, and the list reloads itself when you are done.

  1. Select Add Service at the top right. A dialog titled Add Service Asset opens over the table.
  2. Type a Name — the placeholder suggests e.g. Customer Portal. This is the only required field. Submit without it and the dialog stays open with Name is required in red under the box.
  3. Add a Description if it helps a colleague recognise the service. Whatever you write appears under the name in the list, and the search box looks inside it.
  4. Set the Criticality. The choices are Low, Medium, High and Critical, and it starts on Medium. This is what the coloured badge in the list shows.
  5. Fill in the optional fields as you have them: Service Type (the placeholder offers e.g. Business, IT, Infrastructure), SLA Target (such as e.g. 99.9% uptime), comma-separated Tags, and free-text Notes.
  6. Select Add Service in the dialog to save, or Cancel to abandon it — cancelling discards what you typed. On save the dialog closes, the table reloads, and the new row takes its place in name order.
The owner is whoever adds the service

Neither dialog has an owner picker. Aegis records the person creating the service as its owner and keeps showing that name in the Owner column — which is why both rows in the capture read Test Admin 1 although the screenshot was taken by a different account. If ownership has to move, raise it with your Aegis contact. The column shows - only when no owner can be resolved at all.

Service names must be unique

Saving a name that already exists is refused. The dialog stays open with your text intact and A service with this name already exists appears above the fields. Check the list first if two teams might describe the same service differently — one register with agreed names is worth more than several near-duplicates that nobody can reconcile later.

Correct an existing service

Criticality, service type and SLA target all change over time. Editing a row is what keeps the register honest, and it is the only way to correct a criticality through the product.

  1. Find the row and select Edit. The Edit Service Asset dialog opens with every field already carrying the stored value.
  2. Change what needs changing. The dialog lays the fields out in two columns — Name, Criticality, Service Type, SLA Target and Tags across the top, with Description and Notes running the full width beneath.
  3. Select Save Changes. The dialog closes and the table reloads, so a changed criticality shows straight away as a differently coloured badge, and a renamed service moves to its new position because the list is ordered by name. The change is written to the audit log under your name.
Clearing the tags field clears the stored tags

The edit dialog always sends the whole record, so emptying Tags and saving removes every tag from that service. Owner is not one of the fields in the dialog, and saving leaves it exactly as it was.

Find a service

The two filters work together, and changing either sends you back to the first page.

  1. Type into the Search services... box. After a short pause the table reloads by itself, matching your text against the name, the description and the type, ignoring case. The Search button and the Enter key change nothing further — the list has already updated.
  2. Pick a level from the All criticalities dropdown — Critical, say — to show only services at that level. Set it back to All criticalities to drop the restriction.
  3. If nothing matches, the table is replaced by No services match the current filters. Clear the box and reset the dropdown to bring the full register back.

The empty state

Before anyone has added a service, the page shows No services yet. Add your first service asset to get started. in place of the table. That is not an error — the register has not been started yet. Add one service and the table, the pagination row and (if your role allows it) the Edit links take its place. Read that message as a different thing from No services match the current filters., which means services do exist but your search text or criticality filter is hiding them.

Removing a service

Deleting is the exception on this screen. Contributor and above hold the delete permission and the API endpoint exists, but no screen in Aegis draws a delete control for a service. In practice a service you no longer run is edited — a note recording that it was retired, and a lower criticality — rather than removed. If a row genuinely has to go, raise it with your Aegis contact and be sure first: a service delete removes the record outright rather than marking it as deleted, so it cannot be restored from the screen. The deletion itself is written to the audit log.

Tips and limits

Where this connects