Skip to content

add a welcome flow for new organizations - #61

Merged
hkonsti merged 4 commits into
mainfrom
hkonsti/onboarding-flow-design
Oct 8, 2026
Merged

hkonsti merged 4 commits into
mainfrom
hkonsti/onboarding-flow-design

Conversation

@hkonsti

@hkonsti hkonsti commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

A new organization now lands on a welcome flow before the app, and stays there until it finishes or skips it (a new Organization.onboardedAt, set by POST /api/me/onboarded; existing organizations are marked done by the migration).

Step one asks which agent the person uses. An MCP agent (Claude, ChatGPT, Poke, and the new Claude Code and Claude Desktop) is shown the server address with its own steps, Claude Code's as a terminal command, while the page polls for the login its sign-in makes; over http only the two local agents can be picked, the rest greyed out with a pointer to self-hosting. A login agent gets its login at once, as a message to paste with the sign-in page, username and password.

Step two is the catalog with a plus per integration and a count of connected accounts. A mailbox goes to a page with a Test connection button, backed by a new api route that signs in over IMAP and SMTP and saves nothing, and a provider sign-in started from the flow (?returnTo=welcome, kept in the handshake cookie) comes back to the new connection's permissions page, which ends in Confirm. The app's add-connection path reuses the same catalog and mailbox page instead of the dialog. High-risk actions now come last in the catalog, kept so by a test.


Open workspace in Conductor

…permissions

A new organization is sent to /welcome until it finishes or skips the flow
(Organization.onboardedAt, set by POST /api/me/onboarded). Step one picks
the agent: an MCP agent (Claude, the new Claude Code and Claude Desktop,
ChatGPT, Poke) is shown the server address and its steps while the page
waits for its sign-in, and over http only the two local ones can be picked;
a login agent gets its login at once as a message to paste. Step two is the
catalog, a plus per integration with how many accounts are connected: a
mailbox goes to a page with a Test connection button (a new api route that
signs in and saves nothing), and a provider sign-in started from the flow
comes back to the new connection's permissions page with Confirm.

The app's add-connection path uses the same catalog and mailbox page in
place of the dialog. High-risk actions come last in the catalog, with a
test that keeps it so.
@hkonsti
hkonsti merged commit 7f58fad into main Oct 8, 2026
2 checks passed
@hkonsti
hkonsti deleted the hkonsti/onboarding-flow-design branch October 8, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant