Cloud workspace
The dashboard, accounts, connector keys, and synced data.
Sign in and workspace
The dashboard is server-rendered and requires a Better Auth session. On first sign-in Shiplogue creates a personal workspace.
Two gates protect the dashboard:
- A valid session.
- At least one active connector key.
If either is missing, the dashboard redirects to sign-in or onboarding.
Connector keys
Create one named key per editor, agent, or machine. The full key is shown once; only a SHA-256 hash, prefix, and last four characters are stored.
Keys can be revoked independently. Revoking the last active key sends the workspace back to onboarding on the next dashboard request.
Send the key as a Bearer token:
Authorization: Bearer shp_live_...Workspace data
The Postgres schema stores:
- users, sessions, and workspaces
- connector keys
- opt-in activity events
- stand-ups and delivery records
- integrations, subscriptions, and usage events
The current extension syncs finished drafts only. The events API is ready for opt-in redacted activity metadata, but the extension does not send activity yet.
Dashboard metrics
The dashboard reads real database aggregates:
- stand-ups generated
- updates delivered
- estimated time reclaimed
- activity events and source count
There is no seeded dashboard content. Empty states are real empty states.