Bricks documentation

Bricks is field sales software. Reps visit customers, record what happened, take orders and collect money on the spot; their managers plan the work and review it; the back office invoices, reconciles and reports on it.

These pages are grouped by the job you are doing, not by the part of the product they belong to. Start with the section that matches your work.

Field app

For reps working in the field, mostly on a phone. Recording visits, taking collections, giving samples, planning and reordering your day, and using a paper receipt book.

Managing your team

For supervisors and managers. Approving recorded visits and planning the days of the reps you manage.

Back office

For office staff handling the daily paperwork: recording and approving collections, setting reference codes, voiding spoiled paper receipts, and following where collected money lands in accounting and cash vaults.

Setup & administration

For workspace administrators configuring Bricks: issuing receipt books, monitoring and closing them.

What is not here yet

These pages cover Visits, Collections and Receipt Books. The rest of Bricks — orders, products and price lists, contacts, areas, tickets, assessments, questionnaires, users and permissions — is documented internally and is being added here capability by capability.

Much of what Bricks does is configured per workspace: which features are turned on, what your roles are called, and what each one may do. Where a page depends on that, it says so in an Availability note near the top, and names the permission you need rather than a role name — because role names differ between workspaces.