> 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/adding-entities/teams/team-entity-editing.md).

# Team ownership entity editing

Organizations can restrict entity editing to the teams and members who own each entity, avoiding the need to grant edit permissions across the entire workspace. Ownership must be defined on an entity for this to apply.

You can also grant all team members edit access by default.

This article walks you through how to enable the team ownership entity editing feature. For information on adding a team to Cortex, see [Adding teams](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams.md). See [Viewing teams](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams/viewing-teams.md) for information about viewing teams. Refer to [Team roles](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams/team-roles.md) for information on how to add roles and assign them to team members.

## Step 1: Enabling team ownership entity editing

Users with the `Configure Settings` permission can enable the team ownership entity editing setting.

Team ownership entity editing must be enabled before you can assign entity editing access.

{% hint style="warning" %}
The `Configure Catalogs` permission supersedes **Team ownership entity editing**.
{% endhint %}

1. From the main sidebar, click your avatar in the bottom-left corner.
2. Click **Settings**.
3. From the **Settings** menu, locate the **Workspace** section, then expand **Entities**.
4. Select **Teams**.
5. In the **Team settings** section, toggle on **Team ownership entity editing**. Enabling this feature ensures that the [default user role](/configure/settings/managing-users/permissioning.md#default-roles) is automatically updated and will not include generic permissions for editing entities.
   * Note that the `Configure Catalogs` [permission](/configure/settings/managing-users/permissioning.md) supersedes the **Team ownership entity editing** feature, so any users assigned a custom role with that permission can continue editing all entities, regardless of ownership. Remove the `Configure Catalogs` permission from the custom role(s) to restrict the ability to edit entities.
6. Optionally, toggle on **Give edit access to all team members** to give editing access to all members of the team who own an entity.

## Step 2: Specifying team editors

Follow the steps below to define editing access to specific users within a team. Note that you cannot specify specific users if the **Give access to all team members** option is enabled. See [Adjusting team settings](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/teams/team-roles.md#adjusting-team-settings) for more information.

1. From the main sidebar, expand **Catalogs**, then select **Teams**.
2. Do one of the following:
   * Select the **All** tab to search and filter across all of your organization's entities.
   * Select the **Mine** tab to search and filter only the entities you own.
   * Note that Cortex saves your selection and restores it the next time you open this page.
3. Select a team.
4. In the upper-right corner, click **Configure entity**.
5. From the configuration sidebar, select **Members**.
6. Locate the user you want to make an editor, then click the **pencil icon** next to their name.
7. In the side panel, toggle on the **Editor** setting. Note that if the team member does not have an associated Cortex account, they **cannot** be made an editor.
8. Click **Update**.

On the team page in Cortex, the **Team members** tab displays an `Editor` label next to any members you've marked as editors. Members without a configured [identity mapping](/configure/settings/managing-users/identity-mapping.md) won't appear as editors.

<div align="left" data-with-frame="true"><figure><img src="/files/denM4ftYGzrCdpSCmpK6" alt="The &#x27;Editor&#x27; label next to a team member&#x27;s name on the team page."><figcaption></figcaption></figure></div>

## Troubleshooting and FAQ

See frequently asked questions below.

**Can team editors import entities?**

No, team editors can not import entities. To import entities, a user must have the `Configure Catalog` permission, which also gives users the permission to edit ALL entities, not just the ones they own.

**Can team editors delete entities they own?**

No, team editors can not delete any entities, even if they own them.

**Can users with the Viewer role edit entities if this feature is enabled?**

Yes, if they are a member of the owning team and either Give edit access to all team members is enabled or they have been individually marked as an editor. The team ownership editing feature overrides workspace-level role restrictions for editing team-owned entities.

**Why does a team member not have the** `Editor` **label after I enabled edit access to all team members?**

This can happen if the team member's [identity mapping](/configure/settings/managing-users/identity-mapping.md) has not been configured.