Build Gallery, example type, read 8 Nov 2026
A pay equity view: who can build one, and what it needs
The trap is level: a company-wide gap without level is a headline, not a finding. The view needs pay, level, job family, location and a self-identified group field, and it needs field-level permissions so that the right person builds it. Shapes's salary band generator and compensation dashboard in the hub hold the bands the view compares against.
The guide on pay equity without a consultant walks the build on a platform that holds those fields.
Who can build it, and how
| Platform | How | Source |
|---|---|---|
| Shapes | A Vibe View described on pay, level, job family, location and group fields; the salary band generator in the hub | shapes.co/vibe-views |
| HiBob | Bob AI report in the compensation module | www.hibob.com/platform/core/analytics/ |
| Rippling | Built from a prompt by Rippling AI | www.rippling.com/platform/ai |
| Lattice | Built on compensation bands and the AI Agent's tables | lattice.com/platform/analytics |
Where Shapes is weak
Questions that need payroll or ATS data are answered through integrations, not from Shapes's own records.
Sources
- Shapes, read 8 Nov 2026
- HiBob, read 8 Nov 2026
- Rippling, read 8 Nov 2026
- Lattice, read 8 Nov 2026
- Shapes Vibe Views library, read 8 Nov 2026
Last reviewed 10 Nov 2026.