Set Up a Workspace

Set up one workspace completely before scaling membership or automation. This sequence establishes identity, reporting currency, MFA, subscription, data connections, and owner-controlled defaults in a verifiable order.

Before You Start

Prepare:

• company and optional identity-organization name
• legal operating country
• reporting base currency
• access to a TOTP authenticator
• authority to connect Stripe
• authority to connect the business bank provider
• a workspace owner who will remain available
• a list of the first members and their intended roles

If you plan to use a custom email domain, also identify the DNS administrator and a subdomain such as invoices.example.com.

1. Authenticate

Open Sign up and continue with Google, or select Show other options for Apple, GitHub, or email. Company SSO users should use the identity method configured by their organization.

Email starts the hosted identity flow with the entered address. It is not a local Eigenn password form.

2. Create the Workspace

Complete Create your Canvas workspace:

1. Enter Company name.
2. Enter Organization name when the identity organization should use a different display name.
3. Select the company country.
4. Select the reporting base currency.
5. Submit once and wait for navigation.

Workspace creation also attempts to prepare default Vault folders, a default collections policy, and the identity organization when provider configuration is available. These background defaults are independent, so verify them later rather than assuming every task completed with the form.

3. Enroll MFA

1. Select Generate QR code.
2. Scan it with a TOTP app.
3. Enter the six-digit code.
4. Select Verify & enable.

If you cannot scan, use the manual key. Store the authenticator securely. The current flow does not issue downloadable recovery codes.

The Cancel action in the enrollment view can continue to plan setup without completing MFA. Do not use that as the standard owner setup; verify at least one factor before adding financial connections.

4. Select the Plan

Choose Starter, Pro, or Enterprise on the monthly plan screen and complete hosted checkout.

When checkout returns:

• wait while Eigenn confirms activation
• select Retry status check if synchronization times out
• do not create a second checkout while the provider shows a successful payment

The first-run plan screen currently has no Free card.

5. Complete Required Connections

The protected app opens a required connection flow until the workspace has Stripe and at least one bank connection.

1. Connect Stripe.
2. Connect the bank provider.
3. Choose the bank accounts to add.
4. Wait for the bank sync step.
5. Review the Stripe and bank summary.
6. Select Finish setup.

If either connection already exists, the flow starts with the missing step. It cannot be dismissed while a requirement is unmet.

6. Verify Workspace Identity

Open Settings → General as the owner.

1. Upload the company logo if desired.
2. Confirm company name, email, and country.
3. Review transaction export defaults.
4. Leave Delete team untouched.

Company email is a workspace contact value. It does not change an individual's sign-in email.

7. Confirm Currency and Regional Preferences

Open Settings → Account → Currency and verify the base currency. If it must change:

1. select the new currency
2. select Update in the confirmation toast
3. wait for the balance-conversion job to complete
4. compare representative balances

Then open Settings → Account → Date & Locale for your personal timezone, date, time, and week-start preferences.

These are not all workspace values: locale and formatting are personal, while base currency is shared and owner-only.

8. Establish Access Policy

Before sending invitations:

1. open Settings → Security
2. decide whether future members must use MFA
3. enable Require MFA for New Members if required
4. select Save
5. invite a test member after activation
6. confirm the member is required to enroll or verify MFA

The rule is prospective. Members who joined before activation are not forced into MFA.

Session timeout, IP whitelist, audit retention, data retention, and anonymization values can be saved on the same page but do not currently change product behavior. Do not treat them as completed controls.

9. Add Members Carefully

Use Settings → Members or Settings → Account → Teams according to the membership task.

• Keep at least two owners when the organization needs continuity.
• Use Viewer for read-only access.
• Remember that Member can perform many team writes.
• Current billing service behavior also allows Members to start checkout, open the billing portal, and schedule cancellation.

See Manage Team Access for the complete role workflow.

10. Configure Alerts and Billing Review

Each operator should open Settings → Notifications in the workspace and review their own channels. Preferences do not apply to teammates automatically.

Then have the owner review Settings → Billing:

• current plan
• cancellation badge
• hosted billing portal
• order history
• billing delegates

Delegate status is currently an administrative label. It does not grant new billing permissions or send renewal reminders.

11. Verify the Operating Record

Before enabling automation:

1. compare connected bank accounts with the provider
2. compare recent transaction dates, signs, and balances
3. compare Stripe customers and invoices
4. inspect connection sync status
5. open Settings → Usage and check whether its values look credible
6. if Usage shows zero with No limit everywhere, treat it as the known load fallback rather than real consumption
7. run the first finance review using a small, explainable period

A connection is authorized before all historical data necessarily finishes syncing.

Completion Checklist

• Workspace name, country, and base currency are correct.
• At least two owner recovery paths exist where required.
• The initial owner has a verified authenticator.
• Plan state matches hosted billing.
• Stripe and at least one bank account are connected.
• Initial sync has been compared with source records.
• Future-member MFA policy is decided before invitations.
• Every invited operator understands their role.
• Personal notification preferences are reviewed.
• Saved-only Security and Branding values are not being represented as enforced.

Troubleshooting

The form created the workspace but navigation failed

Reload and check the workspace switcher. The post-create redirect can fail after the database creation succeeds.

The MFA setup was skipped

Open Settings → Account → Security, select Add device, and complete authenticator enrollment before continuing.

The plan is still inactive after payment

Return to onboarding and use Retry status check. Compare provider state before starting checkout again.

The connection modal keeps returning

Confirm both connection facts in the same active workspace: Stripe is connected and at least one bank connection exists.

Base currency saved without conversion

Select the currency again and use Update in the toast. Saving the value and running the conversion job are separate actions.

Related Pages

• Getting Started
• Settings Overview
• Security and Access
• Billing and Usage
• Marketplace Integrations
• First Cash Review