> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/introduction/quick-starts-by-role/cakewalk-for-app-owners.md).

# Human Access for App Owners

The App Owner quick start: approve requests, manage permissions and run reviews for the apps you own.

### ❓**Why Use Cakewalk?**

As an App Owner, you are responsible for **governing access to the apps you own**. Cakewalk makes this easier by:

* Giving you visibility into who has access and why.
* Routing access requests directly to you.
* Keeping full audit logs of every decision.
* Letting you take action directly from Slack.

***

### 🧑‍💻**Everyday Workflows**

#### **Reviewing Apps & Accesses**

* Access full app metadata (security, compliance, company info).
* View current users, permission levels and last access times.

💡 *Why this matters:* Quickly spot unused or risky access.

***

#### **Approvals**

* Receive tasks to review requests for app you own via Slack or in Cakewalk.
* Make approval decisions fast, with all the context you need built in.

💡 *Why this matters:* Employees get faster access, you maintain oversight.

***

#### **Actioning**

* Grant/remove access, change permissions or archive apps.
* Tasks are assigned automatically by Cakewalk.
* For supported apps, access is auto provisioned by Agent Cake reducing operational overhead for app owners.

💡 *Why this matters:* You stay in control of your apps without chasing tickets.

***

#### **Access Reviews**

* Receive review tasks when an access review is scheduled for one of your apps.
* See a list of users, their permissions and last activity.
* Decide whether to **approve**, **revoke** or **change** permissions.
* Complete reviews directly in Cakewalk.

💡 *Why this matters:* Access Reviews are critical for compliance (SOX, ISO, SOC 2) and for reducing risk from unused or over-privileged access. As an App Owner, your input ensures your apps stay secure and compliant without IT chasing you for sign-off.


---

# 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://www.cakewalk.security/docs/human-access/introduction/quick-starts-by-role/cakewalk-for-app-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.