> For the complete documentation index, see [llms.txt](https://docs.integry.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.integry.ai/apps/authentication/access-control-and-testing.md).

# Access Control and Testing

## Controlling access

You control the access of each app in your workspace. They can be accessed by:

* All users
* [Beta users only](/users/testing-with-beta-users.md)
* No one

### Configure access for an App

1. Go to Apps.
2. Click an app to open configure screen.
3. Toggle to Access.
4. Set **The app can be accessed by** to the desired option.

## Testing

Beta users can test apps, functions or flows from within the Integry app, or from the embedded UI in your app.

### Testing from the Integry app

Go to Apps and click **View as a User**.

It opens the embeddable UI in a modal. This view is **live**, i.e., you are accessing it as a real user, and all changes you make will impact connected accounts of the selected user.

{% hint style="info" %}
By default, your user ID will be selected. If you want, you can select a different user to **impersonate** but please remember that this is **live** and changes cannot be reversed.
{% endhint %}

If the selected user is a Beta User, you should see additional apps that only Beta users can access. Feel free to test your new ideas. When you're ready to release them, go back and make the app accessible to *All users*.

### Testing in your app

The embedded UI in your app will automatically show additional apps that only Beta users can access. No further action is needed in Integry.

Feel free to test your new ideas. When you're ready to release them, go back to the Integry app and make the app accessible to *All users*.


---

# 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.integry.ai/apps/authentication/access-control-and-testing.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.