> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yrka.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in, sign up, and manage account access

> Create an owner account, sign in with email or an external provider, accept an invite, and resolve common access problems before they slow you down.

Getting into Yrka depends on how your organization is set up. Owners create the account and workspace at sign-up. Admins and employees join through invitations sent by an owner or admin. Some organizations also allow domain-matched sign-in through Google or Microsoft, but those still require admin approval or an accepted invitation before access is granted.

## Create a new account

If you are setting up a new Yrka workspace for your organization, start here. Creating an account at `/auth/sign-up` provisions a new organization and assigns you the owner role.

<Steps>
  <Step title="Open the sign-up page">
    Go to `/auth/sign-up`. Public self-serve sign-up is available when your launch path enables it. If your organization is doing a managed rollout, contact your implementation owner or support instead of signing up directly.
  </Step>

  <Step title="Enter your details and create a password">
    Use your work email and a strong password that meets the Yrka password standard. After submitting, you will land on a sign-up success page with prompts to continue setup or start checkout.
  </Step>

  <Step title="Complete workspace setup">
    You will be directed to the onboarding checklist at `/admin/onboarding`. See [Complete your first workspace setup](/setup/first-workspace) for the full walkthrough.
  </Step>
</Steps>

<Note>
  Sign-up creates one organization. If you need to join an existing workspace instead of creating a new one, ask your admin for an invitation link.
</Note>

## Sign in to an existing account

<Steps>
  <Step title="Open the sign-in page">
    Go to `/auth/login`.
  </Step>

  <Step title="Choose your sign-in method">
    Sign in with your email and password, or use a configured external provider (Google or Microsoft) if your organization has enabled one. If you are not sure which method your organization uses, try email and password first.
  </Step>

  <Step title="Complete any provider prompts">
    If you use Google or Microsoft sign-in, the app may ask for your work email first to check provider availability without revealing organization details. Enter your work email when prompted.
  </Step>

  <Step title="Reach your workspace">
    Admins land in the admin workspace when their membership and permissions are active. Employees land in the employee workspace when employee app access is enabled on their profile.
  </Step>
</Steps>

## Accept an employee or admin invitation

When an admin adds you to a workspace, you receive an invitation at your work email address. The invitation contains a unique link that confirms your identity before granting access.

<Steps>
  <Step title="Open the invitation link">
    Click the link in your invitation email. It takes you to `/invite/[token]` where you can see the masked email address the invitation was sent to. Confirm it matches your work email.
  </Step>

  <Step title="Set your password or sign in">
    If you do not yet have a Yrka account, you can set your password directly on the invite page. If you already have an account, sign in with the exact email address on the invitation — using a different email will not activate access.
  </Step>

  <Step title="Confirm access">
    After accepting, you will land in your workspace. Admins reach the admin area; employees reach the employee app.
  </Step>
</Steps>

<Warning>
  Invitation acceptance requires the exact email address shown on the invite page. If you signed in with a different account, choose **Use another account** and sign in with the invited email before accepting again. Invitations that are expired, revoked, or already accepted cannot be reused — ask your admin for a new invitation.
</Warning>

## Pending access states

Sometimes sign-in succeeds but you land on `/auth/pending-access` rather than your workspace. This happens when the system recognizes your identity but your organization access has not yet been approved.

| State                            | What it means                                                                      | What to do                                                            |
| -------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Pending access**               | Your identity is known, but an admin has not approved your request yet.            | Wait for admin approval.                                              |
| **Denied**                       | An admin rejected the request.                                                     | Contact your organization to understand why.                          |
| **Expired**                      | The pending request timed out.                                                     | Sign in again with the same work email to submit a new request.       |
| **Provider unavailable**         | Google or Microsoft sign-in is not enabled or configured for your domain.          | Try email and password sign-in instead.                               |
| **Disabled employee app access** | Your account is valid, but your employee self-service access has not been enabled. | Ask a manager or admin to enable employee app access on your profile. |

<Info>
  Admins with access-management permissions can approve, deny, or re-invite users from the admin tools. If you are an admin handling pending access requests, check the access review section in **Admin Tools**.
</Info>

## Common sign-in issues

<AccordionGroup>
  <Accordion title="I used my personal email instead of my work email">
    Sign out and sign back in with your work email. If you accepted an invitation with the wrong email, ask your admin to revoke the old invitation and send a new one to your work email.
  </Accordion>

  <Accordion title="Google or Microsoft sign-in is not working">
    External sign-in providers must be configured for your organization and your email domain must be on the allowed list. Even if sign-in succeeds with a provider, organization membership still requires an accepted invitation or admin approval. Try email and password sign-in while your admin reviews the provider configuration.
  </Accordion>

  <Accordion title="I see an error page at /auth/error">
    Retry sign-in once in a fresh browser tab. If the error continues, note the visible error message, the page route, the timestamp, and your email domain, then share those details with your support contact. Do not share passwords, OAuth codes, or session tokens.
  </Accordion>

  <Accordion title="My browser session seems stale">
    Sign out completely, close any incognito or private tabs, and sign in again using a fresh browser profile. Stale sessions can cause unexpected redirects and error states.
  </Accordion>

  <Accordion title="I can sign in but I cannot access anything">
    Your account may be valid but your access may be limited by your account lifecycle state. If the account was suspended, canceled, or marked for deletion, use the billing or account owner support path rather than creating a new workspace.
  </Accordion>
</AccordionGroup>

<Tip>
  When contacting support about a sign-in issue, share the visible error text, the URL you landed on, the timestamp, and your email domain. Never include passwords, OAuth codes, provider tokens, or session cookies in a support message.
</Tip>