Developer Accounts and Workspaces
How teams sign in, create a workspace, request sandbox access, and move toward production.
The account-access page should show the exact operator path from first sign-in to a real workspace.
The platform should make it obvious when an account is still waiting to be attached to the correct organization.
Onboarding should always point to the exact next lane instead of leaving the user on a generic summary page.
Each organization can invite the right people into the workspace without collapsing docs, API access, billing, and customer review into one shared login.
The goal is simple: keep account access, approvals, reporting, and integration history easy to find from the start instead of hiding them behind email threads.
The portal keeps those stages explicit so teams always know whether they are reading public docs, working in sandbox, or using production credentials.
The account-access page should make the current access state obvious before the user moves into organization setup.
The first-run lane should be visible from the access page instead of hiding behind generic onboarding language.
Once account access is clean, the user should know the exact next operating step.
The person shipping the integration usually owns the first account and workspace attach path.
Finance can be added once the workspace exists and billing responsibility is clear.
Audit and compliance ownership follow the initial technical setup instead of blocking it.
Platform access is built for the people who run the integration day to day: developers, technical leads, security owners, and billing or compliance contacts.
Each organization can invite the right people into the workspace without collapsing docs, API access, billing, and customer review into one shared login.
Create an account, request sandbox access, issue the first key, connect a webhook, and review usage from the same workspace.
The goal is simple: keep account access, approvals, reporting, and integration history easy to find from the start instead of hiding them behind email threads.
Approved organizations move from sandbox to production through consent review, billing setup, integration verification, and audit-ready checks.
The portal keeps those stages explicit so teams always know whether they are reading public docs, working in sandbox, or using production credentials.