Feature · Getting started
Accept an invitation
Sign in with Google, GitHub, a code sent to your email, or a password. Sign-up asks for your name, your organization and your role.
How it works
Ways to sign in
- Google or GitHub, when your Agent server offers them.
- An email code: a 6-digit code, or the same code as a link. The code lasts 10 minutes and allows 5 tries. You can ask for a new code after 30 seconds.
- Email and password. A password has at least 12 characters.
Sign-in and sign-up use the same email code flow.
Sign up
Give your name, the organization name and, optionally, your role: Engineering lead, Engineer, Product or Founder. Agent then creates:
- your organization, with you as the owner;
- your CEO,
@ceo, and Ava, your assistant; - a starting daily budget.
Join by invite
Open the link in the invite email. Sign in with your account, or create one.
Single sign-on
"Continue with SSO" by email domain is not built. Enterprise identity (OIDC, SAML and SCIM) exists when your Agent server turns it on. See Enterprise identity.
From the help article Sign in and sign up, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
AnyonegetSignupOptionsGets signup options.
Types:
EmptyRequestreturnsSignupOptionsDto
AnyonesignupStartEmails a six-digit sign-in code (also usable as a link). The same answer whether or not the address has an account.
Types:
SignupStartRequestreturnsSignupStartResponse
AnyonesignupVerifyChecks an emailed code and signs the person in.
Types:
SignupVerifyRequestreturnsSignupVerifyResponse
AnyoneoauthStartThe provider's consent URL; its callback signs the person in (or links the provider to them, for connect, or accepts an invitation, for invite).
Types:
OAuthStartRequestreturnsOAuthStartResponse
AnyoneNo API tokenscreateOrgThe signed-in person's own organization, with them as owner; the session switches to it.
Types:
CreateOrgRequestreturnsCreateOrgResponse
ViewergetOnboardingGets onboarding.
Types:
EmptyRequestreturnsOnboardingStateDto
AdminskipOnboardingStepSkips the onboarding step.
Types:
SkipOnboardingStepRequestreturnsOnboardingStateDto
AdminNo API tokensconnectStartConnects the start.
Types:
ConnectStartRequestreturnsConnectStartResponse
AdmingetConnectGets the connect.
Types:
ConnectIdRequestreturnsConnectSessionDto
AdminNo API tokenscompleteConnectCompletes the connect.
Types:
CompleteConnectRequestreturnsConnectSessionDto
AnyonegetInviteWhat an invitation link is for, and how this person can accept it here.
Types:
InviteLookupRequestreturnsInvitePreviewDto
AnyoneinviteCodeStartEmails a sign-in code to the invited address, so accepting proves it. The same answer as signupStart.
Types:
InviteCodeStartRequestreturnsSignupStartResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Integration changed
- Onboarding changed
- Address proven
- Integration connect failed
- Integration connect started
- Integration connected
- Signup completed
- Vendor trigger removed