Add organization navigation
Proposal
Introduce an organizational switcher to navigation.
Scope of changes
- Add an organizational switcher to the Left sidebar
- Update breadcrumbs to include organizations
- Adding Organization to
Search or go to...
modal
Important context
- Organizations are isolated from each other by default meaning content available will be scoped to a single organization at a time. This includes issue counts, merge requests, todo's, and available groups/projects.
- User exists across organizations and can be a "user" in one or many organizations
- Additional details available https://docs.gitlab.com/ee/architecture/blueprints/organization/
Organization switching details
- A user clicking on the switcher button opens a dropdown
- Dropdown to be implemented leveraging a combobox UI element
- In the dropdown, the user is presented with:
- A section indicating their current organization
- Clicking on the current organization item takes the user to the organization's "front page"
- A section listing available organizations
- List is populated based on organizations the user is considered a "user" in. Organization user details
- Clicking on an item from the "Switch organization" section will change the context to that organization, mark that item as current, and close the dropdown.
- If switching is performed on a page that exists across organizations, the user will remain on that page with the content scoped to the selected organization
- Your work
- Explore
- Search
- User profile
- If switching is performed on a page that does NOT exist across organizations, the user will be taken to the organization's "front page".
- Projects
- Groups
- Admin
- User settings
- Organization
- If switching is performed on a page that exists across organizations, the user will remain on that page with the content scoped to the selected organization
- A section indicating their current organization
Page contexts
Breadcrumb changes
Include organizations as the first item of the breadcrumb on all applicable pages.
Search or go to... modal addition
Clicking the option will take the user to the organization "front page"
Business drivers
https://docs.gitlab.com/ee/architecture/blueprints/organization/#motivation
The Organization focuses on creating a better experience for Organizations to manage their GitLab experience. By introducing Organizations and Cells we can improve the reliability, performance and availability of our SaaS Platforms.
Supporting research/data
- Pods Architecture Sentiment Research
- Problem & Solution Validation: Organizations Research
- Estimate cross-organizational users
Other locations that were considered
Inline with "Search or go to..." button
Option details
As context only when needed
Option details
Second sidebar
Option details
Previous designs prior to "Search or go to..." button
#396717 (closed)
Design files
Checklist
-
Review the handbook page for navigation changes -
Add relevant information to the issue description detailing your proposal, including usage and business drivers. -
List at least two other places you considered to introduce your feature -
Add relevant designs to the Design Management area of the issue -
Ensure your UI suggestion align with the Documentation Style Guide -
Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing. -
Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring. -
Engage the Foundations Product Manager for approval. The Foundations DRI ( @cdybenko) will work with UX partners in product design, research, and technical writing, as applicable. -
Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your item will live in more than one place. -
Ensure engineers are familiar with the implementation steps for navigation.
Edited by Mike Nichols