An administrator publishes a new Next Experience theme carrying the corporate colours and sets it as the instance default. Accounts created this week load the new colours, while several long serving users report that their sessions still render in the previous colours even after signing out and back in. What explains the difference?
- AThose users have already selected a theme for themselves, and a theme chosen by the user takes precedence over the theme set as the instance default. Correct
- BThe instance default theme is read only when an account is first created, so established accounts keep whichever theme was current on the day they were provisioned.
- CThe theme was published without being marked active, so it renders only for accounts that have no stored preference of any kind against them yet.
- DThe browser cache on the established accounts is holding the previous stylesheet, and the corporate colours appear once that cached copy expires by itself.
Why A is correct: Correct because the personal theme choice is stored as that user's preference and the instance default is only the fallback used when no personal selection exists on the account.
Why B is wrong: Tempting because it fits the pattern of new accounts behaving differently, but the default is read at each session for any user who has not chosen a theme, so it is not stamped onto an account at creation.
Why C is wrong: Tempting because an inactive record genuinely stops many platform features working, but an inactive theme would not load for the new accounts either, which contradicts the reported behaviour.
Why D is wrong: Tempting because stale cached assets do cause styling oddities, but a cache would not survive signing out and back in for some users while never affecting the newer accounts at all.