SeyAuthentication
Sey has two separate auth surfaces: the dashboard your team uses, and the public portal and widget your customers use. They are independent.
Dashboard sign-in
Workspace members sign in to the dashboard at app.sey.so. Two methods are supported:
- Email and password. After signup, Sey sends a one-time verification code to confirm the email before the account is active.
- Google. Social sign-in with a Google account.
Sign up, sign in, email verification, and accepting workspace invitations all flow through the dashboard auth screens.
Workspace identity
A workspace maps to an organization. Each member has a role - owner, admin, or member. See Team and roles. Active sessions track your currently selected workspace, which you can switch from the workspace menu.
Portal sign-in
Customers do not have dashboard accounts. Instead, the portal uses email one-time codes: a participant enters their email, receives a six-digit code, and signs in. Codes are rate-limited.
A participant's portal account can be linked to a workspace member if their email matches, so a teammate can also act as a participant on the portal side.
Widget identity
The widget does not require portal sign-in. It tracks an identity session for the current browser, which is anonymous until identify() is called. For verified widget identity, use a signed identity token. See Widget SDK reference and Identity tokens.
Bridging the widget and portal
A verified widget identity can be single-sign-on'd into a portal session via createPortalSession() or navigateToPortal(). The first portal sign-in claims any anonymous widget activity into the verified participant.