# Managing User Metadata

You may have read the [Automate data access control decisions use case](/2024.2/secure-your-data/getting-started-with-secure/automate-data-access-control-decisions/managing-user-metadata.md) already. If so you are aware of the [two paths](/2024.2/secure-your-data/getting-started-with-secure/automate-data-access-control-decisions/the-two-paths.md) you must choose between: orchestrated-RBAC vs ABAC. To manage user metadata with this particular use case, you should use ABAC.

This is because you must know the contents and sensitivity of **every** column in your data ecosystem to follow this use case. With orchestrated RBAC, you tag your columns with access logic baked in. ABAC means you tag your columns with facts: what is in the column. It is feasible to do the latter, extremely hard to do the former (unless you use [tag lineage](/2024.2/secure-your-data/getting-started-with-secure/compliantly-open-more-sensitive-data-for-ml-and-analytics/open-managing-data-metadata.md#tag-lineage) described in the next topic), especially in a data ecosystem with constant change. This means that your users will need to have facts about them that drive policy decisions (ABAC) rather than single variables that drive access (as in orchestrated-RBAC).

Understanding that, please read the ABAC section in the automate data access control decisions use case's [Managing user metadata](/2024.2/secure-your-data/getting-started-with-secure/automate-data-access-control-decisions/managing-user-metadata.md#abac-user-attributes-and-groups) guide.


---

# Agent Instructions: 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:

```
GET https://documentation.immuta.com/2024.2/secure-your-data/getting-started-with-secure/compliantly-open-more-sensitive-data-for-ml-and-analytics/open-managing-user-metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.