Browse the manual
Product areas and access
The product areas available in Made with Pepper and how roles control access.
On this page
The application connects customers, work, documents, purchases and reports. Two controls determine access: enabled modules and account permissions.
Find the work you need
| Area | Task | Guide |
|---|---|---|
| Customers | Keep customer and supplier details together | Customers |
| Engagements | Connect agreed scope and milestones to invoices | Bill agreed milestones |
| Invoices | Prepare documents and record payments | Invoices |
| Purchases | Record supplier invoices and supporting files | Purchases |
| Reports | Review balances and prepare an accountant handoff | Reports, Tax periods |
| Files | Find files and their related records | Files |
| People | Find colleagues and teams | People and teams |
Use the desktop navigation rail, or More on a phone. Navigation shows only the areas your account can open.
Change enabled modules
Settings > Modules lists each module, its state and its dependencies. Expand a module to read its permissions, record types, tools and scheduled jobs.
Invoices, Customers, Items, Files, People and Settings are core modules. They stay on. Engagements, Purchases and Reports are optional modules.
Only the active owner can change module states. Admins can read the page.
- Open Settings > Modules.
- Find the optional module.
- Click Turn on or Turn off.
- Read the confirmation for that module.
- Confirm the change.
To turn on a module, its dependencies must already be on. You cannot turn off a module while an enabled module depends on it. Open obligations can also block a change. Read the refusal before trying again.
Turning off a module does not delete its records. A successful change appears in the audit log. Turning it on does not grant missing account permissions.
Control access with roles
An owner or admin can invite people and assign roles. Built-in roles provide common permissions. Custom roles select permitted actions. A guest scope can further limit modules and named records.
Module access is a ceiling. A role cannot open a disabled module, and a guest scope cannot add a missing role permission. See Roles and permissions.
Related pages
Need help with the product?
Contact support