Which statement best describes the role of a 'persona' in CLM?

Which statement best describes the role of a 'persona' in CLM?

• A. It customizes navigation, actions, and Dashboards for a user identity.
• B. It determines the user's password policy
• C. It sets the default language for the portal
• D. It creates new groups

Answer: (A)

In CLM, a persona defines the tailored user experience for a specific user identity. It determines what the user sees and can do by shaping navigation, available actions, and the dashboards or widgets that are shown. This personalization helps align the interface with the user’s role and typical tasks, making it faster and easier to work through workflows. So, describing a persona as something that customizes navigation, actions, and Dashboards for a user identity captures this idea of role-based, user-specific UX. The other options refer to security policies (password policies), locale settings (default portal language), or access-control structures (creating new groups), which are not about shaping the individual user’s interface and experience. For example, an approver persona might show an "Approve" action prominently and display a dashboard with pending approvals, while a creator persona might focus on templates and drafting tools.

In CLM, a persona defines the tailored user experience for a specific user identity. It determines what the user sees and can do by shaping navigation, available actions, and the dashboards or widgets that are shown. This personalization helps align the interface with the user’s role and typical tasks, making it faster and easier to work through workflows.

So, describing a persona as something that customizes navigation, actions, and Dashboards for a user identity captures this idea of role-based, user-specific UX. The other options refer to security policies (password policies), locale settings (default portal language), or access-control structures (creating new groups), which are not about shaping the individual user’s interface and experience. For example, an approver persona might show an "Approve" action prominently and display a dashboard with pending approvals, while a creator persona might focus on templates and drafting tools.