> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/govern/detect-your-data/audit/reference-guides/unknown-user.md).

# Unknown Users in Audit Logs

Identify unknown users in query audit logs for Databricks Unity Catalog

[Unity Catalog query audit](/saas/govern/detect-your-data/audit/reference-guides/query-audit-logs/databricks-uc.md) brings in audit information for all tables and data sources, so some audit logs are created from activity by users not registered in Immuta. These audit records will appear in Immuta, providing valuable information of activity, with the username Unknown. This can be seen on the audit page or in user and data activity dashboards.

## Identify users

While the Immuta user is unknown, the user's Databricks Unity Catalog username can be found within the audit log. To view the user's data platform username:

1. Navigate to the event page.
2. Select **View JSON**.
3. The username can be found in the `auditPayload.technologyContext.account.`**`username`** field.

## Register users

To improve your future audit records, ensure these users are properly registered and can be named in the logs:

1. If you have not registered any users, [pull in users from your IAM](/saas/configuration/people/section-contents/reference-guides/index.md).
2. If you have registered users but this user was missed, [manually create the Immuta user](/saas/configuration/people/users-index/how-to-guides/managing-personas-and-permissions.md).
3. If this user is in Immuta but not appearing in the audit record, [map the user's Databricks username into Immuta](/saas/configuration/people/users-index/how-to-guides/external-user-mapping.md).


---

# 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://documentation.immuta.com/saas/govern/detect-your-data/audit/reference-guides/unknown-user.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.