Hierarchical Security Modelling

Allows for access based on management chain or a position hierarchy

Does not use standard sharing

Can be used with all security models - roles, teams, shares

Read Access: Manager or Parent positions have acces to records owned by their reports and downwards depending on the hierarchy depth.

Write, Update, Append, Append To access is only granted to the direct parent of reports/position (Scenario - Manager needs to work on behalf of report - employee is on holiday etc.)

manager has access to records that reports have access to via security roles and shares

Performance (recommendations still under development)

• Aim for four levels of hierarchy

• Use with other security models

• Related to number of users in in the parent's organizations

Security has moved to Settings | Security

Users, Security Roles, Field Security Profiles, Positions, Teams, Business Units, Hierarchy Security, Access Team Templates

Position Hierarchy

Assign users to a position (new entity). Position is relevant only if Custom Position Hierarchy is selected.

Users related via a visual hiearchy

Hierarchy Security

Enable Hierarchy Modeling

Must be enabled, default is ???

Select Hiearchy Model

Choose Manager Hierarchy or Custom Position Hierarchy. Managers uses Manager field on user

records.

Set the Hierarchy Depth

Addresses possible performance issues by keeping the number low.

Exclude entities from hierarchy

Only user-owned entities can be part of the model. By default, all entities are included - specify which ones to exclude.

New Queries in Advanced Find

New query options in advanced find to support hiearchy include:

• Equals Current User Or His Reporting Hierarchy

• Equals Current User And His Teams or His Reporting Hierarchy And Their Teams