Skip to content

Notices

The announcements you write in WordPress, shown to the members who use your app.

PluginUltimate Member - Notices
Endpoint groupNotices
PlanEvery plan

Notices has two surfaces, and the zone you drop it into decides which one you get.

  1. Drag Notices into the Background zone for the ambient banner. It sits above the bottom bar on every screen, and the navigation stays usable underneath it.
  2. Drag Notices onto a navigation bar or into the side drawer for the list screen — every notice aimed at the member, including the ones they have already closed.

Place it in both zones to get both. They share one set of settings.

SettingWhat it doesDefault
Title, DescriptionShown at the top of the list screenEmpty
Banner positionWhich end of the screen the banner sits atBottom
Notices in the bannerHow many to stack at once, 1–31
Use each notice’s own coloursDraw a notice in the colours it was given in WordPressOn
Show the iconDraw an icon on notices that have oneOn
The button dismisses the noticeTapping a notice’s button also marks it readOn
Keep notices they have readList dismissed notices, dimmedOn
Notices per pageHow many the list loads at a time, 1–5020
RestrictionsWhich roles see the tabEveryone

Under Appearance you also get the notice card — border, corners, padding and margin — and the title and body typography. The card is used by the banner and by each row of the list, so a notice looks the same wherever it appears.

Your website decides the rest. Who a notice reaches, what it says and what colours it carries are set per notice under Ultimate Member → Notices, and the app follows them.

The notices screen, with the ones already read kept at the bottom
The notices screen, with the ones already read kept at the bottom
A notice as a banner, with the screen underneath it still usable

Two of the extension’s own settings behave differently in an app, because they describe a website.

Page rules are ignored. The allowed-URL lists and the home, posts and pages switches describe addresses an app does not have, so every notice aimed at a member reaches them wherever they are.

Show in footer still counts. A notice with it turned off is one you placed on a single page with a shortcode, so the app lists it on the Notices screen but never raises it as a banner.

Dismissing works in both directions. A notice closed in the app is closed on your website too, because it is written to the same list your site’s own close button writes to. Only the Flush action on the notice itself clears that list.

Signed-out readers see the notices you target at logged-out visitors. Their dismissals are remembered on the device rather than on your site, since there is no account to record them against.

SymptomCauseFix
The screen is empty or shows an errorThe Notices group is offMemberside → REST API — switch it on. See Enable the endpoints you need
The card is greyed outUM - Notices is inactiveActivate it
The banner never appearsEvery notice is dismissed, or none is set to show in the footerCheck the notice under Ultimate Member → Notices, and use Flush to clear who has read it
A notice looks plain in the appIt has a text colour but no background colourSet both, or neither — a light text colour on the app’s own background would be unreadable
Both a banner and the completion gate are showingProfile completion covers the app until it is finishedExpected. The gate comes first; the banner is there when they get past it