Summer release: one label system across every app

In our Winter release, Plauti introduced a new brand and started updating labels across its apps. The Summer release continues that work: every label you see inside your org now uses one consistent naming system, built around what a screen, field, or automation does rather than which product it used to belong to.

What's changing in this release?

This release updates the visual labels across every app in your org — component names, object names, field labels, permission sets, custom settings, and flow actions — so they match Plauti's current branding.

This update is visual only. No API names, field references, or other technical identifiers change behind the scenes. Your existing configurations, automations, and integrations keep working exactly as they do today.

Why is Plauti relabeling everything?

Consistent labels mean less guessing. As Plauti adds capabilities across Monitor, Clean, Prevent, and Act, matching labels help you find the right screen or field without needing to know which product it used to come from.

Do you need to do anything?

No action is required. Every change applies automatically, and none of it affects how your automations, integrations, or configurations run.

Plauti's support pages list every renamed label, organized by app, if you want to check the exact new name before your team runs into it in the UI. If a rebranded label is hard to find, Plauti's support team can help you locate it.

If you're mapping out how Monitor, Clean, Prevent, and Act fit your CRM data strategy, this is a good moment to take stock of where your org's data quality stands today.