How is a persona used pertaining to CLM customization?

• A. Personas determine which documents a user can access.
• B. Personas customize notification settings for each user.
• C. A CLM Administrator can define what users see on their User navigation Header based on their persona. (Correct)
• D. Personas set the default storage location for deployment packages.

Answer: (C)

Personas are used to tailor the user experience by mapping each user to a role-like profile that drives what appears in the UI. In CLM customization, a persona defines what a user sees in the User navigation Header, so administrators can present the most relevant tabs, links, and shortcuts for that role. This makes the interface more focused and efficient: a contract manager might get quick access to approvals and contracts, while an analyst might see reporting and insights instead. This approach guides users to their primary tasks without exposing irrelevant features, improving productivity. Remember, access to documents is governed by security permissions, not by the persona-driven header, and notification settings or deployment package storage are controlled in other configuration areas, not by the persona-based header customization.