How do you configure analytics privileges for Talent Management data?

How do you configure analytics privileges for Talent Management data?

• A. Remove All Access To Reports
• B. Change Only Password Policies
• C. Assign Analytic Privileges And Data Access Controls; Configure Bookmarks And Role-Based Access To Reports
• D. Analytics Privileges Cannot Be Configured

Answer: (C)

Analytics access in Talent Management is controlled by combining analytic privileges with data access controls, plus using bookmarks and role-based access to reports. Analytic privileges determine what actions a user can perform in the analytics environment, such as viewing dashboards, running reports, or applying certain analytical features. Data access controls specify which data the user is allowed to see—often filtered by organization, department, location, or other criteria—so users only access information relevant to their role. By configuring bookmarks, you can predefine report views and filters for quick access, and by applying role-based access to reports, you ensure each user’s view aligns with their responsibilities. This approach provides the right balance of access and data visibility, supporting governance and the least-privilege principle. Other options don’t address the full security model: removing all access to reports would block legitimate work; changing password policies does not affect who can view analytics data; and it’s not true that analytics privileges cannot be configured, since you can set privileges, data access, bookmarks, and RBAC to control analytics access.

Analytics access in Talent Management is controlled by combining analytic privileges with data access controls, plus using bookmarks and role-based access to reports. Analytic privileges determine what actions a user can perform in the analytics environment, such as viewing dashboards, running reports, or applying certain analytical features. Data access controls specify which data the user is allowed to see—often filtered by organization, department, location, or other criteria—so users only access information relevant to their role. By configuring bookmarks, you can predefine report views and filters for quick access, and by applying role-based access to reports, you ensure each user’s view aligns with their responsibilities. This approach provides the right balance of access and data visibility, supporting governance and the least-privilege principle.

Other options don’t address the full security model: removing all access to reports would block legitimate work; changing password policies does not affect who can view analytics data; and it’s not true that analytics privileges cannot be configured, since you can set privileges, data access, bookmarks, and RBAC to control analytics access.