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
1 months agoLaine
1 months agoReed
1 months agoLawana
1 months agoBong
2 months agoLisbeth
18 days agoAlita
20 days agoTomas
1 months agoYolande
1 months agoCarman
2 months agoLeonida
1 months agoHubert
2 months agoLayla
2 months agoKasandra
2 months agoRashida
2 months agoKasandra
2 months agoXochitl
2 months agoJackie
2 months agoPhuong
2 months agoEliz
2 months agoGianna
3 months agoMargret
2 months agoNatalya
2 months agoJordan
2 months agoJennifer
2 months ago