Which statement describes the relationship between an analytical object and a custom duty role?

Which statement describes the relationship between an analytical object and a custom duty role?

• A. One custom duty role must be created per analytical object.
• B. An analytical object requires individual duties for each object.
• C. You can grant access to multiple analytical objects using one custom duty role.
• D. Custom duties do not affect access to analytical objects.

Answer: (C)

In this access control setup, a custom duty role is a bundle of privileges that governs what a user can do with analytical objects. An analytical object is a specific report, dashboard, or data view. You can include access to several analytical objects inside one custom duty, so assigning that single duty to a user grants them access to all the objects covered by that duty. This approach is efficient because it groups related objects under one role rather than creating a separate duty for each object. For example, a department-wide duty might grant read access to multiple dashboards used by that team, and any user given that duty gets access to all of them. Conversely, if permissions were tightly tied to individual objects with separate duties, management would become more intricate. The key idea is that one custom duty can control access to multiple analytical objects, not just a single one.

In this access control setup, a custom duty role is a bundle of privileges that governs what a user can do with analytical objects. An analytical object is a specific report, dashboard, or data view. You can include access to several analytical objects inside one custom duty, so assigning that single duty to a user grants them access to all the objects covered by that duty. This approach is efficient because it groups related objects under one role rather than creating a separate duty for each object. For example, a department-wide duty might grant read access to multiple dashboards used by that team, and any user given that duty gets access to all of them. Conversely, if permissions were tightly tied to individual objects with separate duties, management would become more intricate. The key idea is that one custom duty can control access to multiple analytical objects, not just a single one.