Manage WordPress Across an Account

Use the WordPress inventory that matches the scope of the work:

• Open All Organizations → Core, Plugins, or Themes when the same task spans Organizations you can access.
• Open Account → Operations → Bulk Management when every target belongs to one Account.
• Open the Website-scoped WordPress pages when a task needs inspection or a decision specific to one Website.

Work across Organizations

The All Organizations inventories combine eligible WordPress Websites without changing your active Organization. Use search, Organization, client, label, Website type, update, vulnerability, and refresh filters to narrow the rows. Sort the table or change the visible columns when you need to compare versions and status.

Core lists each Website directly. Themes groups matching installations by theme; expand a theme to review its Websites and current versions. The Theme Catalog can install a public or Organization-specific custom theme on eligible targets. Custom themes stay confined to their Organization even when another Organization has a theme with the same stylesheet name.

Before a Core or Theme operation starts, TMXIO previews the accepted and excluded targets. Review that preview before confirming. Read-only or otherwise unavailable Websites can remain visible for context, but TMXIO excludes them from changes. The operation panel then tracks the combined job across Organizations.

Work within one Account

1. Choose Core, Plugins, Themes, or Database.
2. Filter the inventory until the intended Websites are the only visible targets.
3. Select the targets and review exclusions or unavailable rows.
4. Start the operation once.
5. Keep the operation panel open until every target reaches a terminal result.
6. Retry only failed targets. Do not start a second portfolio-wide operation to recover a partial failure.

The summary and target rows answer different questions. The summary describes the operation as a whole; each target row records what happened for one Website. A successful subset remains successful when another target fails.

Before a broad update

• Confirm a current restore point exists for every Website that supports backups.
• Read the upstream release notes for breaking changes.
• Separate security updates from optional feature updates when rollback risk differs.
• Schedule customer-visible work for an approved change window.

If the operation stops changing, capture the operation identifier and affected targets, then open a support request. Repeated clicks can create competing work and make diagnosis harder.