A notification setting labelled “Product updates” might cover release notes, research invitations, promotions, service announcements, or all four. A toggle labelled “Email” might disable one campaign stream while invoices and security alerts continue. When the interface hides those boundaries, users cannot make an informed choice and support teams cannot explain what happened.
CopyDoc can export Figma text for structured review, find repeated or inconsistent terms, and sync approved content back into designs. The audit must still reconcile those words with subscription systems, channel permissions, legal requirements, and actual sending behaviour.
Build a notification taxonomy
Inventory every message category across email, push, SMS, in-app inbox, browser notification, and any collaboration channels. For each category, record:
- user purpose and triggering event;
- transactional, operational, marketing, or mixed classification;
- available channels;
- default state and source of consent;
- frequency or digest options;
- whether the user can disable it;
- account, workspace, project, or device scope;
- sending system and preference key;
- policy or regulatory owner.
Do not let internal campaign names become customer labels. “Lifecycle nurture 03” explains the sender’s workflow, not the value or content the recipient should expect.
Describe the consequence of each choice
Export the preference-center strings with CopyDoc and group them by category, channel, scope, and action. A good setting name identifies the subject; its description explains examples, frequency, and important exclusions.
Compare:
Updates
with:
Weekly product tips and feature announcements by email
The second option gives the user a topic, cadence, and channel. Keep labels short enough to scan, but do not remove the distinctions that make consent meaningful.
Separate preferences that solve different problems. Topic asks “what is this about?” Channel asks “where will it arrive?” Frequency asks “how often?” Scope asks “for which account or project?” One overloaded toggle rarely communicates all four.
This differs from a push notification and in-app message review. That workflow improves the messages themselves; a preference-center audit governs the promises about which messages will be sent and how choices are stored.
Make mandatory messages explicit without sounding evasive
Some account, billing, security, or legal notices may continue after a user disables optional communication. Name those categories clearly and explain why they cannot be turned off while the account remains active. Do not hide them inside an “unsubscribe from all” exception footnote.
Review whether a supposedly mandatory category is truly necessary. Product convenience is not automatically a legal or operational requirement. When policy owners approve an exception, the UI copy should describe its scope in plain language rather than claiming that every “service” message is essential.
For marketing choices, check that the interface, email footer, onboarding consent, and account settings use the same category names. “News and offers” in one place should not become “Product communication” somewhere else.
Design the complete state set
Audit Figma frames for more than the default preference list:
- first visit with inherited defaults;
- all optional notifications enabled;
- all optional notifications disabled;
- mixed topics and channels;
- workspace-level setting controlled by an admin;
- browser or operating-system permission blocked;
- SMS number missing or unverified;
- save in progress, success, and failure;
- preference loaded from another device;
- account with multiple organisations;
- unsubscribe link with an expired or invalid token.
The interface should distinguish a product preference from a device permission. Turning on browser notifications inside the product cannot override a browser-level block. Tell the user where to recover without blaming them for a setting the product cannot change.
Reconcile copy with the underlying model
Create a review sheet with stable string IDs, Figma frame, preference key, current copy, proposed copy, classification, scope, owner, and approval status. Ask engineering or marketing operations to trace each visible control to the real stored value and sending systems.
Test combinations rather than isolated toggles. A master email switch may disable child topics, leave them selected but dormant, or permanently clear them. The copy and visual state need to reflect the implemented behaviour. If saving takes time across systems, confirm the change without promising instant suppression that cannot be guaranteed.
The permission and role copy audit has a useful model for authority and scope. Notification preferences require a related but distinct review of consent, channel capability, category boundaries, and downstream senders.
Re-import and test realistic language
After product, legal, support, and operational owners approve the wording, re-import it with CopyDoc and inspect every state. Test longer translated strings, screen-reader order, toggle labels, group headings, helper text, save feedback, and small mobile widths.
Before release, verify:
- every category has one stable customer-facing name;
- channel, frequency, and scope are visible where relevant;
- mandatory messages are narrowly and honestly described;
- device permissions are not confused with product preferences;
- unsubscribe and account settings use matching language;
- success and failure states explain what was saved;
- support documentation uses the same taxonomy;
- test sends respect every supported combination.
CopyDoc makes a broad terminology audit and controlled update practical. It cannot determine whether a message is legally required or whether a downstream campaign ignores the preference. The safest preference center joins clear language to verified sending behaviour, so a user’s choice means the same thing everywhere it appears.
Read as Markdown Related resource index Site index for AI agents
Pro Bundle