Decide who may open what, across companies and branches

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can say, for any control somebody is relying on, whether the server enforces it, the browser merely shapes the choice, or nothing reads it at all — and you can design a group’s access around the boundaries that actually hold: applet installs at the door, permission sets on the API, company and branch targets on documents, and roles as the one thing everything hangs off.

Presentations

1. Installing an applet is a door, not a fence — about 12 minutes, narrated
2. A target restricts documents, and not your customer list — about 13 minutes, narrated
3. Everything hangs off a role — about 12 minutes, narrated
4. Hiding a column is not withholding a number — about 11 minutes, narrated
5. What actually stops a sale below cost — about 12 minutes, narrated

Modules this series draws on

• Core Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• Applet Store
• Tenant Admin Applet
• Employee Maintenance
• Sales Invoice (Internal)
• Teams and Permissions
• Settings and Permissions
• Setting Up Pricing Schemes

All presentations · Presentations for the whole-system operator