Planner settings applied org-wide versus per profile
Key Takeaway
A profile with its own saved Planner Settings uses them instead of the org default. You can't delete a profile's Planner Settings in the UI, so to make those users match the org default, update the profile's settings so each value equals the org default value.
Planner Settings in the Admin Console control how the Life Sciences Customer Engagement Calendar behaves, including calendar display, account search, business hours, routines, and event indicator colors. You can apply one configuration to every profile in the org ("Org Default") and give specific profiles their own configuration ("Profile"). A consultant uses the two levels to set a single baseline and then tailor the calendar for particular user groups.
Org Default and Profile levels
Like several other Admin Console configurations, Planner Settings use a hierarchical framework with two levels. The org default is the baseline configuration that applies to all users unless a profile-level configuration overrides it. A profile-level configuration applies to users assigned to that profile and takes precedence over the org default, so it works as an exception for one group.
If a user's profile has its own Planner Settings configuration...
The profile-level configuration applies to the user instead of the org default. The Life Sciences Cloud mobile app uses the profile-level configuration for that user.
If a user's profile has no profile-level configuration...
The org default applies to the user.
Your org default sets "Work Day Start Time" to 8:00 AM. A hospital account team starts its day at 7:00 AM. You set "Apply Settings To" to Profile and select that team's profile. You copy the org default values, change Work Day Start Time to 7:00 AM, and save. Users assigned to that profile now get the profile-level configuration with the 7:00 AM start, including in the Life Sciences Cloud mobile app. Users on profiles without their own configuration keep the 8:00 AM org default.