Get Help

Use the "Forgot password?" link next to the password box on the login page. You'll get an email with a link to set a new one. If the link says it's invalid or expired, request a fresh one — a reset link is single-use, and it has to be opened in the same browser that asked for it unless your deployment uses the token-based email template.

Because this deployment's Supabase project doesn't have Google sign-in switched on. The button is hidden rather than shown-and-broken. Whoever operates the deployment can enable it with a Google Cloud OAuth client and the provider toggle in Supabase — no redeploy needed, the button appears within a few minutes of it being turned on.

Yes — the eye icon at the right-hand end of any password box reveals what you've typed, and hides it again. It always starts hidden, on every page and every visit.

Two things gate every page: whether the business has that module licensed, and whether the person's role carries the permission. An unlicensed module's pages don't appear at all. Check the member's role under the business's Team & Permissions screen.

A business is the company — one inventory, one tax registration, one crew, one customer ledger. An offering is a product or service line you market, and only Discovery works per-offering. Most modules are per-business; Discovery is the exception.

Use the business switcher in the top bar. It shows each business's own logo, or a generic icon for one that hasn't set one. The module rail and everything in it reloads for the business you pick.

Activate a module from the business's Licenses screen. Cancelling one never deletes data: you get 30 days of read-only grace, after which access stops but every row is kept. Reactivating restores everything, including events that were parked while it was off.

No. Nothing hard-depends on anything else. A feature that would normally show another module's data just leaves that section out when it isn't licensed, rather than failing. Finance works with hand-entered bills whether or not Inventory or Service is on.

Only if you want your AI usage billed to your own provider account. Otherwise the platform's included credit is used automatically. Connect your own key from Settings → Billing if you'd rather use it; your own key always wins when one is connected.

Settings → Usage breaks down AI runs and credit consumption. Repeatable AI operations are cached, so asking for the same thing twice doesn't bill twice.

Almost always a missing line rather than a broken ledger: until the year is closed, the period's own profit hasn't moved into retained earnings. WonderArk shows it as its own equity line for exactly this reason — check you're reading that line, and check the trial balance agrees.

No, and that's deliberate. Correction is by reversal: reverse the entry and post a correct one, so both halves stay in the account's history where an audit can see them. A filed (locked) period is never reopened.

Check the Finance dashboard's unposted documents list — it names the reason. The two common ones are a chart of accounts that hasn't been set up yet, and a document with no accounting consequence. Neither is a retryable error, so they surface on screen instead of being retried silently.

No. It prepares the return — the sales and purchase registers, the reconciliation against GSTR-2B, and a readiness check across the ledger, bank and period lock. Submitting to the tax authority is still something you or your accountant do.

It suggests, it never decides. A wrong automatic match hides a real missing entry behind a plausible one, and nobody re-checks a transaction already ticked off. The amount is a gate, candidates come back ranked with reasons, and you confirm each one.

Both have a bulk import. Inventory takes a CSV with at least `sku` and `name`; Discovery accepts CSV, Excel or PDF and uses AI to map whatever columns your file has onto its own fields.

No, that's the intended behaviour platform-wide. Below the tablet breakpoint every table becomes one card per row with labelled fields, rather than a table you'd have to scroll sideways through or squint at.

Admin (in the avatar menu) is your own account's business and module configuration. The Platform portal is the superadmin control plane for the whole deployment — branding, plans, feature flags, AI providers — and only platform superadmins can reach it.

The Platform portal's AI Providers page. A key set there is used by every account that hasn't connected its own, and takes precedence over the PLATFORM_AI_API_KEY environment variable — so you can change it without a redeploy.

CRM → Channels. You'll need a Meta app with the relevant webhook secrets set as environment variables on the deployment before the connection can verify.

Yes — create an API key from a business's Admin → API Keys screen. Keys are business-scoped and carry the same permissions model as a person's role.