Skip to main content
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.
1

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

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

Complete workspace setup

You will be directed to the onboarding checklist at /admin/onboarding. See Complete your first workspace setup for the full walkthrough.
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.

​
Sign in to an existing account

1

Open the sign-in page

Go to /auth/login.
2

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

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

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.

​
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.
1

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

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

Confirm access

After accepting, you will land in your workspace. Admins reach the admin area; employees reach the employee app.
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.

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

​
Common sign-in issues

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