Life. Work. More together.
Workspace setup

Review setup choices and know what can change later

Use explanations alongside each choice, confirm dependencies and preserve established history.

Use explanations alongside each choice, confirm dependencies and preserve established history.

Read the choice before confirming it#

Setup asks practical questions so the workflow fits the workspace. Each help link opens a focused comparison in a new tab, leaving the setup page available.

A choice can affect visibility, record structure, payment handling, tax presentation or a future correction. Read the explanation rather than selecting an option only because it appears first.

  1. Check the active profile and workspace.
  2. Compare the offered options using the relevant help link.
  3. Confirm permissions, country, currency and required apps.
  4. Review the final summary before saving.

Presentation and history are different kinds of change#

A theme, view or interface language can change presentation without changing original records. Foundational financial choices, issued documents, posted entries, completed sales and closed cash counts have stronger protections.

Where the system requires a reviewed migration, create a deliberate plan for the affected records. Do not use a profile switch, app disable or setting rename to bypass history controls.

Choose useful reports and integrations#

Report preferences choose the supported views you want to work with. They do not create transactions, convert a cashbook into double-entry books or submit a government return.

Exports, local checks, integration requests, sandbox responses and live submissions are different outcomes. Read the capability shown for the selected workflow and confirm the actual result.

When more help is needed#

Use Support with the action attempted, the relevant workspace and a clear description of the result. Keep passwords, payment-card details and provider secrets out of the message.

For tailored work, describe the desired outcome and review the written scope and quote before accepting. A request is not a promise that an unimplemented integration already works.

Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.