Not-permitted screen: add button to open profile menu / org switcher
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- authentication, frontend
Research direction
Start at the code for the not-permitted screen and the profile menu or organization switcher entry point. Check how the screen handles permission errors and whether it can open the menu programmatically; the issue leaves that interaction and when to show the hint unresolved. Done when the generic hint appears as agreed and its button opens the profile menu with the org switcher.
Written by the indexing model from the issue text.
Description
Problem
Authors logged into the wrong Adobe org or account (e.g. their CC org instead of the org AEM is provisioned on) land on the “Not Authorised” screen with no hint why or how to fix it. For one customer this generates tens of support tickets every week.
A project-level banner isn’t possible, so this needs a generic fix in the product.
Proposal
Add a short hint to the not-permitted screen that the user may be in the wrong Adobe org or logged in with the wrong account, plus a button that opens the profile menu with the org switcher.
Acceptance criteria
- Not-permitted screen shows the wrong-org/account hint
- Button opens the profile menu with the org switcher
- Generic copy, no project config needed
Open questions
- Can the profile menu be opened programmatically from the screen?
- Show the hint for all permission errors, or only when the user has multiple orgs?
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 74
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/da-live
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
customer-feedback ew
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ew
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug ew
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/monaco-editor#5563 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
account: profile bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/cozy-client#1777 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day