> For the complete documentation index, see [llms.txt](https://docs.opendatadiscovery.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opendatadiscovery.org/~/changes/pcY8r1Ougw5Sv8zDaz8G/configuration-and-deployment/enable-security/authorization/user-owner-association.md).

# User-owner association

User-owner association is an important part of using ODD Platform. If user doesn't have association with any [owner](/~/changes/pcY8r1Ougw5Sv8zDaz8G/configuration-and-deployment/enable-security/authorization/owners.md), it's impossible to him to manage data entities or have owner-based security role.

There are 2 ways of association process - for admins and for regular users. We will cover both of them in details below.

### Admin

Association process for admins is straightforward.

1. After logging in you will see modal dialog in the bottom of the main page
2. Select owner which you want to associate yourself with and press `Associate` button.

### User

Association process for regular users is a bit more complicated and involves a few more steps

1. After logging in you will see the same modal dialog as admins in the bottom of the main page
2. Select owner which you want to associate yourself with and press `Send request` button.
3. In `Management` section under `Associations` tab admin user will see your association request.
4. Admin should approve request for finishing association process or deny it if there are any issues with current request.

After all these steps user will have an associated owner which can be used across the platform.

{% hint style="info" %}
User-owner relation is one-to-one relation, which means, that one user can be associated only with one owner and vice versa.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.opendatadiscovery.org/~/changes/pcY8r1Ougw5Sv8zDaz8G/configuration-and-deployment/enable-security/authorization/user-owner-association.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.