Documentation Index
Fetch the complete documentation index at: https://backstage.spotify.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Entity overlays is a process originally created to handle use cases of updating metadata of entities ingested into the Software Catalog directly from external sources instead of through manual entity creation, such as those in the data registry, but can be applied to any entity in the Catalog. Applying an overlay does not change the metadata at the source or in the Catalog but decorates the entity in an reversible manner for simpler entity management through Portal’s UI. Overlays currently supports adding labels, annotations, and tags and updating the owner and the lifecycle.Use Cases
Any scenario where there is a need or want for different metadata to exist in Portal than the original source of the entity, including but not limited to:- Decorating an entity with extra metadata only needed in the Software Catalog and not the source
- Adding tags to make an entity more easily searchable in the Catalog
- Defining a relationship between entities just in Portal with labels
- Add annotations that are required for other plugins to show on the entity
Permissions
There is a default RBAC policy in place to protect entities from being unexpectedly updated. These rules are:- Portal admins can always update an entity (Entity overlays admin role)
- The owner of an entity can update their entity (Entity overlays user role)
- If an entity has no owner defined in the catalog, any user can update this entity (Entity overlays user role)
entity-overlays.overlay.update permission.
How To
On a given entity page needing an update, go to the ellipses menu in the top right corner.
Edit entity overlay will open the overlays form.

Add after each tag addition.

Save and a confirmation will pop up.
