Defining ownership
Last updated
Was this helpful?
Last updated
Was this helpful?
Ownership is a core use case of Cortex, as many organizations seek to establish clear ownership of services, data, and other entities. Entities should be owned within Cortex to ensure appropriate action can be driven using Scorecards and Initiatives.
Ownership can be defined by accepting Cortex's automated recommendations for ownership, pulled in from third-party integrations, or defined manually in the Cortex UI. Ownership can also be inherited from an entity's .
By mapping every service and resource to its responsible , issues get resolved faster, accountability is clear, and decisions happen quickly.
Ownership drives which users will receive from Cortex, including alerts for on-call changes, when is needed on an assigned entity, when an entity is re-evaluated and its Scorecard changes, and more.
When viewing an entity, the owners appear in the metadata bar at the top of the page:
Click into the team name to view the team's entity page, including a list of members and a list of entities owned by that team.
You can define owners based on:
A team
We recommend setting up teams as owners. If you link a group
in your YAML file from a different platform (such as Okta), the members of the team will be automatically updated in Cortex if anyone leaves your organization and is removed from your integrated identity provider.
A user email address
Owners can be defined:
By accepting Cortex's automated recommendations for owners, based on repository activity
Automatically if Cortex detects that an entity is owned by a team that does not yet exist in Cortex
If an entity's YAML references a team, but that team doesn't have a corresponding entry within Cortex, Cortex will automatically create a team. The team will include a label that says Automatically created by Cortex.
Directly in the Cortex UI
Cortex analyzes a repository and automatically recommends a team owner for entities that do not have an owner.
To review and assign ownership across all unowned entities:
In the main nav of Cortex, click Tools > Ownership.
A list of recommendations for ownership is displayed.
Review and accept the recommended owners.
To apply all recommended owners: Ensure the checkboxes for all entities are selected, then at the top of the list, click Accept recommendations.
To apply selected owners: On the left side of the list, check the box next to the entities whose recommended owners you want to accept. When you are finished selecting, click Accept recommendations at the top of the list.
You can pull in all resources from AWS, and Cortex syncs those owners automatically based on their tags in AWS, allowing you to easily keep the resource owners up to date.
To see a list of entities you own directly and entities that are owned by your team's child teams:
The list defaults to displaying the "Mine" tab, showing only the entities you own.
At the top of the list, click Display.
Enable the toggle next to Include child teams.
Click Done.
You can filter the entity list by owner:
In the upper right corner, click Filter.
Teams can exist within hierarchies. You can view a list of all entities that are owned by the parent team and all children teams in the hierarchy:
Navigate to the parent team's page in Cortex.
Click the Entities tab.
Click Display, then enable the toggle next to Inherited Children.
Click Done.
The list will now display all entities owned by the parent and its children teams. Note that this setting does not persist when you navigate away from the page.
You can who will be defined as owners for your entities.
By pulling information from third-party integrations in the
Ownership can also be inherited via .
The ability to must be enabled.
If an entity does not have an owner and Cortex has recommendations for who the owner should be, it will be flagged in the ownership tool under Tools > Ownership, in the "Owners" section of an entity details page overview, in the "Owners" sidebar link on an entity details page, and it will appear during the import process when .
Users can edit ownership on this page only if they have edit access for all entities. If a user only has edit access for some entities, they can accept ownership recommendations from an entity's details page,
Users can accept ownership recommendations for an entity if they have edit access for that specific entity, and if UI editing is enabled for that entity type under .
On an next to the "Owners" field, click Recommendations.
Review the suggested owners. To accept a recommendation, check the box next to the recommended owner then click Add owners.
In Cortex, navigate to .
Cortex can automatically discover ownership for your AWS resources using their owner
tag. To enable this, make sure that your AWS resources have an owner tag matching the x-cortex-tag
of the corresponding Cortex team and enable the Sync ownership from AWS toggle in .
To see a list of entities you own directly, navigate to then click the Mine tab:
Navigate to .
Under , click the All tab.
In the left side of the filter modal, click Teams. Select teams from the dropdown, then click Apply at the bottom.
Read more about hierarchies in .
Under , there are several settings relating to teams. Read more about these in the .