The tasks that are visible to an individual in Pacer is based on Communities. This impacts the tasks that appear on the Tasks page and the data used for the individual's dashboards and reports.
Communities allow you to have a complete list of tasks for all stakeholders, but hide certain tasks from certain people. Individuals will only see tasks that are associated with communities in which the person has been granted access.
Users are assigned to one or more Communities; Tasks are assigned to a single Community.
Common uses cases of Community:
- Within a set of tasks that needs to be completed for a specific location, some are completed by individuals at the location and some are done by individuals the corporate office. To reduce the tasks the location-level needs to see, the corporate tasks can be assigned to a community that is not granted to the location-level team.
- A project manager needs to complete a set of project tasks for each location team. In order to keep everything organized, the tasks are added to the location, but since only the PM needs to see the tasks, those tasks can be placed in a separate community that only the PM can view.
- A company wants to grant access to a vendor to complete some tasks; since the vendor should not be able to see the non-vendor tasks, the vendor related tasks are added to a specific community.
By using Communities you are able to have a consolidated list of tasks grouped by that team/location and also allows you to declutter the tasks for the applicable individuals.
Comments
0 comments
Article is closed for comments.