> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/getting-started/signing-in-and-your-account-1.md).

# Signing in & your account

Allshore has no passwords of its own. Your firm's organization directory is the source of truth for who you are, so signing in means accepting an invitation once and then signing in through your organization from then on.

## Getting your account

1. **An admin at your firm invites you.** The invitation arrives by email.
2. **You accept it.** Accepting creates your account and joins you to your firm's organization.
3. **Your admin gives you a role.** The role decides which workspace you land in — there is no "pick your workspace" step.
4. **You sign in.** You arrive at your **Dashboard**.

There is no separate Allshore password to set, rotate or forget. If your firm uses single sign-on, that is what you will be asked for.

## Roles, and what each one sees

Your role decides your whole workspace, not just which buttons are enabled:

| Role                             | Where you land                                                                 |
| -------------------------------- | ------------------------------------------------------------------------------ |
| **Partner admin**                | The Partner workspace, with every administrative action enabled                |
| **Partner user**                 | The Partner workspace, with admin-only actions visible but disabled            |
| **Consultant**                   | The Consultant workspace — your own time, expenses, credentials and onboarding |
| **Client admin / client viewer** | Your client's portal — approvals, invoices, contracts                          |

Two things follow from this that are worth knowing up front.

**Admin-only actions are disabled, not hidden.** If you are a partner user you will still see the controls a partner admin has. They are greyed out rather than removed, so you can see what exists and know who to ask. Throughout this guide, anything restricted is marked **(admin only)**.

**You cannot switch workspaces.** Signing in as a partner shows you the Partner workspace and nothing else. Reading a client's portal means signing in as that client — which is deliberate, and part of how the platform keeps clients' data separated.

## "Your account has no role yet"

If you sign in and see a card reading **Your account has no role yet**, your account exists but no role has been assigned to it. Nothing is broken and nothing is lost — the workspace simply cannot decide what to show you.

Ask an admin at your firm to assign your role. Once they have, sign in again and you will land in the right place.

## Checking who you are signed in as

The foot of the navigation rail, bottom left, always shows three things:

* your **name**,
* your **organization**,
* your **role**.

If something looks wrong — the wrong organization, a role you did not expect — that is the first place to look, and the fastest thing to quote when you ask for help.

## Signing out

Sign out from the rail foot. On a phone, open the navigation drawer with the menu button first — sign-out lives at the bottom of the drawer, in the same place as on a wide screen.


---

# 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.allshore.ai/getting-started/signing-in-and-your-account-1.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.