Set Up a Workspace

Set up one workspace completely before you scale membership or automation. This sequence establishes identity, reporting currency, MFA, subscription, data connections, and owner-controlled defaults in an order that you can check.

Before You Start

Prepare:

• company and optional identity-organization name
• legal country of operation
• 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 find 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. A company SSO user uses the identity method that their organization set up.

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 Eigenn workspace:

1. Enter Company name.
2. Enter Organization name when the identity organization needs a different display name.
3. Select the company country.
4. Select the reporting base currency.
5. Submit the form one time only.
6. Wait for the navigation.

Workspace creation also tries to prepare default Vault folders, a default collections policy, and the identity organization when a provider configuration is available. These background defaults are independent. Check them later. Do not assume that 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 MFA. Do not use that as the standard owner setup. Confirm at least one factor before you add financial connections.

4. Select the Plan

Choose Starter, Pro, or Enterprise on the monthly plan screen. Then 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 now has no Free card.

5. Complete the Necessary Connections

The protected app opens the 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. Examine the Stripe and bank summary.
6. Select Finish setup.

If either connection already exists, the flow starts with the missing step. You cannot dismiss the flow while a necessary connection is absent.

6. Confirm Workspace Identity

Open Settings → General as the owner.

1. Upload the company logo when you want one.
2. Confirm company name, email, and country.
3. Examine the 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 check 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. The locale and the format are personal. The workspace shares the base currency, and only an owner can change it.

8. Establish Access Policy

Before you send invitations:

1. Open Settings → Security.
2. Decide whether future members must use MFA.
3. Turn on Require MFA for New Members when necessary.
4. Select Save.
5. Invite a test member after activation.
6. Confirm that the member must enroll or confirm MFA.

The rule is prospective. Eigenn does not force MFA on members who joined before activation.

You can save session timeout, IP whitelist, audit retention, data retention, and anonymization values on the same page. These values do not change product behavior now. Do not treat them as completed controls.

9. Add Members Carefully

Use Settings → Members or Settings → Account → Teams for the membership task.

• Keep at least two owners when the organization needs continuity.
• Use Viewer for read-only access.
• A Member can do many team writes.
• The current billing service also lets a Member start checkout, open the billing portal, and schedule cancellation.

See Manage Team Access for the complete role workflow.

10. Set Up Alerts and Billing Review

We recommend that each operator opens Settings → Notifications in the workspace and examines their own channels. Preferences do not apply to teammates automatically.

Then the owner examines Settings → Billing:

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

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

11. Confirm the Operations Record

Before you turn on automation:

1. Compare connected bank accounts with the provider.
2. Compare recent transaction dates, signs, and balances.
3. Compare Stripe customers and invoices.
4. Examine the 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 with a small, explainable period.

Eigenn authorizes a connection before all historical data completes the sync.

Completion Checklist

• Workspace name, country, and base currency are correct.
• At least two owner recovery paths exist where necessary.
• The initial owner has a confirmed authenticator.
• Plan state matches hosted billing.
• The workspace has Stripe and at least one connected bank account.
• You compared the initial sync with the source records.
• You decided the future-member MFA policy before invitations.
• Every invited operator understands their role.
• Each operator examined the personal notification preferences.
• You do not represent the saved-only Security and Branding values as enforced.

Troubleshoot

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.

You skipped the MFA setup

Open Settings → Account → Security. Select Add device. Complete the authenticator enrollment before you continue.

The plan is still inactive after payment

Return to onboarding and use Retry status check. Compare the provider state before you start checkout again.

The connection modal returns again and again

Confirm both connection facts in the same active workspace. The workspace has a Stripe connection, and it has at least one bank connection.

Base currency saved without conversion

Select the currency again and use Update in the toast. The save of the value and the conversion job are separate actions.

Related Pages

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