Notification settings and reminder enrollment

Use Settings > Notifications > Reminder enrollment to manage reminder delivery for the account and browser or installed app you are using. Enrollment does not create scheduled work or grant access to a Guide or person.

Understand the page

The page separates Browser reminders from Packaged mobile reminders. The latter also contains supported desktop local enrollment, despite its mobile labels. Browser and installed-app delivery are separate choices.

Field	What it tells you
Web push, Native push, Mobile local	Whether the corresponding delivery service is available.
Browser permission, Native permission	Whether this browser or app has notification permission.
This browser, This device	Whether a matching active enrollment exists for this account here.
Active browsers, Active mobile	Active registrations across the account, not confirmation that this device can receive an alert.
Last delivery issue	A recent delivery problem for the account; it may concern another enrolled destination.

Permission and enrollment are different. Granted does not register the account by itself, and Enrolled does not prove current permission or successful receipt. Native permission combines available native capabilities; it does not prove that both push and local delivery are allowed.

Enable or stop delivery

1. Choose browser setup or mobile and desktop setup.
2. Use Enable or Enable mobile and answer the permission prompt.
3. Check the permission and This browser or This device result.
4. After changing permissions outside CareMap, select Check setup again.

Revoke removes the current browser enrollment. Revoke mobile removes the current installed-app destination. These actions do not revoke every other device. Already scheduled local alerts need separate care; see the device guide. There is no account-wide list of editable notification categories on this page.

Interpret delivery readiness

• Provider ready: the delivery service is configured, but device permission, active enrollment, and current content access still matter.
• Mock ready: simulated delivery is configured. It does not prove a real push was sent; local device scheduling is checked separately.
• Disabled, Missing config, or Missing public key: the corresponding service is unavailable or incomplete. Contact your administrator or support; repeated permission prompts will not fix that service state.
• Checking: wait for loading to finish. If it fails, Try again reloads setup information; repeat the intended action afterward if needed.

Use Home or Schedule to find the work itself. A delivery status is not proof that someone read a reminder or completed its work. See notification troubleshooting for recovery.