Documentation home / Access and workspaces / Sign in
Sign in¶
Sign in through Discord to reach your workspaces or continue an invitation.
At a glance¶
In Trapitan: /auth/login.
Who can open this page: Public login page; direct visits render the Discord sign-in screen, including for signed-in users.
What you see¶
Choose Continue with Discord. Trapitan sends you to Discord and uses its returned identity claims to find or create your Trapitan identity. There is no password, email-entry or Google sign-in control on this screen. A pending browser-extension connection adds a short sign-in hint.
Who fills in each field¶
The signed-in-member label identifies you as the person starting sign-in. Discord supplies the identity claims; you do not type those claims into Trapitan.
| Field or data | What it means | Who fills it in | Can it be changed here? | When it updates |
|---|---|---|---|---|
| Discord identity | Discord supplies provider identity claims; you initiate sign-in. Historical Google rows cannot authenticate. | signed-in-member |
Read-only | Discord OAuth callback |
Calculations¶
No derived values on this page.
Freshness and updates¶
Identity information updates after a successful Discord callback. Ordinary sign-in returns to Choose a workspace. An active pending invitation returns to its join page; a pending extension authorization continues to its consent journey instead.
Actions and permissions¶
Who can take action: The actor and permission for each action are listed below. Who can perform each action depends on the server's checks, independently of whether navigation or a button is visible.
| Action | Actor | Permission |
|---|---|---|
| Sign in with Discord | signed-in-member |
Public start; enabled Discord provider, validated OAuth state/callback |
In Trapitan, select Continue with Discord, finish Discord authentication and return to the platform. This documentation does not start a sign-in session.
States and edge cases¶
A direct visit to the login route renders the sign-in screen even when you already have a session; the platform home redirects signed-in users to the workspace selector. An unsupported provider, unavailable provider configuration, failed OAuth callback or invalid state produces a sign-in error. Retry the Discord journey after resolving the failure. Historical Google identity rows can remain readable, but Google cannot authenticate. Completing sign-in alone does not grant workspace access.
Related pages¶
Source references¶
Source reviewed: 2026-10-05
Source references
Stable page ID: access.sign-in.
src/trapitan/api/routes/auth.pysrc/trapitan/web/templates/login.html