In Adobe Workfront, custom statuses can be created at the system level or for specific groups. To meet the requirement that not all users need access to these new statuses, the administrator must scope them. This is achieved by creating the custom statuses within the settings of a specific Group. By associating the statuses with the group that owns the relevant projects, only users and projects within that group will be able to see and use them, effectively segmenting their availability from the rest of the system.

A. User profiles do not have a "Status Settings" area for creating custom statuses. Statuses are a system or group-level configuration, not a personal user setting.

C. While Agile teams use custom statuses on storyboards, the storyboard is a tool for visualizing and using statuses, not for creating them. The fundamental administrative action is creating the status for the group in the Setup area.

1. Adobe Workfront Documentation - Create or edit a group status:

"As a group administrator, you can create custom statuses for the groups you manage. The statuses you create are available only for objects associated with that group."

Location: Adobe Experience League > Workfront Documentation > Administrator Guide > Set up Workfront > Create and manage Groups > Create or edit a group status. (This article explicitly details the process described in option B).

2. Adobe Workfront Documentation - System-wide vs. group-specific statuses:

"Statuses can be created for the entire Workfront system or for a specific group. ... When you create a status for a specific group, only users associated with that group can see and apply the status to the objects they work on."

Location: Adobe Experience League > Workfront Documentation > Administrator Guide > Set up Workfront > Project Preferences > Statuses > System-wide vs. group-specific statuses. (This section clarifies the scoping mechanism central to the question).