A client's organizational structure has employees moving on and off projects and switching their Workfront responsibilities often. Why would the…

Using groups for sharing is a best practice for managing permissions at scale, especially in dynamic environments. When an employee's role or project assignment changes, a system administrator only needs to add or remove them from the relevant group. This single action automatically updates the user's access to all objects shared with that group. This method is significantly more efficient and less error-prone than manually adjusting permissions for an individual user on every single project, task, report, and other relevant objects.

A. Workfront grants the highest level of access available. If a user has 'View' from a group and 'Manage' individually, they get 'Manage' access. The permissions are aggregated, not strictly overridden.

B. This is factually incorrect. Workfront allows objects to be shared simultaneously with a combination of individual users, groups, teams, and roles.

1. Adobe Workfront Documentation, "Share objects": In the section "Share an object with users, teams, groups, or roles," the documentation states, "Sharing an object with a group is an easy way to grant access to a large number of users at once. When you add or remove users from the group, their access to the object is automatically updated." This directly supports the efficiency described in the correct answer (C).

2. Adobe Workfront Documentation, "Overview of sharing permissions on objects": This document explains how permissions are determined: "When a user has access to an object from multiple permission sources (for example, they are shared on the object directly, and they are also part of a team, group, or they have access through their access level), their permissions on the object are a combination of all permissions from all sources." This principle refutes the "override" logic in option A.

3. Adobe Workfront Documentation, "Create and manage groups": The section "The value of using groups" highlights the primary benefit: "Using groups to manage your users can save you time when you need to share objects with multiple users or when you need to manage user assignments on work items." This reinforces the core reason for choosing option C.