Role Types

activate supports three types of roles static roles dynamic roles target roles static roles a static role is defined directly within activate, and members are added manually through the interface common use cases department based roles (e g , finance, hr) location based roles (e g , auckland office) characteristics membership is managed directly in activate no external data source is required dynamic roles a dynamic role automatically calculates membership based on information from external systems such as {{active directory}} common use cases roles based on ad groups or {{ou}} s system specific roles such as service desk or administrator roles characteristics defined by a members parameter in activate membership is updated automatically from the external source in activate studio, dynamic roles are shown with a gear icon overlay on the role icon activate does not support nested groups for role memberships dynamic roles are evaluated on demand rather than on a fixed schedule membership is calculated when a user’s roles are checked and stored only after the user accesses activate as a result, role membership may not be up to date for users who have not logged in recently for reporting scenarios, a scheduled task may be required to ensure role data is refreshed target roles target roles are hybrid roles used mainly for security checks and targeting logic , rather than direct membership key points users are not automatically added viewing role members will show no results use an availableusers parameter instead of members intended for internal logic and access control built in target roles self – true if the current user is the same as the target user (similar to windows “self”) owner – true if the current user owns the target object (e g , distribution list or security group) direct reports – true if the target user is a direct report of the current user