Group administrators should have access to all the projects created by their group members | Community
Skip to main content
Level 9
February 24, 2026

Group administrators should have access to all the projects created by their group members

  • February 24, 2026
  • 2 replies
  • 33 views

Current situation is that if the group member does not follow the process and creates projects without the group share, the group administrator would not be able to see the project. This means that the group administrator does not have autonomy and would either require the systems administrator to share those types of projects to the group administrator or do a default sharing via access level which is missing the share to group administrator and only share to the homegroup.

Let’s give the group administrator the autonomy so that they can create workflows and see all the projects for their group!

2 replies

Patrick-antegma
Level 4
February 24, 2026

One of the purposes is to groups is to model your organization. The main problem is that group administrators main role is to manage the group and not the projects of a group. The group administrator’s role is to handle the group specific settings.

 

When given the group administrator the permissions to change projects per default, you would have no way to remove this permissions when you don’t want to give them the permissions.

 

Why don’t you create a second group or team “Group x administrator” and assign them to the projects via project template.

KellieGardner
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 26, 2026

@PollyCo - Agree It would be nice if group admins could get that access. The workaround I’ve always done is sharing at the template level, portfolio or in the access level so that group admins can get access either through a team or job role, etc.