> 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/members.md).

# Members

Members are the people who build and manage Apps in a Heisenware account. The **Members** screen lists them in groups: first the owners of the account, then each [workspace](https://docs.heisenware.com/app-manager/app-manager/workspaces.md) you reach with the people who hold it.

{% hint style="info" %}

#### Members vs. users

Members build the Apps. Users are the people who use them in the App Player. See [App users and access](https://docs.heisenware.com/app-manager/app-manager/users-and-access.md) for those.
{% endhint %}

## What a member holds

Every member owns the account, or holds one or more workspaces:

| Access                   | What it gives                                                                           |
| ------------------------ | --------------------------------------------------------------------------------------- |
| **Owner of the account** | Every workspace, the plan and billing, all members, and adding and deleting workspaces. |
| **Owner of a workspace** | Builds in that workspace and chooses who else does.                                     |
| **Editor**               | Builds in that workspace, its integrations included.                                    |

**Plan & Billing** is shown to owners of the account only. Everyone sees the owners of the account, since those reach their workspace too. A workspace nobody has been invited to yet says so: only the account's owners reach it.

Each row shows the member's name, their email, their **Access** in that workspace, and whether their address is **Verified**.

## Invite someone

Enter an email address in the box at the top right, choose what the invitation grants, and click **Invite**. An owner of the account can grant any of its workspaces or the account itself; an owner of a workspace only their own workspaces.

What the invited address already has decides what happens:

* **New to the platform**: an invitation email with a link that sets a password. Taking it up asks for a first and last name and a password, or for a Google account under the invited address.
* **A user of one of your Apps, but no member**: the same invitation email. Being a user of an App gives nobody the App Manager.
* **A member already**: the access is added to what they hold, at once and without an email. This is how someone reaches a second workspace: it is there at their next look.
* **A member who never took up their invitation**: a fresh invitation email. The row shows the resend icon until they do.

## Change what someone holds

* **Access**: choose **Owner** or **Editor** on a member's row in a workspace.
* **Send invitation again**: the circular arrow on the row, for a member who never took up their invitation. Any link sent before stops working.
* **Remove from a workspace**: the trash icon on a member's row in a workspace. They lose that workspace at once, with the connections they have open, and keep whatever else they hold. A member left holding nothing is no member any more; if they are still a user of an App, they stay that, without the App Manager.
* **Delete member**: the trash icon on a member's row under the owners of the account. This removes them from the platform and from every App where their address was the username. It cannot be undone; you can always invite them again.

Every change bites at once, however long the member's sign-in would otherwise last.

An account keeps at least one owner. There is no way to take account ownership away again in the Manager: delete the member and invite them back with the access they should have.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-e5e7dc66df515ed5059792a4631de536960853bf%2Fmanager-members.png?alt=media" alt="The Members screen: the owners of the account, the members of a workspace, and the box that invites one"><figcaption></figcaption></figure>


---

# 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/members.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.
