Feature Request: Pre-Desktop User-Context Execution Phase / Delay Desktop Until Login Policies Complete #6

New Issue

michael · 2026-01-19T18:31:13Z

michael commented

2026-01-19 18:31:13 +00:00

Originally created by @trandall50 on GitHub.

Summary
With the transition to ADE + Jamf Setup Manager, there is currently no supported mechanism to execute user-context actions before the desktop is presented on first login. This creates a visible UX gap during initial sign-in that was previously achievable through depNotify

Problem
Jamf Setup Manager intentionally operates outside of a reliable user context, which is appropriate for device-level actions. In environments where preserving user choice is important, configuration profiles that enforce user-level settings are not always desirable. As a result, common provisioning tasks such as Dock configuration, wallpaper, and user preferences must be deferred to login-triggered policies.

Because login policies execute after the desktop is already visible, users briefly see a default or partially configured environment before final configuration completes.

Requested Capabilities
We would like to request one of the following supported options:

Option 1
Post-Login Execution Phase
Provide a supported post-user-creation / post-sign-in execution phase that:

Runs after the user account exists and the user is fully signed in
Supports user-context-dependent actions
Executes before the desktop is shown (or while it is hidden)

Option 2
Hide Desktop Until First-Login Policies Complete
Provide a supported mechanism to hide or delay the desktop until all first-login-triggered policies have completed.

This would allow existing login policies to remain unchanged while ensuring users are not exposed to an incomplete UI.

Thank you

Originally created by @trandall50 on GitHub. Summary With the transition to ADE + Jamf Setup Manager, there is currently no supported mechanism to execute user-context actions before the desktop is presented on first login. This creates a visible UX gap during initial sign-in that was previously achievable through depNotify Problem Jamf Setup Manager intentionally operates outside of a reliable user context, which is appropriate for device-level actions. In environments where preserving user choice is important, configuration profiles that enforce user-level settings are not always desirable. As a result, common provisioning tasks such as Dock configuration, wallpaper, and user preferences must be deferred to login-triggered policies. Because login policies execute after the desktop is already visible, users briefly see a default or partially configured environment before final configuration completes. Requested Capabilities We would like to request one of the following supported options: Option 1 Post-Login Execution Phase Provide a supported post-user-creation / post-sign-in execution phase that: - Runs after the user account exists and the user is fully signed in - Supports user-context-dependent actions - Executes before the desktop is shown (or while it is hidden) Option 2 Hide Desktop Until First-Login Policies Complete Provide a supported mechanism to hide or delay the desktop until all first-login-triggered policies have completed. This would allow existing login policies to remain unchanged while ensuring users are not exposed to an incomplete UI. Thank you

michael added the enhancement label 2026-01-19 18:31:13 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#6