> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/api/graphql/data-access/enumerations/owner-source.md).

# OwnerSource

How an owner role assignment was provisioned. Filtering on any of the Derived values is equivalent to filtering on all of them: they only distinguish which system for reporting, not for filtering.

```graphql
enum OwnerSource {
  DerivedFromCollibra
  DerivedFromDataSource
  DerivedOther
  Manual
}
```

### Values

#### DerivedFromCollibra <a href="#derived-from-collibra" id="derived-from-collibra"></a>

Derived from Collibra's configuration. Read-only in Data Access.

#### DerivedFromDataSource <a href="#derived-from-data-source" id="derived-from-data-source"></a>

Derived from a data source's own metadata (an owners field or a collibra\_owner tag in the import). Read-only in Data Access.

#### DerivedOther <a href="#derived-other" id="derived-other"></a>

Derived from another source system's configuration. Read-only in Data Access.

#### Manual <a href="#manual" id="manual"></a>

Assigned through the Data Access management API or UI. Can be unassigned.

### Member Of

[`AccessControlOwnerFilterInput`](/api/graphql/data-access/input-types/access-control-owner-filter-input.md) input ● [`RoleOwnerAssignment`](/api/graphql/data-access/object-types/role-owner-assignment.md) object ● [`RoleOwnerFilterInput`](/api/graphql/data-access/input-types/role-owner-filter-input.md) input


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/api/graphql/data-access/enumerations/owner-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.