Getting Started

SummaryCopy Anchor Link

Eigenn onboarding establishes the workspace, the person who signs in, and the financial connections that power the product. Complete those foundations before you use balances, receivables, or automation as operations signals.

What You Will Set UpCopy Anchor Link

The supported first-run path covers four layers:

1. Identity — Sign in through the hosted authentication flow.
2. Workspace — Choose the company name, the country, and the base currency.
3. Account protection — Enroll an authenticator app and confirm 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 shows Starter, Growth, Scale, and Enterprise. Starter is marked as recommended. Starter, Growth and Scale use monthly hosted checkout; Enterprise requires a sales agreement and cannot be purchased through self-service checkout.

CapabilitiesCopy Anchor Link

Eigenn enables new users to securely create and configure a workspace, sign in with supported identity providers, set up multi-factor authentication, select a paid plan, and connect both Stripe and a bank account. The onboarding supports background provisioning of default folders and collection policies. Users can test and verify their workspace, view financial records, manage notifications, and further configure workspace roles and controls.

PrerequisitesCopy Anchor Link

You need an active internet connection and a supported web browser. Have access to a company identity or email, and be ready with authentication devices like a phone for TOTP codes. You will need access to a Stripe account and at least one bank connection for integration. Payment information is necessary to select a plan and activate subscriptions. Organization and company details will be required to fill workspace details.

ConceptsCopy Anchor Link

What Is OptionalCopy Anchor Link

These tasks improve the workspace, but they are not part of the necessary connection gate:

• invite teammates and assign the correct roles
• upload a workspace logo
• set transaction export defaults
• confirm a custom sending domain
• adjust personal date, time, and appearance preferences
• create more integrations and automations
• create more planning models, dimensions, and shared views
• publish or pin Assistant work that the team must revisit

We recommend that workspace owners complete organization, role, billing, and security-policy setup before they invite a large team.

WorkflowCopy Anchor Link

1. Sign In or Create an AccountCopy Anchor Link

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

• 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 that your organization set.

After authentication, Eigenn sends a new user with no workspace to workspace creation. Eigenn sends a user who returns to the requested page or to the active workspace.

2. Create the WorkspaceCopy Anchor Link

Complete Create your Eigenn workspace:

The company name must contain at least two characters. An organization name must be unique when identity-organization setup is on.

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

3. Enroll an AuthenticatorCopy Anchor Link

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 you cannot scan the code, 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 PlanCopy Anchor Link

Choose Starter, Growth or Scale on the onboarding plan page to continue to Stripe Checkout. For Enterprise, contact support to arrange a sales agreement; a visible plan card does not make it available through self-service checkout.

After payment, Eigenn polls for subscription activation. If activation does not synchronize before the poll window ends, select Retry status check. Do not submit checkout again while a successful payment continues to sync.

Eigenn automatically redirects an already active subscriber out of plan setup.

5. Connect Stripe and a BankCopy Anchor Link

When connection enforcement is enabled, Eigenn opens a non-dismissible setup flow for workspace Owners with write-enabled billing when either required connection is missing. Members and Viewers are not blocked by this gate.

The steps are:

1. Read the welcome step.
2. Connect Stripe.
3. Connect a bank provider.
4. Choose the bank accounts to add.
5. Wait for bank synchronization.
6. Examine the connection summary.
7. Select Finish setup.

The flow skips a connection step when that connection already exists. It closes after the active workspace has an enabled Stripe connection with authorization and an account identifier, plus a connected bank provider with at least one enabled account. If connection facts cannot load, the gate does not block; confirm readiness in the connection settings.

When you select Finish setup, Eigenn records onboarding completion. Eigenn bases the connection check on live connection records, not only on that completion flag.

6. Confirm the First Operations RecordCopy Anchor Link

Before you act on the data:

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

Initial sync can continue after you establish a connection. A connected badge proves that authorization exists. It does not prove that the import of every historical record is complete.

7. Complete Workspace ActivationCopy Anchor Link

Open Assistant → Workspace activation. This checklist uses live workspace conditions, so it helps you find setup that is still incomplete after the connection flow closes.

1. Review the incomplete activation steps.
2. Complete a linked task in the product, or start a suggested Assistant prompt.
3. Return to Workspace activation.
4. Confirm that the step now shows complete.
5. Open What I know about your business and save the stable business context that Assistant should keep in mind.

Use the business profile for industry, fiscal year, base currency, goals, focus areas, and durable notes. Keep temporary scenario assumptions in the related forecast or planning model.

8. Create the First Planning ModelCopy Anchor Link

Use Scenario planning on Scale or above when the team needs a custom operating model beyond the standard Forecast workbench.

1. Open Scenario planning → Models.
2. Select New model.
3. Choose a focused template such as 13-Week Cash Flow, P&L and Runway, Headcount plan, or Receivables & DSO.
4. Confirm the time range and actuals boundary.
5. Import or link the required planning actuals.
6. Add one alternative scenario.
7. Save a review view and share the lowest access that the reviewer needs.

Start with one decision. Do not recreate every company spreadsheet during onboarding. Continue with Build a Driver-Based Planning Model when you need to define variables and formulas, or Configure Planning Time and Actuals when the model calendar and actuals boundary need more care.

9. Establish Workspace ControlsCopy Anchor Link

Before automation or customer data expands, configure the shared controls that the team needs.

• Open Settings → Approvals to require ordered sign-off for sensitive actions.
• Open Settings → Customer fields to define business-specific fields that should appear on every customer.
• Open Settings → Members and confirm that owners, members, and viewers have the intended roles.
• Open Settings → Security and confirm the workspace MFA policy.

Test an approval policy with a low-risk representative action. Add only a small customer-field set with a clear owner for each value.

Behavior specificationCopy Anchor Link

TroubleshootCopy Anchor Link

Sign-in returns to the login pageCopy Anchor Link

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

Workspace creation says that the name is not availableCopy Anchor Link

Choose a distinct organization name. Then submit again. The company name can stay recognizable while you make the identity-organization name unique.

Eigenn rejects the MFA codeCopy Anchor Link

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

Payment succeeded but the access sync continuesCopy Anchor Link

Keep the onboarding page open. Use Retry status check after the timeout message appears. Do not start a second checkout for the same plan.

The connection flow will not closeCopy Anchor Link

Confirm an enabled, authorized Stripe connection and a connected bank provider with an enabled account in the active workspace. Complete the missing step and review the summary. If you cannot continue, use Contact support, Switch workspace, or Sign out.

Counts or balances are unexpectedly emptyCopy Anchor Link

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

DiagramsCopy Anchor Link

Rendering diagram…

ScreenshotsCopy Anchor Link

Activation hub recommending the first business outcome and linking to documentation and support.

Shown with synthetic data in a local workspace.

VerificationCopy Anchor Link

1. Open Eigenn and confirm the sign-in page presents Google and other options, and allows authentication with your organization’s selected identity method.
2. After signing in, check that workspace creation requires a unique company name of at least two characters, country, and base currency. Submission should succeed unless restricted by organization-name rules.
3. Following workspace creation, ensure that a QR code for MFA can be generated and set up by a standard TOTP app. Verification should succeed with a current code.
4. Upon reaching the plan selection page, select a self-service plan and verify that Stripe Checkout is launched for payment. Enterprise requires a sales agreement instead. Successful payment should activate the subscription without requiring checkout to be submitted again.
5. As a paid owner with connection enforcement enabled, open a protected area with a missing connection. Confirm the required flow and its recovery exits. After setup, check authorization and enabled bank accounts separately from historical sync completeness.
6. Inspect Transactions, Invoices, Usage, and Currency in Settings to ensure that the correct data from the connected bank and Stripe accounts has synchronized and is visible.
7. Use the Assistant workspace activation checklist and confirm it updates when tasks are completed within the product.
8. Create a simple planning model and confirm it is listed in the Models view, with actuals imported or linked, and share options available. Confirm additional planning model links are operational.
9. In Settings, test Approvals, Customer fields, Members, and Security configuration—ensure changes are saved and policies are enforced according to roles and MFA settings.

RelatedCopy Anchor Link

Continue SetupCopy Anchor Link

• Set Up a Workspace
• Onboarding and Support
• Security and Access
• Account Preferences
• Marketplace Integrations
• Manage Team Access
• Assistant Workspace and Saved Work
• Create Your First Planning Model
• Build a Driver-Based Planning Model
• Connect Planning Data and Actuals
• Configure Planning Time and Actuals
• Configure Approval Policies
• Configure Customer Fields