> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ownership sources reference

> Compare the integrations that can supply owners in Cortex: provider values, name formats, sync times, and identity mapping needs

Cortex can pull owners from your Git provider, identity provider, HR system, ITSM tool, on-call tool, or cloud tags. This page compares every ownership source in one place so you can choose a source of truth and write `x-cortex-owners` blocks correctly.

If you're new to ownership in Cortex, start with [How ownership works](/ingesting-data-into-cortex/entities-overview/entities/ownership). For help choosing a source, see [Ownership best practices](/ingesting-data-into-cortex/entities-overview/entities/ownership/ownership-best-practices).

## Sources that use `x-cortex-owners`

For these sources, reference the provider's team or group in the entity descriptor with `type: group`:

```yaml theme={null}
x-cortex-owners:
  - type: group
    name: <name in the format below>
    provider: <provider value below>
```

| Source | `provider` value | `name` format | Sync time (UTC) | Identity mapping |
| - | - | - | - | - |
| [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops#syncing-ownership-from-azure-devops) | `AZURE_DEVOPS` | Azure DevOps team name (case-sensitive) | Daily at 10 a.m. | Required to connect team members to Cortex users |
| [BambooHR](/ingesting-data-into-cortex/integrations/bamboohr#syncing-ownership-from-bamboohr) | `BAMBOO_HR` | Team value from BambooHR's **Employee ownership field** | Daily at 6 a.m. | Not needed. Cortex uses each member's email address from BambooHR. |
| [Bitbucket](/ingesting-data-into-cortex/integrations/bitbucket#syncing-ownership-from-bitbucket) | `BITBUCKET` | Bitbucket team name | Daily at 10 a.m. | Required to connect team members to Cortex users |
| [Entra ID](/ingesting-data-into-cortex/integrations/entraid#syncing-ownership-from-entra-id) | `ACTIVE_DIRECTORY` | Entra ID group name (case-sensitive) | Daily at 6 a.m. | Optional. Cortex uses identity mappings when they exist, and falls back to the member's email address from Entra ID. |
| [GitHub](/ingesting-data-into-cortex/integrations/github#syncing-ownership-from-github) | `GITHUB` | `<organization>/<team-name>` | Daily at 9 a.m. | Required to connect team members to Cortex users |
| [GitLab](/ingesting-data-into-cortex/integrations/gitlab#syncing-ownership-from-gitlab) | `GITLAB` | GitLab group name | Daily at 10 a.m. | Required to connect group members to Cortex users |
| [Google](/ingesting-data-into-cortex/integrations/google/connecting-entities-to-google-cloud-platform#syncing-ownership-from-google-groups) | `GOOGLE` | Full Google Group email address | Daily at 9 a.m. | Optional. Cortex uses identity mappings when they exist, and falls back to the member's email address from Google. |
| [Okta](/ingesting-data-into-cortex/integrations/okta#syncing-ownership-from-okta) | `OKTA` | Okta group name (case-sensitive) | Daily at 3 p.m. | Optional. Cortex uses identity mappings when they exist, and falls back to the member's email address from Okta. |
| [Opsgenie](/ingesting-data-into-cortex/integrations/opsgenie#syncing-ownership-from-opsgenie) | `OPSGENIE` | Opsgenie team name (case-sensitive) | Teams daily at 9 a.m., identities daily at 10 a.m. | Required to connect team members to Cortex users |
| [ServiceNow](/ingesting-data-into-cortex/integrations/servicenow#syncing-ownership-from-servicenow) | `SERVICE_NOW` | ServiceNow team name (case-sensitive) | Daily at 9 a.m. | Not needed |
| [Workday](/ingesting-data-into-cortex/integrations/workday/using-the-integration-for-workday#syncing-ownership-from-workday) | `CORTEX` | Cortex tag of the team imported from Workday | Daily at 9 a.m. | Not needed. Cortex uses each member's email address from Workday. |

<Info>
  Workday teams are imported as Cortex teams, so you reference them by their Cortex tag with `provider: CORTEX`.
</Info>

## Sources that use cloud tags

AWS and Azure Resources don't use `x-cortex-owners`. Instead, Cortex reads an ownership tag on each cloud resource and matches its value to a Cortex team's `x-cortex-tag`. By default, the tag key is `owner`, and you can customize it in each integration's settings. Because the tag points to a Cortex team, you don't need identity mappings for this step.

| Source | Tag value | Sync time (UTC) | How to enable |
| - | - | - | - |
| [AWS](/ingesting-data-into-cortex/integrations/aws/importing-entities-from-aws#syncing-ownership-from-aws) | The owning team's `x-cortex-tag` | Daily at 6 a.m. | Turn on ownership sync in the AWS integration settings |
| [Azure Resources](/ingesting-data-into-cortex/integrations/azureresources#syncing-ownership-from-azure-resources) | The owning team's `x-cortex-tag` | Daily at 6 a.m. | Turn on ownership sync in the Azure Resources settings |


## Related topics

- [How ownership works](/ingesting-data-into-cortex/entities-overview/entities/ownership.md)
- [BambooHR](/ingesting-data-into-cortex/integrations/bamboohr.md)
- [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops.md)