Getting started

Onboarding checklist

Put a new agaro workspace into operation in the safest practical order.

Use this sequence after the onboarding wizard. It keeps master data and permissions in place before operational transactions begin.

1. Confirm company and fiscal settings

Open /settings?tab=general and confirm the legal business name, branding, and document identity. Then open /settings/finance to verify country, currency, fiscal year, invoice numbering, payment terms, and cash rounding.

Do this before sending invoices or posting bills. Numbering and tax choices affect documents that should remain historically stable.

2. Install only the modules you will use

Open the Store at /modules. Managers can request modules. Paid capabilities show the billing path available to the workspace. Installed modules determine both navigation and server access.

See Installing modules for module behavior.

3. Create or import master data

Start with the records other workflows reference:

  1. Contacts and vendors
  2. Products and services
  3. Warehouses and stock locations if Inventory is enabled
  4. Employees and departments if Workforce is enabled
  5. Tax rates, expense categories, income categories, and payment methods

Use the Import control on a supported list page. Preview the rows, resolve validation errors, then apply the import. Do not create invoices or purchase orders against placeholder records if the real master data is available.

4. Invite the team and assign permissions

Open /roles. Create invitations, choose a base role, and assign module access. The available base roles are SUPER_ADMIN, MANAGER, DEVELOPER, EMPLOYEE, and VIEWER.

Keep SUPER_ADMIN limited to owners who need billing, security, and destructive workspace controls. Managers operate most business workflows. Viewers can open installed modules but cannot mutate records. Permission sets and access groups can further narrow record, field, and menu access.

5. Configure security

Open /settings/security and choose the workspace two factor policy. The policy can cover all users or employees only. Team members enroll their factor from their own account security area.

Review pending invitations, privileged access, and permission sets under /roles and /settings/access-rights if you are an Access Rights administrator.

6. Connect operational providers

Connect only what the business needs:

  1. Stripe under /settings/payments for customer checkout and invoice payment links
  2. Email and calendar providers under /settings?tab=integrations
  3. Printers and barcode hardware under the Devices area when Inventory is installed
  4. AI and MCP under Developer and AI when those capabilities are enabled

7. Run one controlled transaction per workflow

Before bulk use, run a small end to end check:

  1. Create a contact, create an invoice, send it, and record a small payment.
  2. If Inventory is enabled, create a test purchase order, receive stock, create a sales order, and deliver it.
  3. If Workforce is enabled, create an employee and verify attendance access before payroll setup.
  4. If Projects is enabled, create a project, task, and milestone, then confirm ownership and visibility.

Use test records with obvious names and move them to Recently deleted afterward where the module supports soft deletion.

8. Review reports and audit history

Open the module reports and compare totals with the controlled transactions. Open the Activity Log at /activity to confirm that changes show the expected actor and record.

If a report is empty, first confirm that the source records are in the required posted, sent, confirmed, or completed state. Draft records often do not count in operational or financial reporting.