MESH is Soveryne's shared asset register. It keeps one record for each real-world thing your organisation runs, fills itself from the cloud and directory sources you connect, and lets you add the business context and relationships that no source can tell it.
What MESH does
One register for every product. The assets you register in Command, the hosts ATLAS discovers and the resources imported from your sources all land in the same register. Command, ATLAS and MESH show the same records.
Automatic import. MESH reads your Microsoft Azure, Amazon Web Services, Google Cloud and ServiceNow inventory, and people, groups and access from Microsoft Entra and Google directory. It refreshes every hour. See Connecting sources.
Read-only. MESH only reads from your sources. It never changes anything in them.
Context and relationships. You add the things a source cannot know, such as business services, teams, buildings and racks, and connect them: which team is responsible for a service, which system supports it, where a server is located.
A map. The Workspace page draws everything as a map, so you can see how your estate fits together.
Who uses it
Role
What they do here
Admin
Everything: explore the map, add and change context entities and relationships, connect and manage sources, and look at imports, the review queue and activity.
Every other member of the workspace
Explore the Workspace map and list, and open any record. Members cannot change anything.
You sign in through the Soveryne sign-in page. See Single sign-on.
To fill the register automatically, an admin connects at least one source. See Connecting sources. You can also start with the assets your team registers in Command. See Assets in Command.
Getting around
The navigation on the left lists the pages. Members see only Workspace.
Page
What it shows
Who sees it
Workspace
The asset register as a map or a list: assets, context entities and their relationships.
Everyone
People and groups
People, groups and memberships read from your directories and clouds.
Admin
Workload identities
Service accounts, service principals, managed identities, roles and applications.
Admin
Access inventory
Roles, policies and role assignments: who has access to what.
Admin
Connected sources
Your connected clouds and directories, their health and coverage. See Connecting sources.
To go back to the Soveryne portal, select the Soveryne logo at the top left, or select your initials at the top right and choose Return to portal. Log out is in the same menu.
Explore the map
Anyone can do this. Workspace opens as a map.
The Workspace map with assets and context entities grouped by resource type, joined by relationship lines
Each dot is an asset or a context entity. Each line is a relationship.
Dots are gathered into named groups, each labelled with its name and the number of records in it, for example "Applications & systems · 11".
The line under the map counts what is loaded, for example "12 assets · 6 context entities · 8 relationships". The map draws up to 120 dots at a time. If there are more, the line says how many are hidden; use search or filters to narrow the map.
Select a dot or a line to open its record. See Open a record.
To move around:
Drag the background to pan, and use Zoom in (+) and Zoom out (−).
Select Fit graph to fit the whole map on screen.
Drag a group by its rim or name to move it, or drag a dot within its group. Double-click a group to reset it. Select Reset layout to undo all your moves. Your moves are not saved when you leave the page.
Under Layout, choose Constellation or Orbit to change how the map is drawn.
The legend at the bottom (it shows a count such as "18 nodes · 8 connections · 5 groups") explains the line styles: "Solid: connection · dashed: dependency / usage · dotted: events / messages." The colour of a line shows the kind of relationship, for example People / ownership or Physical connection, and an icon on the line shows its type.
Search and filter the map
Type in Search this page… to keep only matching records, by name or type, and the records directly connected to them.
Select Filters to open the filter panel:
Group by changes how dots are grouped: Resource type, Physical location (around buildings, data centres and racks), Business service (around your business services) or Connected groups (records that are linked together). Records that do not belong to a group go to an "Unassigned" group.
Under Resource types, Relationship context and Relationship types, untick a category to hide it. Hidden categories also hide their lines. Select Show all to bring a section back. Filters shows how many categories are hidden.
Relationship labels writes the type on each line. Connection icons shows or hides the line icons.
The Filters panel with Group by, resource types and relationship types
If nothing is left to show, MESH says "No visible nodes". Select Restore graph categories to show everything again.
Watch: exploring the asset map (about 1 min)
Use the list view
Select List view (the list button above the map) to see the register as a table. Select Graph view to go back to the map.
The Workspace list view showing assets and context entities with their kind and description
Under List, choose Resources (assets and context entities, with Name, Asset kind and Description) or Relationships (with their type, context, both ends and purpose).
Select a name in the first column to open the record.
An admin can tick Show removed records (list view) to include removed context entities and relationships.
Open a record
Select a dot, a line or a name in the list. The record opens in a window. Links in a record open in a new tab. Values that are not known show "Not specified".
An asset shows where it came from above its name: "Registered asset" (registered in Command), "Discovered asset" (found by ATLAS), "Imported asset" (read from a connected source) or "Asset". It shows its status, criticality (Low, Medium or High) and owner, an Overview, Identity & network (asset kind, host name, IP address, classification), Relationships (each one incoming or outgoing, with the record at the other end), Discovery (what the source called it) and Record metadata.
A context entity shows its type and status, an Overview, its Relationships and Last update (who changed it last, and when).
A relationship shows its type, its context (business, technical or physical), the two records it connects under From and To, its Purpose, Connection details and Last update.
Select a related record to jump to it. Select Back to to return to the record you came from. Close the window with the close button at the top right.
An asset record with its overview, identity and relationships
Assets can't be changed or removed in MESH. Edit or retire them in Command. See Assets in Command.
Add a context entity
Admins can do this. A context entity is something that matters to your organisation but that no source reports: a business service, a team, a person, a building, a rack.
1
On Workspace, select Add context entity (the + button above the map).
2
Under Category, choose People & business ("People, teams and services"), Virtual ("Systems, software and networks") or Physical ("Places, equipment and devices").
3
Under Entity type, choose the type. The types are:
People & business: Person, Team, Business service.
Physical: Building, Data center, Rack, Physical device, Storage device, Sensor, Vehicle.
4
Under Entity details, enter a Name (required, up to 300 characters).
5
Optionally, enter a Description (up to 4,000 characters) of its role or responsibility in your organisation.
6
Select Add entity.
The Add context entity window with the Physical category and the Building type selected
The window stays open while MESH saves, then closes. The new entity appears on the map and in the list.
Watch: adding a context entity and a relationship (about 1.5 min)
Edit a context entity
1
Open the entity's record.
2
Select Edit entity (the pencil at the top of the window).
3
Change the type, name or description.
4
Select Save changes.
Add a relationship
Admins can do this. A relationship connects two records: an asset and a context entity, two assets, or two context entities.
1
Select Add relationship above the map. To start from an asset, open the asset's record and select Add relationship there: the asset is filled in as From.
2
Under Relationship context, choose:
Business: "Usage, ownership and dependencies", for example supports, depends on, responsible for.
Technical: "Network, data and hosting", for example Database connection, HTTP / HTTPS connection, hosts.
Physical: "Locations, access and equipment", for example Located in, Installed in, Has physical access to.
3
Choose the Relationship type.
4
Under Connect two resources, type part of a name in From and choose the record from the results. Do the same for To. You can search by name or type. Select ⇄ to swap the direction.
5
Check the preview, which reads like a sentence, for example "Grid control system Located in → Control room".
6
Optionally, under Connection details, describe the Purpose (up to 2,000 characters) and Protocol, port or connection details (up to 100 characters). For technical relationships MESH suggests a value, for example "SSH / TCP 22", which you can change.
7
Select Add relationship.
The Add relationship window with a physical Located in relationship and its preview
There is only one relationship of each type between the same two records in the same direction. Adding it again updates the existing one.
Edit a relationship
1
Open the relationship's record, for example by selecting its line on the map.
2
Select Edit relationship.
3
Change what you need and select Save changes.
Remove and restore context
Admins can do this.
1
Open the record of the context entity or relationship.
2
Select Remove entity or Remove relationship (the bin at the top of the window).
3
Read the confirmation and select Remove.
Removing keeps the record for audit; it no longer appears on the map. Removing a context entity also removes all its relationships.
To bring a record back:
1
Select List view and tick Show removed records (list view).
2
Open the removed record and select Restore / edit.
3
Select Save changes.
Relationships removed together with an entity are not restored with it. Restore each one you need.
People, workload identities and access
Admins can see three read-only pages filled from your connected directories and clouds. They are empty until a source with that coverage has completed an import.
People and groups: people, groups, group memberships and cloud user accounts.
Workload identities: service accounts, service principals, managed identities, cloud roles and applications.
Access inventory: roles, policies, role assignments and access relationships, including principals MESH could not resolve.
Each page lists records with Kind, Name, Address, Provider, Scope and Active, 50 to a page. Use Previous and Next to page through, and select a record to see all its details.
Activity
Admins can see Activity: a list of changes to assets in the register. The columns are Asset (the asset's name), Application (Command, ATLAS, or MESH for an import from a connected source), Actor (the person who made the change) and At (when). Select an entry to see which fields changed.
Where MESH cannot tell who a person is, it shows "Workspace member".
Changes to context entities and relationships are not listed here. Their record shows who changed them last, under Last update.
How Command and ATLAS feed MESH
Product
What it adds
Where you change it
Command
The assets your team registers, with their owner, criticality and classification. Command also shows each asset's imported facts and the review queue.
Cloud resources, CMDB items, people, groups, identities and access.
At the source. MESH reads it again every hour.
MESH
Context entities and relationships.
MESH Workspace.
In Command, open Assets and select Connected sources to see a summary of your sources and the review queue. Select Open MESH there to manage the connections in MESH.
Assistants
MESH has no assistant yet.
Coming soon
An assistant that gives your assets context by generating the relationships between them automatically.
How MESH protects you
MESH never writes to your sources. It only reads.
No credentials pass through your browser. You sign in at your provider's own page; MESH accepts only the genuine Microsoft, Google, AWS and ServiceNow sign-in addresses.
Nothing disappears by accident. An import that could not read everything never removes records. When an import would mark a large number of records as gone, it waits for a person to confirm. See Review queue and import history.
Imports never overwrite people. Fields your team owns, such as owner and criticality, are never changed by an import, and no source overwrites another source's facts.
Duplicates are merged only on strong evidence. Weaker matches become a question for a person. A merge can be split again in Command.
Removal keeps history. Removed context and relationships are kept for audit, and a removed source's inventory stays available as stale data unless you choose to delete it.
Only a signed-in person can change the register. Every change is linked to the person who made it.
Troubleshooting
Message
What it means
What to do
"Your workspace is ready" / "Add context entities and connect a synchronization source to build your asset graph."
The page has no records yet.
Add a context entity, register assets in Command, or connect a source.
"No matching resources"
Nothing matches your search.
Clear or change the search.
"No visible nodes"
Your filters or search hide everything.
Select Restore graph categories, or clear the search.
"Records could not be loaded"
MESH could not fetch the register.
Select Refresh. If it keeps failing, reload the page.
"Return to the application portal to sign in."
Your session has ended.
Go back to the Soveryne portal and open MESH again.
"Enter a name."
A context entity needs a name.
Type a name.
"Choose a resource from the results."
From or To is not a record from the list.
Type part of the name and select a result.
"Choose two different resources."
From and To are the same record.
Choose a different record for one end.
"Add a context entity or import assets first."
There is nothing to connect yet.
Add a context entity or connect a source first.
"Choose an existing active endpoint from this workspace."
