-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
[Epic] Admin-specific customizations #11111
Comments
We definitely need a spec for this. One fairly extreme idea I had was to introduce an
I'm down for a more clever solution, but it seems like users want a completely customizable experience between their elevated prompt and non-elevated prompt. So might as well enable that experience? Especially since loading a different JSON would be trivial. |
idea
Then just screw it with the appearance config on the existing profile - just have two different profiles. this has been thoughts with Luca, who has kept me up since 3am |
written and maintained by @carlos-zamora & @zadjii-msft
For quite some time now, we've gotten requests for admin-specific customizations. The first being to have an "appearance config" for an elevated session. However, we stopped working on that when we hit the following problem: how do we determine which appearance config to choose when a user is in an elevated session and also has an unfocused appearance config?
Over time, we've gotten more requests with similar situations (not necessarily limited to appearance config). This epic tracks these requests:
zadjii-msft notes:
Nexus of weird
elevate:true
bugs:User stories
profile.defaults
block when running elevatedappearance
when running elevatedtheme
when running elevatedOpen questions
{container}DefaultProfile
? (like UWP? this is an intentionally dumb example)elevatedTheme
,elevatedDefaultProfile
,profiles.elevatedDefaults
ORadmin-settings.json
globals
block for elevated settings, ala Add per-window-name global settings #9992?Other Admin QoL issues
The text was updated successfully, but these errors were encountered: