Which setting determines whether a user can edit a custom form within a project?

Question

Options

• AField-level security
• BSharing permissions
• CAccess level for the project
• DApproval workflow settings

• A
  8% (3)
• B
  75% (27)
• C
  14% (5)
• D
  3% (1)

Explanation

Sharing permissions control what actions a user can perform on a resource - including whether they can view, edit, or manage a custom form within a project. Option A (Field-level security) is incorrect because it governs visibility and editability of individual fields within a form, not the form itself. Option C (Access level for the project) controls a user's overall role in the project (e.g., viewer vs. member), but does not directly determine form-editing rights. Option D (Approval workflow settings) defines routing and sign-off rules for submissions, not who can modify the form's structure.

Memory tip: Think "sharing = who can touch what." If you need to grant or restrict a user's ability to edit a form as a whole, look to sharing permissions first - they sit one level above individual field controls.

No community discussion yet for this question.