Cloud.gov Platform admins and some users are members of multiple organizations. It's essential that users are always aware of what org they are currently working within and making changes to. Most users are members of only one organization, and do not need to swap, but should still be certain of their organization's identity.
About orgs
Each organization has a guid and single string name (immutable) defined at org creation in a hyphenated-slug-format. (There isn't a prettier human-friendly org name but they're reliably understandable/recognizable like "cloud-gov"). Users do not have the choice to join or leave an organization, delete an organization, or edit the organization name. Users should generally not be in "no" org (unless there's an application error) -- all cloud.gov users should be members of at least one organization. (while this isn't true for pages users, who have different orgs, we don't need to accommodate that now)
Proposed steps
[ ] Review research and understand different states/constraints based on API
[ ] Create mockups representing each state of the interaction
[ ] Iterate on mockups based on feedback from team
[ ] Collaborate with engineers for technical feasibility of proposed designs
[ ] Attach final mockups displaying each state with annotations
Ensure this issue has a clear Definition of Done in the Acceptance Criteria list below:
Acceptance Criteria
The proposed design accommodates the following:
[ ] A user in multiple orgs can swap between orgs in the UI
[ ] A user in a single org is not prompted to swap between orgs
[ ] The current org is always clearly visible for all users
[ ] Handoff to engineering is complete (create a new issue)
jduss4
commented
1 month ago
Background:
Cloud.gov Platform admins and some users are members of multiple organizations. It's essential that users are always aware of what org they are currently working within and making changes to. Most users are members of only one organization, and do not need to swap, but should still be certain of their organization's identity.
About orgs
Each organization has a guid and single string name (immutable) defined at org creation in a hyphenated-slug-format. (There isn't a prettier human-friendly org name but they're reliably understandable/recognizable like "cloud-gov"). Users do not have the choice to join or leave an organization, delete an organization, or edit the organization name. Users should generally not be in "no" org (unless there's an application error) -- all cloud.gov users should be members of at least one organization. (while this isn't true for pages users, who have different orgs, we don't need to accommodate that now)
Proposed steps
Ensure this issue has a clear Definition of Done in the Acceptance Criteria list below:
Acceptance Criteria
The proposed design accommodates the following: