> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/ownership/viewing-and-managing-ownership.md). # Viewing and managing ownership Once your catalog has owners assigned, Cortex gives you several ways to slice that data: by individual, by team, or across a team hierarchy. This page covers how to find the entities you own, filter by team, and remove ownership that's no longer accurate. ## Viewing entities you own 1. From the main sidebar, expand **Catalog**, the select **All entities**. 2. Select the **Mine** tab. A list of entities you own is displayed.
The Entities page showing all entities owned by the user.
### Viewing child team ownership 1. From the main sidebar, expand **Catalog**, the select **All entities**. 2. Select the **Mine** tab. 3. At the top of the list, click **Display**. 4. Toggle on **Include child teams**.
The 'Include child teams' option, toggle on.
5. Click **Done**. ## Viewing a team's owned entities 1. From the main sidebar, expand **Catalog**, the select **All entities**. 2. Select the **All** tab. 3. At the top of the list, click **Filter**. 4. In the **Filter** window, click **Teams**.
The 'Teams' option in the Filter window.
5. Select a team or teams from the drop-down menu. 6. Click **Apply**. ### Viewing entities owned by all teams within a hierarchy Teams can exist [within hierarchies](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams/viewing-teams.md#understanding-hierarchies). To view a list of entities owned by the parent team and all children teams in the hierarchy: 1. Navigate to the parent team's page. 2. Select the **Entities** tab.
The 'Entities' tab on a team's page.
3. At the top of the list, click **Display**. 4. Toggle on **Inherited Children**.
The 'Inherited children' option toggled on.
5. Click **Done**. The list displays all entities owned by the parent and its children teams. Note that this setting does not persist when you navigate away from the page. ## Removing ownership To remove an owner, use the same method you used to add them. ### Removing ownership via YAML * Update the `x-cortex-owners` block in your YAML to reference only the correct teams or individuals. Ensure that all referenced teams actually exist in Cortex. * If using [GitOps](/configure/gitops.md), make sure the YAML is updated and merged to your main branch, then allow Cortex to re-sync. This updates the ownership in the UI to match the YAML. ### Removing ownership via API Use the [Create or update entity API](/api/readme/catalog-entities.md#post-api-v1-open-api) to completely replace the entity YAML, or the [Create or patch entity API](/api/readme/catalog-entities.md#patch-api-v1-open-api) to remove one or more owner and not change the rest of the entity YAML. ### Removing inherited ownership * Check if the entity is a child of a domain or group with [ownership inheritance](/ingesting-data-into-cortex/entities-overview/entities/ownership/ownership-inheritance.md) enabled. If so, the parent’s owners may be appended to the entity. * To remove inherited owners, edit the domain or parent’s owner inheritance setting (e.g. change from `Append` to `None`). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/ownership/viewing-and-managing-ownership.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.