馃帹 Design: Explore how to evolve the Admin Area groups and project pages in the Organization context
Problem
One of the steps to migrate functionality from the Admin Area to the Organization is to create parity in the functionality we offer in both areas. For the groups and projects overview, there are two pages in the Admin Area that we need to decide how to evolve. The information that is available there consists of:
- Metadata
- Content (in case of groups)
- Members
- Invited groups
Admin Area > Projects > Project
Admin Area > Groups > Group
Proposal
Maintain the admin view for organization owners. When viewing groups/projects in the organization owner should have option to visit the project (as non-owners do) via the link, but are presented with an option to "manage" as well.
| Organization owner - Groups | Organization owner - Projects |
|---|---|
 |
 |
"Lift and shift" admin group/project views to the organization level
Open questions
-
What would be the experience in relation to the group and project list functionality in Organizations, where currently we are linking to a group or project overview page directly?
Answer: Add an additional option to go to manage view.
-
Since the Organization groups and projects overview is accessible to all Organization users, we would have to accommodate both audiences (Organization Owner and Organization User). Should we rather adapt the group and project overview pages to offer more of this kind of information, as is the case in the Admin Area today, so that we have one unified view? Or should Organization Owners have several options where they want to go?
Answer: Option to visit manage is only available to organization owners