Authentication

Public and authenticated routes

The homepage and documentation do not require an application Workspace. Connect your context hands off to platform sign-in, then returns to task-specific Workspace creation. Workspace pages, source downloads and mutation requests require an authenticated identity.

The hosting audience can independently restrict the entire site. An owner-private preview still has a site-level access wall before its public application pages.

Intent continuity

The selected example, Ask/Run mode and connection kind are carried in the return path. On Connect your context, the task and current question or Run draft are held temporarily in the same browser session. They become the starting instruction in the new Workspace; sample records and results never transfer. The temporary draft is removed after creation.

Continue sign-in in the same browser tab to preserve a custom draft. The selected example remains the fallback if browser session storage is unavailable.

Integration boundary

Sign-in is provided by the hosting platform. PatternLab does not accept API keys or expose a public developer authentication flow. Owner-scoped storage queries control which Workspace records and source files an account can retrieve.