Admin Tools
The admin area manages the data that makes inspections and proposals accurate. These tools are intentionally separate from field data entry because they affect mappings, visibility, pricing, user permissions, and Salesforce write behavior. The goal is to let high-level users maintain catalogs and forms without making every change through code or direct Salesforce manipulation.
Main tools
| Tool | Purpose | Typical owner |
|---|---|---|
| Catalog Setup | Add/edit inspection items and inspect coverage | High-level admin |
| Product Mappings | Map inspection items to Salesforce Product2 records | Division admin |
| Branch Pricebooks | Validate active pricebook entries and pricing | Division/admin team |
| Form Editor | Maintain inspection structure by division/type | Level 4+ or admin |
| Users | Review Salesforce-provisioned users and access | Level 5 |
| Operations | Monitor submitted/review workflow state | Managers/admins |
Operating model
Inspection form item ── maps to ── Salesforce Product2
Product2 ── appears in ── Division pricebook
Division pricebook ── controls ── availability and list price
Admin tool decision ── changes ── what field users can selectCatalog setup direction
Catalog setup should become the user-friendly control center for item readiness. The desired long-term pattern is to select an inspection item and immediately see:
- whether the item is mapped globally or by division;
- which Product2 record is used;
- which pricebooks have an active entry;
- whether the item appears on active inspections;
- which divisions can be updated together.
Pricing rule
Most operations price by division, not branch. Branch-specific behavior should be treated as an exception. The known example is NYC Branch 03 under NNJ, where specific inspection items map to different Salesforce products than the rest of the division.
Pitfalls
- Do not treat branch pricebook behavior as the default pricing model; most catalogs are division-scoped.
- Do not activate an inspection item without confirming that the mapped Product2 is active in the intended pricebook.
- Do not assume a global mapping is always correct when a division override exists.
Related pages
- Salesforce Integration explains the Product2 and PricebookEntry records.
- Roles and Permissions explains who can access sensitive setup tools.