Expand my Community achievements bar.

The next phase for Workfront Community ideas is coming soon. Learn all about it in our blog!

How can I add a new department to our Workfront instance, but keep the global search results specific to the relevant department (so the two departments don't get results that don't apply to them)?

Avatar

Level 5

Our current Workfront production environment is set up for our Marketing Department and includes request queues, custom forms, templates, projects, layouts, dashboard, reports, etc. – everything needed to fully manage our projects in Workfront.

  • Recently, members of our video team have been given worker accounts and they are assigned tasks in a few of the marketing department templates/projects.

We now wish to set up the Video Department with their own stand-alone processes:

  • Request queues, custom forms, templates, projects, layouts, dashboards, reports, etc.
  • The Marketing Dept. members do not want to see any of the stand-alone video department objects when doing a “global” search.
  • The Video Dept. will need to see the Marketing Dept. projects that they are assigned to (and relevant reports), but otherwise they don’t want to see Marketing Dept. objects when using the global search.

Can I silo the two departments so they don’t see each other’s results when using the global search feature, but they would be able to see their own relevant projects and tasks on reports?

Thanks in advance for any help with how to proceed!

Cathy

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Level 7

Hi Cathy,

What you're describing is definitely possible, and a type of sharing security that Workfront is designed to handle. It will definitely take some careful design at the outset, and may require some rework on how your processes are designed for the Marketing team depending on how they were initially set-up.

Sharing within Workfront can be controlled by Company, Group, Team, Role and individual person across all objects (templates, queues, reports etc.)

Taking the Template object as an example, you could have a Template that has Template Sharing set to View for the Video Department Group and Manage for the specific user who designed the template. When a Marketing person said 'Create new project', that template would not appear as long as they were not a member of the Video Department Group. Project Sharing on that template could then be set to View/Contribute/Manage for the Video Department Group only.

At the initial setup of that project, only the Video Dept would be able to see it in search results. If a Marketing person were assigned a specific task on that project, then the sharing settings in Project Preferences in Setup would take hold. You could grant them access to the task and project, or the task only - for example. Those settings can also be controlled BY the Group, so the rules for Marketing don't have to be the rules for Video etc.

The same sort of settings apply across most objects, so it's mostly a matter of carefully storyboarding out sample scenarios and what should happen for each. The hard part in your instance may be going backwards to retrofit this into the existing Marketing processes, depending on how they were setup. It's not impossible, just a lot of testing.

Happy to elaborate if you have specific scenarios in mind.

Katherine

Avatar

Level 9

Hi Cathy!

We get this alot in our instance because we need to give access to various things but it makes the search feature hard at times.

I created a dashboard of 'Advanced Project Search' that has a bunch of prompts by owner, project type, start date, campaign, project name, etc.

They can use that to search for specific projects vs. weeding through the search results. It also allows me the opportunity to limit the search area to a specific segment such as department.