Account Setup

Get your Architecto account ready for design work, team collaboration, billing, security, and integrations.

Account and Sign-In

Architecto uses the application authentication configuration as the source of truth. The currently configured sign-in methods are:

New Account Checklist

1. Create an account with email/password, magic link, Google, or GitHub.
2. Verify the email address when prompted.
3. Complete onboarding so Architecto can tailor the workspace to your architecture workflow.
4. Create or join an organization if the work belongs to a team.
5. Review profile, security, billing, and integration settings before inviting collaborators.

Workspace Profile

Use workspace settings to keep the account identity and defaults clean:

• Profile - Set display name, avatar, and public identity details.
• Theme - Choose light, dark, or system behavior.
• Locale - English and Deutsch are configured locales.
• Default architecture preferences - Set cloud and export defaults where the workspace exposes them.
• Notifications - Choose which account, collaboration, and workflow events should reach your inbox.

Organizations and Seats

Organizations are enabled, and users are allowed to create organizations. Use organizations when designs, diagrams, imports, analysis, or documentation need shared ownership.

Recommended Setup

1. Create an organization for the company, platform team, or client engagement.
2. Invite members with the minimum role they need.
3. Assign paid seats only to members who need Pro or Ultimate entitlements.
4. Keep billing ownership with an organization owner or administrator.
5. Remove unused seats when teammates leave a workspace.

Seat-based billing is configured for paid checkout plans, so organization licensing should be reviewed whenever team membership changes.

Billing and Entitlements

Architecto billing is Stripe-backed. The public paid checkout plans in the current configuration are Pro and Ultimate. Basic exists as a hidden daily plan and should not be presented as a public tier.

New users receive a 14-day guided trial assignment during signup and a 1,000-credit signup grant when the signup hook completes. The guided trial window controls onboarding and lifecycle guidance; unused signup credits remain spendable after day 14.

Upgrading a Plan

1. Open billing from the workspace or organization settings.
2. Choose Pro or Ultimate.
3. Select monthly or yearly billing in the currency shown by the checkout.
4. Confirm seat count and payment details in Stripe checkout.
5. Return to Architecto and refresh billing status if the workspace has not updated after the webhook completes.

Plan changes are mapped from Stripe price IDs back to Architecto plan tiers. If a checkout or webhook cannot resolve a configured price ID, the account falls back to Free entitlement until billing is corrected.

Security

Password and Email

• Use a unique password when signing in with email and password.
• Keep email verification enabled for new signups.
• Use the password reset flow instead of sharing credentials across a team.

Passkeys

Passkeys are enabled and are the preferred low-friction security upgrade after account creation. Add passkeys from account security settings on devices that support Windows Hello, Touch ID, Face ID, platform authenticators, or security keys.

Two-Factor Authentication

Two-factor authentication is enabled through the authentication plugin. Turn it on for owners, administrators, and anyone managing billing, integrations, or production architecture data.

API Access and Integrations

Use developer or workspace API settings for API keys and webhooks when the workspace exposes them. Store keys in a secure secret manager and rotate them when access changes.

Integration availability depends on configured provider credentials. This documentation focuses on GitHub, Jira, Linear, Slack, Microsoft Teams, Google Docs, and Notion. Provider buttons should only be shown when the matching client ID and secret are configured for the environment.

Use integrations for:

• Importing or reviewing repositories through Git providers.
• Sending architecture, drift, or review events to team workflows.
• Creating downstream documentation or issue-tracking records from validated architecture work.
• Connecting webhooks for custom automation.

Storage and Data

Architecto saves architecture work in the cloud workspace. Treat exports as delivery artifacts, not as the only copy of the system record.

• Export diagrams and generated documentation from the relevant workspace surface.
• Keep sensitive architecture exports in approved company storage.
• Delete unused diagrams intentionally; deletion workflows can be permanent.
• Use account deletion only when ownership, exports, and billing have already been reviewed.

Next Steps

• Create your first architecture - First Architecture
• Review analysis output - Understanding Analysis
• Explore integrations - Integrations
• Check billing behavior - Pricing