Defining ownership

Overview of ownership in Cortex

Every entity in your catalog should have a clear answer to the question: who is responsible for this? Ownership is what makes that answer reliable.

In practice, ownership does more than assign a name to an entity. It's the connective tissue between your catalog and your workflows. It determines who gets notified when an incident fires, who's accountable when a Scorecard degrades, and who needs to act when verification lapses. Without it, alerts go unanswered, reviews stall, and gaps in your platform go unnoticed.

Cortex gives you several ways to establish ownership:

• Automated recommendations based on repository activity

• Definitions pulled from your identity providers and version control integrations

• Manual assignment in the UI

• Inheritance from parent entities in your hierarchy.

However you get there, the goal is the same: every entity has an accountable owner, and that owner is always current.

Avoid inefficient manual processes by using Cortex's Ownership tool to solve entity ownership quickly. Cortex automatically predicts entity owners so developers can skip the guesswork and reach the right person immediately.

Viewing entity owners

When viewing an entity, the owners appear in the metadata bar on the right side of the page:

If the entity is owned by a team, click the team name to open the team's entity page, which lists its members and owned entities. If owned by an individual, Cortex displays the user's email. For information on assigning owners, refer to

Viewing entities without owners

There are a few ways to find entities in your catalog that don't have owners yet:

• Use the Ownership tool to see unowned entities and Cortex's automated recommendations for owners

• View the Executive Report, which lists unowned entities

• Run an Ownership Verification Scorecard, which adds tasks to your homepage for any entities still missing owners