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

# App users and access

Every App decides for itself who may open it, even when several Apps sit in the same workspace. You set that on the App's page in the App Manager, under **Access Settings**, and you see everyone who uses the App under **App users**.

{% hint style="info" %}

#### Users vs. members

This page is about the users of your Apps. The people who build the Apps are members: see [Members](https://docs.heisenware.com/app-manager/app-manager/members.md).
{% endhint %}

## Access modes

**Access Mode** offers five choices. A change applies at once, to everyone who has the App open, so do not change it more often than your users can follow.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-c3ad5f02ba42aee2e44af6c20bb9c9d0b627f9b7%2Fmanager-access-mode.png?alt=media" alt="The Access Settings card of an App, with its Access Mode list"><figcaption></figcaption></figure>

### Anyone can use the app

The App is open. Whoever has the link or scans the QR code is in, with no sign-in. The Player still gives each device an identity of its own, a generated name it remembers, so your logic can tell one terminal from another.

### Users must provide a master password

One password, shared by everyone allowed in. You set it under **Master Password**, in the same card. The browser keeps the answer, so a user types it again only on another device, in a private window, or after clearing the browser's data.

### Users have to sign-up

Every user has an account of their own, with an email and a password or their Google account. Heisenware keeps the accounts; you do not have to create them. The browser keeps the sign-in until the user logs out or clears its data. To offer a way out, drop the Logout [App action](https://docs.heisenware.com/app-builder/app-builder/pages.md#app-actions) onto a button, or onto an executor's output.

### Users have to sign-up and provide a master password

Both of the above: a personal account and the shared password.

### Only previously invited users can login

Only the addresses you invite can get in. The App's page then shows an invite field beside **App users**.

* **Programmatically**: the [`users` class](https://docs.heisenware.com/reference/functions/utilities/users.md) makes an access link from a flow, so another App can hand one out.
* **Ask**: only in this mode can an App be opened to [Ask](https://docs.heisenware.com/app-manager/app-manager/ask.md), where its users question the workspace's data with an AI. Switching to another mode ends Ask for the App; the Manager asks before it does.

## Inviting users

Type the address and click **Invite**. What happens depends on what the address already has:

* **New to the platform**: an invitation email with a link that sets a password.
* **Known, but never set up a way in**: a fresh invitation email. The link sent before stops working, except the very first invitation's, which keeps working until one of the two sets a password.
* **Known, with a password of their own**: no password link. They get an email saying this App is now open to them.
* **Already a user of this App**: nothing is sent, and the Manager offers to send them a password reset instead. Use it for someone who cannot get in.

A row with **Invitation pending** has never been taken up. Its icon sends the invitation again.

## App users

The table shows everyone the App holds, 25 at a time:

| Column                  | What it shows                                                                     |
| ----------------------- | --------------------------------------------------------------------------------- |
| **Email/Username**      | The address of a user with an account, or the name a device remembers for itself. |
| **Name**                | The first and last name, where the user gave one.                                 |
| **Verified**            | Whether the address has been confirmed.                                           |
| **Last Login**          | When they were last in, or **Invitation pending**.                                |
| **Browser**, **Device** | What they came with.                                                              |

In an open App or one behind the master password, the rows are devices rather than people: one row per device that ever opened the App, by the name it remembers.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-b891487d1df9b47083a4e395111cb01b341df088%2Fmanager-app-users.png?alt=media" alt="The user list of an App anyone can open: one row per device, each with the name it remembers, its browser and its device"><figcaption></figcaption></figure>

In the sign-up modes and the invite-only mode they are people: the **Email/Username** column holds the address, **Name** the name the user gave, and a user who signs in from several devices with the same address stays one row.

The trash icon removes a user, person or device alike: their record goes, their session ends, and their [Ask](https://docs.heisenware.com/app-manager/app-manager/ask.md) conversation goes with them.

{% hint style="info" %}

#### Managing users from a flow

The [`users` class](https://docs.heisenware.com/reference/functions/utilities/users.md) lists an App's users from the Flowboard and makes an access link for one. Inviting and removing happen here, on this screen.
{% endhint %}

## Using who is there

Your logic reads the user of the scope it runs in from the `$USER` [variable](https://docs.heisenware.com/concepts/variables-and-endpoints.md): the address of a signed-in user, the device's name in the open modes, and empty where no person is involved. Use it to greet by name, to filter a query so each user sees only their own rows, or to record who did something.

If a table keeps each row's owner in an `email` field, a `getTableData` executor filters for the signed-in user's own rows:

```yaml
# name
orders
# options
filter: [email, =, $USER]
```

On a kiosk the same mechanism names the terminal: the device's `$USER` becomes the machine it stands at, and every query takes that as an input.


---

# 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.heisenware.com/app-manager/app-manager/users-and-access.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.
