Creating and Managing Entities

In Service Mapping, all documentation is built around Entities, such as IT Services, Applications, Vendors, or Customers. Each entity is represented by a Card: a structured page that follows a predefined Layout and contains all related information and assets.

This guide explains how to create and maintain cards in vScope.

Creating a New Card

1. Open Service Mapping Click the Service Mapping icon in the vScope sidebar, and then click Create.

2. Choose Entity Type Select what kind of entity you want to document, for example, IT Service, Application, or Vendor. This choice determines which layout will be used for the card.

3. Add Basic Information Give the card a name and a short description. These fields help others understand the purpose of the entity and its role in your organization.

4. Create Card Click Create to save your new entity and open it for editing.

Adding Information

Once the card is created, you can start filling in details using the fields and tables defined by its layout.

Tip

Use tables for any information that comes from vScope’s asset repository. It allows you to display live asset details and keep your documentation automatically up to date.

Managing Relationships

Cards can link to other entities to show dependencies or ownership. For example, an IT Service may depend on several Applications or Vendors.

Adding relationships helps visualize how systems and services connect across your organization and makes governance documentation more meaningful.

Saving and Editing Cards

All changes to a card are saved automatically. You can update fields, add assets, or modify relationships at any time.

• Collaborators can edit cards according to their permissions, managed through Collaboration Access Control (ACL).
• Administrators can update the layout or structure behind a card, affecting all cards of the same type.

Tip

Keep ownership and contact information up to date, it’s one of the most valuable parts of maintaining accurate governance documentation.

Summary

Creating and maintaining cards is the core of Service Mapping. By combining layouts, asset data, and collaboration, you can build a complete, living service catalog that connects your business and IT operations.

---

Frequently Asked Questions

Can I change the layout of an existing entity?

No. Once a card is created, its layout cannot be changed. If you need a different layout, you can create a new card by duplicating the existing one and then select the preferred layout during creation.

Can I view my documentation in tables as well?

Yes. Each entity type, including IT Services, is also available as an asset type in vScope Tables. This means you can build custom views and reports just like for any other asset type.

You can also use vScope’s standard features such as:

• History & Compare to track changes and trends over time
• Tracker to set up alerts when documentation changes, or something breaks a policy
• Dashboards to create visual overviews of your services and governance status

Will my documentation update automatically when assets change?

Yes. Information about linked assets is automatically updated. If an asset is no longer discovered by vScope, a warning will appear to indicate that the asset is missing. To ensure quality governance, users should actively review and update the assets linked to each entity when needed.