Skip to content
English
  • There are no suggestions because the search field is empty.

Admin | Groups

Understand how to administer Groups

Go to the Admin Overview page

Topics

 

Groups | Purpose

Groups can be used to organize projects with the additional option to limit visibility.

Groups | Organize Projects and Not Restrict Visibility

Groups can be used to organize projects, e.g. by "Project Type", and not restrict visibility.

  • In this example, projects are organized using five Groups...
    1. "Cost Reduction"
    2. "NPI"
    3. "Not Project Specific"
    4. "Sustaining"
    5. "Templates"
  • None of the Groups have restricted visibility .
    Admin - Groups - 1 - by Project Type
  • All projects are in a Group. Note: a project can be in only one Group.
    Admin - Groups - 2 - Projects assigned to Groups
  • In Playbook, the projects are organized by Group and users see all Groups and their projects, whether they are assigned to them or not. Admin - Groups - 3 - Projects in Playbook organized by Group
  • Groups can be any attribute such as, "Project Type", "Business Unit", etc. 

Groups | Organize Projects and Restrict Visibility

Groups can also be used to organize projects, e.g. by "Business Unit", and visibility can be restricted.

  • In this example, there are five groups...
    1. "Business Unit 1"
    2. "Business Unit 2"
    3. "Business Unit 3"
    4. "Not Project Specific"
    5. "Templates"
  • Groups "Business Unit 1, 2, and 3" have Restricted Visibility.
  • Groups "Not Project Specific" and "Templates" do not have Restricted Visibility.Admin - Groups - 4 - by Business Unit
  • "Project 1" is in Group "Business Unit 1", "Project 2" is in Group "Business Unit 2", and "Project 3" is in Group "Business Unit 3".
  • "Library 1" is in Group "Templates" and "Misc. Other" is in Group "Not Project Specific".
    Admin - Groups - 5 - Projects assigned to Business Units
  • In this example, Paul is assigned to "Project 1" in Group "Business Unit 1" and "Misc. Other" in Group "Not Project Specific", but is not assigned to any projects in "Business Unit 2 or 3" (i.e. Project 2 or 3).Admin - Groups - 7 - Paul Paterson assigned to Projects
  • In Playbook, Paul sees "Project 1" because he is assigned to it.
  • He doesn't see "Project 2" or "Project 3" because they are in Groups with restricted visibility, and he's not assigned to either project.
  • Paul also sees projects in Groups whose visibility is not restricted, for example, all projects in Groups "Misc. Other" and "Not Project Specific".Admin - Groups - 6 - Projects in Playbook by Business Unit
  • On the other hand, Mary is assigned to "Project 2" in Group "Business Unit 2", "Project 3" in Group "Business Unit 3", and "Misc. Other" in Group "Not Project Specific", but she's not assigned to any projects in Group "Business Unit 1" (i.e. Project 1).
    Admin - Groups - 7 - Mary Meyer assigned to Projects
  • In Playbook, Mary sees "Project 2" and "Project 3" because she is assigned to them.
  • She doesn't see "Project 1" because it is in a Group with restricted visibility, and she's not assigned to the project.
  • She also sees projects in Groups with unrestricted visibility, for example, all projects in Groups "Misc. Other" and "Not Project Specific".
    Admin - Groups - 6 - Marys Projects in Playbook

Groups | Creating

  • To create a Group...
    Admin - Groups - 8 - Create a group
  • The Pencil icon is used to Edit and the Trash Can icon is used to Delete.

Return to the Admin Overview page