How can field-level security be enforced in CLM?

• A. Lock all fields regardless of role.
• B. Encrypt all fields automatically.
• C. Apply field permissions to roles or groups to control read/write access to sensitive fields.
• D. Disable editing of documents entirely.

Answer: (C)

Field-level security in CLM is enforced by assigning field permissions to roles or groups, which controls who can read or write each specific field on a contract. This approach provides precise control over sensitive data, letting you show or hide particular fields based on a user’s role, rather than applying blanket restrictions. You can define for each field whether it’s readable, writable, or hidden for different roles, and then assign users to those roles or groups accordingly. For example, you might allow a contract manager to edit pricing fields while restricting access to confidential financial terms. Locking all fields or encrypting everything would disrupt usability and wouldn't deliver the targeted, per-field control that this security approach is designed to provide. Disabling document editing altogether would stop collaboration and isn’t about securing individual fields.