> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/app-builder/access.md).

# Access

The Access tab has three sections, each controlling a different type of access to your app and its workspace.

## Collaborators

Shows who can open and edit this app in the App builder. On enterprise accounts, team membership is managed at account level — you can see who has access but cannot add or remove collaborators here.

## Support Access

Controls whether the Riff support team can view your workspace.

**Default: disabled (private).** Your workspace is not accessible to Riff support unless you enable this.

When you need help from Riff support:

1. Click **Enable support access**
2. A shareable link to your workspace appears — share this with the support team
3. When the session is resolved, click **Revoke support access** to remove it

Support access is not permanent. Revoke it when you no longer need assistance.

## Workspace API

Controls whether external systems can call your development API endpoints.

**Default: private.** Your development API is not reachable from outside the workspace.

When you need an external service (a webhook, a third-party automation) to call your development endpoints:

1. Click **Enable public access**
2. The API base URL appears: `https://api.riff.new/_projects/{id}/dbtn/devx/app/routes`
3. Access expires automatically after **12 hours**
4. Click **Disable public access** to remove it before expiry if needed

This is a development-only feature. Production API access is managed through your deployed app URL.


---

# 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.riff.ai/reference/app-builder/access.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.