Assets en CMDB
CMDB-resources beheren
Browse cmdb · Edit cmdb · Cmdb lifecycle
Choose the task you want to carry out. Each procedure includes its prerequisites, steps and safeguards.
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Browse cmdb
Browse cmdb.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Resources are not all stored in one identical table; many resource types have their own schemas and form zone definitions.
- Feature flags and permissions can hide resource groups or individual actions even when code exists.
- Soft deletion is common; do not assume a missing record was physically deleted.
- Relationships are often as important as fields. A server without owners, location, applications, or dependency links is less useful to impact analysis.
- Access groups are linked records, not ordinary asset fields.
- Open Assets or Contacts and choose the relevant resource family.
- Select the specific resource type, such as laptops, servers, applications, certificates, contacts, or locations.
- Use the shared table controls to search, sort, open records, configure columns, and use available row or bulk actions.
- Use visualizers and reports to check relationship coverage and data quality.
Expected outcome: The user has reviewed the result of browse cmdb in the application.
Edit cmdb
Edit cmdb.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Resources are not all stored in one identical table; many resource types have their own schemas and form zone definitions.
- Feature flags and permissions can hide resource groups or individual actions even when code exists.
- Relationships are often as important as fields. A server without owners, location, applications, or dependency links is less useful to impact analysis.
- Link access groups using the offered relationship types.
- Bulk operations should use the resource-specific template because each resource type has different required columns.
- Open Assets or Contacts and choose the relevant resource family.
- Select the specific resource type, such as laptops, servers, applications, certificates, contacts, or locations.
- Use create/edit forms where available to maintain required fields, lifecycle/status, ownership, and operational details.
- Add relationships to owners, locations, dependent services, tickets, access groups, or other infrastructure records.
- Attach documents, certificates, or evidence where the resource needs proof or reference material.
- Use Excel templates for large create/update work instead of manual record-by-record entry.
- Use visualizers and reports to check relationship coverage and data quality.
Expected outcome: The user has reviewed the result of edit cmdb in the application.
Cmdb lifecycle
Cmdb lifecycle.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Feature flags and permissions can hide resource groups or individual actions even when code exists.
- Soft deletion is common; do not assume a missing record was physically deleted.
- Relationships are often as important as fields. A server without owners, location, applications, or dependency links is less useful to impact analysis.
- Lifecycle status, access enablement, source synchronization and deletion are separate states. Do not assume one changes the others.
- Open Assets or Contacts and choose the relevant resource family.
- Select the specific resource type, such as laptops, servers, applications, certificates, contacts, or locations.
- Open the record and review its current lifecycle, status, ownership and operational links.
- Save the intended lifecycle or status change and verify the result.
- Use deletion only when intentional and permitted, after reviewing retained history and related work.
Expected outcome: The user has reviewed the result of cmdb lifecycle in the application.
Aanbevolen werkwijze
- Geef voorrang aan gegevens die dienstverlening, compliance en kosten beïnvloeden.
- Leg relaties vast die een concrete operationele vraag beantwoorden.
Gerelateerde handleidingen
Lees verder in Assets en CMDB
Registraties, relaties, groepen, documenten en CMDB-structuur.