Start here
Sign in and set up your account
Cover first GitHub sign-in, account state, and where settings live.
userorg admin
capture: sign-in
Outcome
You are signed in to prpl, you know where your account settings live, and you can read your own role and organization access off the Account page.
Who can do it
- Anyone with a GitHub account can sign in. A brand-new sign-in creates a
wait-listaccount: you can browse and pre-configure, and a site administrator later upgrades you tocustomer. - Invited organization members sign in through the invitation link in their email — no GitHub account is required for that path.
Before you begin
- Signing in asks GitHub only for the
read:useranduser:emailidentity scopes — enough to identify you, with no access to your repositories. Granting repository access is a separate, later step (Connect GitHub authentication). - If you were invited by email, have the invitation link ready. It is single-use, expires 72 hours after it was created, and a repeat invitation replaces the old link.
Steps — sign in with GitHub
- Open prpl and select Sign in in the top bar (or go straight to
/login). - On the Sign in to prpl page, select Sign in with GitHub.
The /login page, calling out the "Sign in with GitHub" button. - Authorize the prpl application on GitHub. The consent screen lists only identity scopes (
read:user,user:email). - You are returned to prpl, signed in. If this is your first sign-in, your account was just created on the wait-list.
- Open your profile menu — your avatar at the top right — and select Settings to open the Account page.
The open profile menu in the top bar, calling out the "Settings" entry.
Steps — join through an organization invitation
- Open the invitation link from your organization administrator. It lands on the Join your organization page.
- Select Accept invitation. prpl creates (or opens) your account from the invitation and signs you in — a GitHub login is not required.
- You land on the Account page with an "Invitation accepted. Welcome to your organization." notice.
What lives on the Account page
The Account page (profile menu → Settings) is your home for configuration:
- The header shows Signed in as your identity, your email if known, and your role.
- GitHub repository access — connect, inspect, or revoke the credential prpl uses to clone your code (guide).
- BYOS defaults — default repository URL, default profile, max recon tasks, and scope notes pre-filled into new scans. Select Save defaults to store them.
- Your organization access (members) — which organizations you belong to and the repositories granted to you.
- Users (organization owners) — members, seats, invitations, and per-repo access for each namespace you own.
- Sign out — at the bottom of the page, and also in the profile menu.
Verify
- The top bar shows your avatar and GitHub login (or invitation email) instead of Sign in.
- The Account page header reads Signed in as your identity and shows a role of
wait-list,customer, orsite_admin. - Invited members: the Account page shows Your organization access with your organization's namespace listed as active.
Troubleshooting
- "this account is disabled" after GitHub authorization. Your prpl account was disabled by an administrator (or your organization owner suspended your membership). Contact your organization owner or prpl support to be re-enabled — signing in again will not help.
- "OAuth state mismatch" or the sign-in stalls. The sign-in handshake is valid for 10 minutes and relies on browser cookies. Start again from
/login; if it repeats, allow cookies for the prpl domain and avoid opening the GitHub page in a different browser profile. - "GitHub OAuth not configured". The deployment itself is missing its GitHub credentials — nothing is wrong with your account. Contact your site administrator.
- The invitation page says "This invitation link is incomplete." The secure part of the link (after
#) was stripped, usually by an email client or copy-paste. Ask your organization administrator to send a fresh invitation. - Accepting an invitation fails. Expired, revoked, or already-used links are refused, and acceptance is also refused when "the organization has no available seats". Ask your administrator to re-invite you (a repeat invitation issues a new link) or free a seat first.
Next step
Connect GitHub authentication — give prpl read access to the repository you want analyzed. See also GitHub authentication and permissions reference and Roles and permissions.
Last verified against commit c0bf54d on 2026-07-10 · capture scenario: sign-in