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

# Signing in & your account

## Your first sign-in

Allshore has no separate password to manage. Your firm's administrator sends you an **email invitation**; accepting it creates your account in your firm's directory and assigns your role. From then on, sign in from the Allshore landing page — you'll authenticate through your organization's sign-in (the same identity system handles password, and any MFA or SSO policy your firm configures).

After signing in you land on your workspace's home screen — for partner staff, the **Dashboard**.

## Roles

Partner staff hold one of two roles, assigned at invitation time:

| Role              | What it adds                                                                                                                                                                                             |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **partner user**  | The full day-to-day workspace: clients, pipeline, roster, hiring, time, invoicing prep, reports.                                                                                                         |
| **partner admin** | Everything above, plus money-final and sensitive actions: approving/executing payroll, voiding invoices, revealing payout details, verifying credentials, approving agent actions, and most of Settings. |

Admin-only actions are enforced by the platform itself, not by what the screen shows. Depending on the screen, an admin-only control may be shown disabled (archiving a candidate document, example data), may not be shown at all (credential verification), or may accept input and refuse it on submission (some Settings forms). In every case the meaning is the same: that action needs a partner admin.

## Where to see who you are

The bottom of the navigation rail (the **rail foot**) always shows three things: your name, your **organization**, and your role (displayed as "partner admin" / "partner user"). The **Sign out** button lives there too — on a phone, open the menu drawer to reach it.

## "Your account has no role yet"

If you sign in and see the **No workspace** card ("Your account has no role yet"), your session isn't carrying a partner, consultant, or client role. This is often a stale session from before your role was granted:

1. **Sign out and back in** — that refreshes the session and usually fixes it.
2. If it persists, ask your firm's administrator to confirm your invitation was accepted and your role is granted in the organization directory.


---

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