LogoLogo
Login to CortexBook a DemoCortex Academycortex.io
  • Cortex Docs
  • Cortex Quick Start
  • Ingesting data into Cortex
    • Managing Entities
      • Adding entities
        • Add services
        • Add domains
        • Add teams
        • Add custom entity types
        • Defining dependencies
      • Entity details page
      • Defining ownership
      • Defining relationship types
      • Grouping entities
      • Adding external documentation
      • Adding Deploy data
      • Adding custom data
      • Viewing discovered entities
      • Archiving entities
      • Relationship graph
      • Using On-call Assistant for incidents
      • Managing Terraform infra in Cortex
    • Managing Catalogs
    • Integrations
      • Internally hosted integrations
      • ArgoCD
      • AWS
      • Azure DevOps
      • Azure Resources
      • BambooHR
      • Bitbucket
      • BugSnag
      • Buildkite
      • Checkmarx
      • CircleCI
      • ClickUp
      • Codecov
      • Coralogix
      • Datadog
      • Dynatrace
      • Entra ID (Azure AD)
      • FireHydrant
      • GitHub
      • GitLab
      • Google
      • Grafana
      • incident.io
      • Instana
      • Jenkins
      • Jira
      • Kubernetes
      • LaunchDarkly
      • Lightstep
      • Mend
      • Microsoft Teams
      • New Relic
      • Okta
      • Opsgenie
      • PagerDuty
      • Prometheus
      • Rollbar
      • Rootly
      • Sentry
      • ServiceNow
      • Slack
      • Snyk
      • SonarQube
      • Splunk Observability Cloud (SignalFx)
      • Splunk On-Call (VictorOps)
      • Sumo Logic
      • Veracode
      • Wiz
      • Workday
      • xMatters
  • Scorecards
    • Initiatives and Action items
      • Creating issues based on Initiatives
    • Scorecard rule exemptions
    • Scorecard rule filters
    • Scorecard examples
    • Scorecards as code
  • Reports
    • Executive report
    • All Scorecards report
    • Bird's eye report
    • Progress report
    • Report card
  • Eng Intelligence
    • Custom Metrics
    • Jira Metrics
    • Metrics Explorer (Beta)
  • Cortex Query Language (CQL)
    • Using CQL reports
    • Using JQ in Cortex
  • Workflows
    • Creating a Workflow
      • Workflows as code
    • Blocks
    • Running a Workflow
    • Registering a Scaffolder template
      • Scaffolder advanced usage
    • Using a Workflow to sync in ArgoCD
    • Kicking off a Jenkins pipeline in a Workflow
  • Plugins
    • Creating a plugin
      • Creating a plugin proxy
    • Migrating Backstage plugins to Cortex
  • Engineering homepage
  • Workspace Settings
    • Using GitOps for Cortex
      • GitOps logs
    • Managing users
      • Roles and permissions
        • Custom roles
        • Team ownership entity editing
      • Configuring SSO
        • Microsoft Entra ID
        • Google
        • Other OIDC providers
        • Okta
          • Okta SCIM
      • Configuring identity mappings
      • Onboarding management
    • API keys, secrets, and tokens
      • Secrets
      • Personal tokens
    • Audit logs
    • Entity settings
      • Data verification
      • Auto archiving entities
    • IP allowlist
    • Notifications
      • Notification logs
    • Customizing your workspace
    • Using search in Cortex
  • Cortex API
    • REST API operations
      • API Keys
      • Audit Logs
      • Catalog Entities
      • Custom Data
        • Custom Data (Advanced)
      • Custom Events
      • Custom Metrics
      • Dependencies
      • Deploys
      • Discovery Audit
      • Docs
      • Eng Intel: User Labels
      • Entity Relationship Types (Beta)
      • Entity Relationships (Beta)
      • Entity Types
      • GitOps Logs
      • Groups
      • Initiatives
      • Integrations APIs
        • Azure Active Directory (Entra ID) API
        • Azure Resources API
        • AWS API
        • Azure DevOps API
        • CircleCI API
        • Coralogix API
        • Datadog API
        • GitHub API
        • GitLab API
        • incident.io API
        • LaunchDarkly API
        • New Relic API
        • PagerDuty API
        • Prometheus API
        • SonarQube API
      • IP Allowlist
      • Notification Logs
      • On call
      • Packages
      • Plugins
      • Queries
      • SCIM
      • Scorecards
      • Secrets
      • Team Hierarchies
      • Teams
      • Workflows
Powered by GitBook
On this page
  • Enable team ownership entity editing
  • Specify team editors
  • Edit a team-owned entity
  • FAQ

Was this helpful?

Export as PDF
  1. Workspace Settings
  2. Managing users
  3. Roles and permissions

Team ownership entity editing

Last updated 2 months ago

Was this helpful?

With the Team ownership entity editing setting, organizations can restrict the ability to edit entities in Cortex to the teams and members who own them without granting generic edit permissions to all users in a workspace. Entity ownership must be defined for the setting to work.

You can also enable edit access to all team members by default.

Entity ownership must be defined to enable team ownership entity editing.

Enable team ownership entity editing

To enable this feature:

  1. Go to the .

  2. Toggle on the setting for Team ownership entity editing.

    • By enabling this feature for the workspace, the will be automatically updated and will not include generic permissions for editing entities.

    • Note that the Edit catalogs will supersede the Team ownership entity editing feature, so any users assigned a custom role with that permission will be able to continue editing all entities, regardless of ownership. Remove the Configure catalogs permission from the custom role(s) to restrict the ability to edit entities.

  3. To enable edit access to all members of the team who owns an entity, you can also toggle on the setting Give edit access to all team members.

The Configure catalogs permission supersedes Team ownership entity editing.

Specify team editors

To do this:

  1. Go to the details page for the team you'd like to set editors for. In the upper right corner of the page, click Configure entity.

  2. Click the Members tab.

  3. Next to the user's name, click the pencil icon.

  4. In the configuration side panel, toggle on the Editor setting.

  5. Click Save.

Edit a team-owned entity

If a team member is designated as an editor, they can click the Entities tab on the team details page to see all entities that they have permission to edit.

If you have permission to edit an entity, you will see Configure entity in the upper right corner of the entity's details page.

If a user is not an editor of a team, they will not be able to see the Configure entity button for any entities owned by the team or the team itself.

FAQ

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.

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

You can also define specific users within a team who can edit owned entities. Note that you cannot specify users if you have enabled the setting Give access to all team members in the .

If a team member does not have an associated Cortex account, they cannot be marked as an editor; the toggle for such users will be grayed out.

When you navigate to the team page in Cortex and view the Team members tab, any members who were marked as editors will display with an Editor label. If a team member's has not yet been configured, they will not be listed as an Editor here.

This can happen if the team member's has not been configured.

Entities settings page
identity mapping
identity mapping
Entities > Teams settings page
permission
default user role
In the UI, there are toggles for "Team ownership entity editing" and "Give edit access to all team members"
Click the Entities tab on the team details page.