Getting Started

Eigenn onboarding establishes the workspace, the person signing in, and the financial connections that power the product. Complete those foundations before using balances, receivables, or automation as operating signals.

What You Will Set Up

The supported first-run path covers four layers:

1. Identity — sign in through the hosted authentication flow.
2. Workspace — choose the company name, country, and base currency.
3. Account protection — enroll an authenticator app and verify a six-digit code.
4. Financial connections — connect Stripe and at least one bank account, then wait for the initial bank sync.

Plan selection is also part of the first-run path. The onboarding plan screen currently offers Starter, Pro, and Enterprise with monthly billing.

1. Sign In or Create an Account

Open Sign in or Sign up. The same hosted authentication flow handles both returning and new users.

• Continue with Google is the primary option.
• Select Show other options for Apple, GitHub, or email.
• Email entry supplies the address to the hosted sign-in service; Eigenn does not show a separate local-password form.
• If your company uses SSO, use the identity option configured for its organization.

After authentication, a new user with no workspace is sent to workspace creation. A returning user is sent to the requested page or the active workspace.

2. Create the Workspace

Complete Create your Canvas workspace:

The company name must contain at least two characters. Organization names must be unique when identity-organization provisioning is enabled.

Workspace creation also provisions default Vault folders and a default collections policy. Those background tasks are independent; a workspace can be created even when one of those defaults needs to recover later.

3. Enroll an Authenticator

After workspace creation, Eigenn opens the MFA setup flow.

1. Select Generate QR code.
2. Scan the code with a TOTP authenticator such as 1Password, Authy, or Google Authenticator.
3. If scanning is unavailable, enter the displayed manual setup key in the authenticator.
4. Enter the six-digit code.
5. Select Verify & enable.

The current enrollment flow adds an authenticator-app factor. It does not add a passkey or hardware security key. You can manage enrolled factors later under Settings → Account → Security.

4. Select a Plan

The onboarding plan page displays the paid plans available for hosted checkout. Choose a plan to continue to Stripe Checkout.

After payment, Eigenn polls for subscription activation. If activation has not synchronized before the polling window ends, select Retry status check. Do not submit checkout again while a successful payment is still syncing.

An already active subscriber is redirected out of plan setup automatically.

5. Connect Stripe and a Bank

When either required connection is missing, Eigenn opens a non-dismissible setup flow on protected product pages.

The steps are:

1. review the welcome step
2. connect Stripe
3. connect a bank provider
4. choose the bank accounts to add
5. wait for bank synchronization
6. review the connection summary and select Finish setup

The flow skips a connection step when that connection already exists. It closes only after the active workspace has both Stripe and at least one bank connection.

Selecting Finish setup records onboarding completion. The connection requirement is based on live connection records, not only on that completion flag.

6. Verify the First Operating Record

Before acting on the data:

1. Open Transactions and confirm the expected bank account and recent activity appear.
2. Open Invoices and confirm Stripe-backed customer and invoice records are present when applicable.
3. Open Settings → Usage and verify that bank, invoice, Inbox, seat, and storage counts look plausible.
4. Open Settings → Account → Currency and confirm the workspace base currency.
5. Review Settings → Notifications so each operator receives only the team-facing alerts they need.

Initial sync can continue after a connection is established. A connected badge proves authorization exists; it does not prove every historical record has finished importing.

What Is Optional

These tasks improve the workspace but are not part of the required connection gate:

• invite teammates and assign appropriate roles
• upload a workspace logo
• configure transaction export defaults
• verify a custom sending domain
• adjust personal date, time, and appearance preferences
• create additional integrations and automations

Workspace owners should complete organization, role, billing, and security-policy setup before inviting a large team.

Troubleshooting

Sign-in returns to the login page

Retry the same authentication method you used previously. If SSO reports that no team exists for the domain, an organization owner must create or configure the organization before domain-based sign-in can succeed.

Workspace creation says the name is taken

Choose a distinct organization name and submit again. The company name can remain recognizable while the identity-organization name is made unique.

The MFA code is rejected

Confirm the device clock is correct, enter the current six-digit code, and try again. Use Regenerate only when you are prepared to replace the unverified setup with a new QR code and secret.

Payment succeeded but access is still syncing

Keep the onboarding page open and use Retry status check after the timeout message appears. Avoid starting a second checkout for the same plan.

The connection flow will not close

Both Stripe and at least one bank account must be recorded in the active workspace. Complete the missing step, wait for the bank sync state, and return to the summary.

Counts or balances are unexpectedly empty

Confirm that you are in the intended workspace and that the initial sync has completed. If the connection is healthy but the record remains incomplete, send a request through Settings → Account → Support with the affected connection and page URL.

Continue Setup

• Set Up a Workspace
• Onboarding and Support
• Security and Access
• Account Preferences
• Marketplace Integrations
• Manage Team Access