> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/platform/user-access.md).

# User Access

Access to the admin console follows two paths. The first path is used during onboarding: a person creates an account, then The Wallet Crew grants access to the tenant. The second path is used after onboarding: a tenant administrator adds and manages other back-office users directly from the admin console.

{% hint style="info" %}
If sign-in works but no tenant appears, access has not been granted yet.
{% endhint %}

### Create an admin account

For first access to a tenant, start by creating a personal account in the admin portal. This creates the login account, but it does not grant tenant access on its own.

{% stepper %}
{% step %}

#### Open the admin portal

Open <https://admin.thewalletcrew.io/>. This is where you sign up and sign in to the administration console.
{% endstep %}

{% step %}

#### Sign up

Start the sign-up flow and choose the preferred method. Once the account is created, The Wallet Crew can grant the first access to the tenant.

<figure><img src="/files/W5PneynD9sgGPqcOG2co" alt="Admin portal sign-up screen with Google, Microsoft, and email sign-in options"><figcaption><p>Create the first back-office account from the admin portal sign-up page.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Use your work email. It makes access assignment faster.
{% endhint %}

### Get access to a tenant

For the first administrator of a tenant, access is usually granted by The Wallet Crew during onboarding. Once a tenant already has an administrator, that administrator can grant access to other users without going through support.

<details>

<summary>Real-world examples</summary>

* A brand contact creates an account during onboarding. The Wallet Crew grants the first access to the tenant.
* A tenant administrator later adds colleagues from the **Users** tab.

</details>

#### Manage back-office users

Once a tenant administrator has access, back-office users can be managed from **Settings → Access control → Users**. The **Roles** tab next to it is used to review the available roles.

The **Users** tab displays a table with **Email**, **Name**, **Role**, **Status**, and **Last login**. Active users appear with an **Active** badge in the **Status** column. The **+ Add new** action opens the user form, and each row menu provides **Edit** and **Delete** actions.

<figure><img src="/files/OpJmUAdl1rKo0P7LVgWU" alt="Users list in Access control showing email, name, role, status, and last login"><figcaption><p>The Users page centralizes user creation, role assignment, and access review.</p></figcaption></figure>

{% stepper %}
{% step %}

#### Open Users

Open **Settings → Access control → Users**.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/access/users-and-roles/users" class="button secondary" data-icon="chevrons-right">Open Users in the admin console</a></p>
{% endstep %}

{% step %}

#### Add a new user

Click **+ Add new**.
{% endstep %}

{% step %}

#### Fill the user details

Fill **Email**, **Name**, and **Role**, then click **Save** in the top-right corner.

The form also shows a read-only **User ID** generated by the system.
{% endstep %}
{% endstepper %}

To edit a user, open the **...** menu on the user row, click **Edit**, update the fields, then click **Save**.

To delete a user, open the **...** menu and click **Delete**. This removes access to the tenant, but does not erase the person’s login account.

### FAQ

<details>

<summary>I can sign in, but I see no tenant. What’s happening?</summary>

The account exists, but it has not been granted access to any tenant yet. For first access, contact The Wallet Crew during onboarding. If the tenant already has an administrator, that administrator can grant access from [Manage back-office users](#manage-back-office-users).

</details>

<details>

<summary>Can a tenant administrator add another user?</summary>

Yes. A tenant administrator can open **Settings → Access control → Users**, click **+ Add new**, fill the user details, and save.

</details>

<details>

<summary>I can access a tenant, but I can’t see Settings. Why?</summary>

The account has access to the tenant, but not with administrator rights. Ask a tenant administrator to review the assigned role.

</details>

<details>

<summary>Does signing up automatically create a tenant?</summary>

No. Signing up only creates the account. Access to a tenant is granted separately.

</details>

<details>

<summary>Can I access multiple tenants with the same account?</summary>

Yes. The same account can be granted access to multiple tenants. The assigned role can differ from one tenant to another.

</details>

<details>

<summary>Should I use my work email or a personal email?</summary>

Use a work email whenever possible. It makes onboarding and access management easier.

</details>

<details>

<summary>I picked the wrong sign-in method (Google vs Microsoft vs email). Can I change it later?</summary>

Avoid signing up again with a different method, because it can create a second identity. If you must switch methods, contact The Wallet Crew support so access can be reassigned safely.

</details>


---

# 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.thewalletcrew.io/configure/advanced-configuration/platform/user-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.
