A client requests a setup where only specific team members can access financial data on a custom form. How can this be achieved?

Question

Options

• ACreate a separate project template with restricted permissions
• BUse calculated fields to display financial data only when certain criteria are met
• CSet conditional visibility rules for the financial fields
• DApply user-level permissions to individual tasks

• A
  15% (5)
• B
  3% (1)
• C
  74% (25)
• D
  9% (3)

Explanation

Conditional visibility rules (C) directly control which users can see specific fields on a form based on their identity, role, or group membership - making financial fields invisible to unauthorized team members without restricting their access to the form itself.

Why the distractors miss the mark:

• A (separate project template) restricts access at the project level, not the field level - it's too coarse-grained and forces duplication of the entire project structure.
• B (calculated fields) determines what value to display based on data logic, not who is permitted to see the field - it's a data transformation tool, not an access control mechanism.
• D (user-level permissions on tasks) controls who can view or edit a task, not individual fields within a form - it can't surgically hide just the financial data.

Memory tip: Think of conditional visibility as a "who sees what" filter at the field level. When the requirement mentions specific people + specific fields, the answer is almost always conditional visibility - it's the only option that targets both dimensions simultaneously.

No community discussion yet for this question.