> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/ox-code-inventory/applications/managing-applications/application-owners.md).

# Application Owners

Application owners identify the people responsible for an application. Assigning owners helps establish accountability and enables ownership-based filtering, reporting, workflows, and application scopes.

An application can have multiple owners with different responsibilities.

### Owner roles

You can assign the following owner roles:

<table><thead><tr><th width="149.8333740234375">Role</th><th>Description</th></tr></thead><tbody><tr><td>Dev</td><td>Responsible for developing and maintaining the application's code.</td></tr><tr><td>Business</td><td>Responsible for the application from a business perspective.</td></tr><tr><td>Security</td><td>Responsible for the application's security posture and remediation activities.</td></tr><tr><td>Watcher</td><td>Receives notifications and can monitor the application without being responsible for remediation.</td></tr></tbody></table>

### Assign application owners

You can assign owners to one or more applications simultaneously.

**To assign application owners:**

1. Go to **Applications**.
2. Select one or more applications.
3. Select **Assign Owner**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-64b542fbd3c54ec30f88149595909bfcc7bcf4a6%2FAssign_App_Owners.png?alt=media" alt="" width="510"><figcaption></figcaption></figure>

4. Select the required owner role.
5. Do one of the following:
   * In the **Select to change Dev owners** section, elect one or more existing users, Or
   * In the **Add New Owner** section, enter the owner's name and email address, and then select **Add**.
6. Select **Save**.

### Best practices

* Assign at least one owner to every application.
* Assign owners according to their responsibilities.
* Keep ownership information up to date when responsibilities change.
* Use owners consistently when defining application scopes.

### Related information

* [Managing applications](/ox-code/ox-code-inventory/applications/managing-applications.md)
* [Scopes](broken://pages/2OEAUmhkBPZnqcSIPLGU)
* [Applications](broken://pages/g9htknA2LyUsOVD8onnT)


---

# 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://docs.ox.security/ox-code/ox-code-inventory/applications/managing-applications/application-owners.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.