A project requires team collaboration on a marketing document. Stakeholders must review and provide feedback, while only project managers should edit the document. How should this be configured in…

Question

Options

• ASet up a proofing workflow for reviewers and assign "Edit" rights to managers.
• BShare the document publicly and allow all users to edit.
• CUse external document storage for feedback collection.
• DDisable proofing and manage feedback via email.

• A
  76% (41)
• B
  13% (7)
• C
  4% (2)
• D
  7% (4)

Explanation

Option A is correct because Workfront's proofing workflow is purpose-built for this exact scenario: it lets you assign stakeholders as reviewers (comment/feedback only) and project managers as editors with Edit rights, enforcing role-based access control within a single, auditable document workflow.

Why the distractors fail:

• B - Public sharing with universal edit access eliminates the required permission separation entirely, letting anyone modify the document.
• C - External storage (e.g., Google Drive) bypasses Workfront's native collaboration features and breaks the audit trail inside the project.
• D - Disabling proofing removes the structured review mechanism; email feedback is untracked, unversioned, and can't be tied back to specific document elements.

Memory tip: Think "proof = review, rights = edit." Workfront proofing controls who can comment, while document sharing rights control who can change. When a question mentions both reviewers and editors, the answer involves both proofing workflows and Edit rights together - that's always option A's pattern.

No community discussion yet for this question.