A consultant is working with a customer's Marketing department on an Adobe Workfront engagement. The customer has already had a successful deployment of Workfront in the IT department. This installation has been extremely simple, with a single system administrator, five custom statuses used by the IT department, and some templates and reports. The director of Marketing is adamant that the Marketing department will not be using anything created for IT. The engagement cannot disrupt the existing installation.
Which approach should the consultant take?
In this scenario, the best approach is to create separate groups for Marketing and IT within the same Workfront instance. Each group will have its own group administrator, and each department's resources (e.g., custom statuses, templates, reports) can be isolated and managed independently by the group admins.
This solution ensures that:
The existing IT setup is not disrupted.
The Marketing department can have its own customized Workfront environment without overlapping with IT's configurations.
This approach avoids creating unnecessary complexity (as in Option A with companies) or restricting functionality (as in Option B with teams).
Refer to Workfront documentation on group management to learn how to implement group-specific configurations in a single instance.
Miss
10 months agoLaine
10 months agoReed
10 months agoLawana
10 months agoBong
11 months agoLisbeth
10 months agoAlita
10 months agoTomas
10 months agoYolande
10 months agoCarman
11 months agoLeonida
10 months agoHubert
11 months agoLayla
11 months agoKasandra
11 months agoRashida
11 months agoKasandra
11 months agoXochitl
11 months agoJackie
11 months agoPhuong
11 months agoEliz
11 months agoGianna
12 months agoMargret
11 months agoNatalya
11 months agoJordan
11 months agoJennifer
11 months ago