Docs · How to

How to: rename NIBWP for your clients

Change the plugin name, description, author and menu label so it fits your agency, without breaking updates or the connection.

Renaming lets you present NIBWP under your own name on a client site: the plugin name, its description, the author, the links and the admin menu label. It is a display change, and it is careful to be only a display change.

The reason that distinction matters is that renaming a plugin naively breaks it. WordPress identifies a plugin by its header, update checks compare against it, and cron, CLI and REST all read it. Change the header everywhere and updates stop arriving, which is a worse outcome than the wrong name in a menu.

TL;DR

Set the name, description, author, links and menu label under User Access. The new name shows in the admin; the real identity is withheld from update checks, cron, CLI and REST, so updates keep working.

A display name, not a fork

The rename is deliberately shallow, and that is what makes it safe:

  • Updates keep working — Update checks see the real plugin, so new versions still arrive.
  • Cron is unaffected — Scheduled tasks read the true identity, not the label.
  • CLI and REST unaffected — Anything programmatic sees the plugin as it really is.
  • Admin reflects your brand — Name, description, author, links and menu label all follow what you set.
  • Per site — Each install carries its own name, so one client never sees another.
  • Reversible — Clear the fields and the original name returns.

What you can change

Five things, all cosmetic:

Plugin name

What appears in the Plugins list and at the top of the admin screens.

Description

The line underneath it in the Plugins list.

Author and links

Who it is by, and where the support and site links point.

Menu label

What the admin menu item is called, which is what people actually see daily.

How it stays safe

  • Display only — The rename never reaches the plugin header that WordPress identifies it by.
  • Withheld where it matters — Update checks, cron, CLI and REST are given the real identity deliberately.
  • No file edits — Nothing is written into the plugin folder, so an update cannot overwrite your branding.
  • License unaffected — Your license is tied to the real plugin, not to the name you show.

Getting started

  • Open User Access — In WordPress, go to NIBWP and open User Access, where the branding fields live.
  • Set the name and label — The menu label is the one people see most, so start there.
  • Check the Plugins list — Confirm the new name and description appear as you intended.
  • Confirm updates still work — Look for the update check on the Plugins screen. It should behave exactly as before.
Do not rename the folder or the headerEditing the plugin header or renaming its directory is what breaks updates and licensing. This feature exists so you never have to, and an update would overwrite those edits anyway.

FAQ

Will my client see the NIBWP name anywhere?
Not in the admin surfaces the rename covers. Internal identifiers keep the real name because updates depend on them.
Does renaming affect my license?
No. The license is tied to the real plugin, not to the displayed name.
Will an update revert my branding?
No. Branding is stored as settings, not as file edits, so updates leave it alone.
Can I set it per site?
Yes. It is per install, so every client can carry a different name.

Make it yours

Put your name on it without breaking anything underneath.

Security and scopes

Connect your first agent.

Follow the quickstart, or book a demo and we'll walk you through it.