Definition
A Salesforce record in the role hierarchy that defines a user's position within the organization's data access structure, determining which records they can see based on the 'roll-up' visibility model.
Real-World Example
Consider a scenario where the system admin at BrightEdge Solutions is working with Role to control how users interact with Salesforce data and features. After configuring Role in the sandbox and validating it with key stakeholders, they roll it out to production. User adoption improves because the interface now matches how teams actually work.
Why Role Matters
A Role is a Salesforce record in the role hierarchy that defines a user's position within the organization's data access structure, determining which records they can see based on the 'roll-up' visibility model. Roles are assigned to users and arranged in a hierarchy where users at higher roles can see records owned by users at roles below them.
Roles are distinct from profiles in Salesforce: profiles control what users can do (CRUD permissions, field-level security, etc.), while roles control what data they can see based on hierarchy. A user has one profile and one role. Mature orgs design role hierarchies thoughtfully to match management structures, with hierarchy levels reflecting actual reporting relationships. Bad role design creates either too much access (managers seeing everything) or too little (managers unable to coach reps).
How Organizations Use Role
- •BrightEdge Solutions — Designs role hierarchies matching their actual management structure for realistic data access.
- •NovaScale — Reviews role hierarchy periodically as the organization evolves.
- •Cobalt Ventures — Treats role design as foundational to record-level security.