Skip to content

Editing Entities

Editing entities in Legend is straightforward. You can modify any field after creation, whether you need to update a description, add a link, change ownership, or adjust relationships.

There are two ways to edit an entity:

Method 1: From the Detail Drawer

  1. Click the entity card on the dashboard to open the detail drawer
  2. Click the Edit button in the top-right corner of the drawer
  3. The editing wizard opens with the entity’s current data pre-filled

Method 2: From the Entity Card Menu

  1. Hover over the entity card on the dashboard
  2. Click the three-dot menu icon in the top-right corner
  3. Select Edit from the menu
  4. The editing wizard opens with the entity’s current data pre-filled

Both methods open the same four-step wizard you used during creation, but with all existing data pre-populated.

Entity detail drawer showing entity information, relationships, and edit options

The editing wizard has the same four steps as the creation wizard:

Update the core information about your entity:

  • Name, description, category (for landmarks)
  • Icon, owner, email, title, teams (depending on entity type)

All fields are pre-filled with current values. Modify any field and click Next to continue.

Add, remove, or modify quick-access links:

  • Update existing link titles, URLs, or icons
  • Add new links by clicking Add Link
  • Remove links by clicking the trash icon next to each link

Links are saved in the order you arrange them. The first link appears most prominently on the entity card.

Edit existing documentation or add new files:

  • Click a documentation tab to edit that file
  • Add new documentation by clicking Add Documentation
  • Remove documentation by clicking the trash icon

Documentation is stored as markdown files and supports full markdown syntax.

Update tags, relationships, and access control:

  • Add or remove tags
  • Modify dependencies and relationships (for landmarks)
  • Adjust access groups and edit groups

Click Save to apply all changes.

To update an entity’s description:

  1. Open the detail drawer
  2. Click Edit
  3. In Step 1, modify the Description field
  4. Click Next through the remaining steps (or click Save if available)
  5. The updated description appears on the entity card immediately

To transfer ownership of a landmark:

  1. Open the landmark’s detail drawer
  2. Click Edit
  3. In Step 1, change the Owner field to a different team or person
  4. Complete the wizard and save
  5. The ownership change is reflected on the landmark card and in the topology

To update a person’s team memberships:

  1. Open the person’s detail drawer
  2. Click Edit
  3. In Step 1, modify the Teams field
  4. Select additional teams or deselect current teams
  5. Complete the wizard and save
  6. The person’s card updates to show the new team count

To add or remove dependencies and associations:

  1. Open the landmark’s detail drawer
  2. Click the Relationships tab
  3. Click Add Relationship to create a new relationship
  4. Select the relationship type (depends on, related to)
  5. Search for and select the target entity
  6. Click Save

To remove a relationship:

  1. Open the Relationships tab
  2. Find the relationship you want to remove
  3. Click the trash icon next to the relationship
  4. Confirm the deletion

To modify documentation files:

  1. Open the entity’s detail drawer
  2. Click the Docs tab
  3. Click the documentation file you want to edit
  4. Modify the markdown content
  5. Click Save to apply changes

Documentation changes are saved immediately and are searchable.

Legend does not currently support bulk editing of multiple entities at once. To update multiple entities, you must edit each one individually.

Workaround for bulk updates: If you need to update a field across many entities (for example, adding a tag to all production services), you can:

  1. Edit the YAML files directly in the data directory
  2. Use a text editor or script to make the changes
  3. Restart the Legend container to reload the data

Who can edit an entity depends on your user role and the entity’s access control settings:

Administrators:

  • Can edit all entities regardless of access control settings

Users with Edit Groups:

  • Can edit entities where they belong to an edit group
  • Edit groups are configured in Step 4 of the editing wizard

Regular Users:

  • Can edit entities they have access to (based on access groups)
  • Cannot edit entities with restricted edit groups they don’t belong to

If you cannot edit an entity, the Edit button will not appear in the detail drawer. Contact your administrator to request edit permissions.

When you click Save in the editing wizard:

  • All changes are validated
  • The entity’s YAML file is updated
  • The audit log records the change
  • The entity card refreshes to show updated data
  • Relationships are recalculated in the topology

If validation fails (for example, a required field is missing), the wizard displays an error message and prevents saving. Correct the error and try again.

Legend does not have an undo feature for entity edits. If you make a mistake:

  1. Open the entity’s detail drawer
  2. Click Edit
  3. Manually revert the changes
  4. Save the entity

For critical data, consider creating a backup before making significant changes. See Backups and Recovery for details.

Edit incrementally:

  • Make small, focused changes rather than large overhauls
  • Test changes by viewing the entity card and detail drawer after saving
  • Use the topology explorer to verify relationship changes

Document significant changes:

  • If you change ownership, add a note in the documentation
  • If you modify dependencies, update the runbook if applicable
  • If you change access control, notify affected users

Review before saving:

  • Click through all wizard steps to review changes
  • Verify that links still work after URL changes
  • Check that relationships make sense in the topology

Use version control:

  • If you’re comfortable with YAML, use Git to track changes
  • Commit changes with descriptive messages
  • Use Git history to review what changed and when