Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Banner in GE to alert users of Migration #3049

Open
jessicaaawu opened this issue Mar 12, 2024 · 0 comments · May be fixed by #3009
Open

Create Banner in GE to alert users of Migration #3049

jessicaaawu opened this issue Mar 12, 2024 · 0 comments · May be fixed by #3009
Assignees

Comments

@jessicaaawu
Copy link

jessicaaawu commented Mar 12, 2024

Problem:
In April (exact date TBD), GE will migrate to Torus tenant and get a new app ID. All users, who wish to use GE as a logged in user, will need to 1) Re-login and 2) Re-consent to GE to access the users data.
This will cause a disruption for the user experience for GE and we need to widely communicate this to our users ahead of time.

Solution
A banner to be created within GE to alert them of: 1) the migration initiative, 2) the most important change/ action they will need to take (Reconsent) and 3) a link to learn more.

Feature spec
image

  1. Placement: Place it by the top right side of GE so its visible and by the login
  2. Background color: Yellow (to alert users, but not red which will make it look alarming)
  3. Dimensions of banner: should follow other existing banners in GE
  4. Have icon to signal an "alert" (announcement) --> have an exclamation mark in a circle (Elinor said this is possible with the Fluent UI)
  5. Bold text Announcement:
  6. Text: Announcement: On April 14th, all users will need to re-login to Graph Explorer and reconsent to permissions. Learn more about impacts of GE migration here.
  7. Hyperlink and underline here to the public blog. (link will be supplied later)

Additional context
Text within the banner subjected to change. Link to blog will be supplied at a later date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants