Projects and partners

Identify site and network authority in a WordPress handoff

Confirm the installation type, identify the exact change and administrative surface, and record who is authorized to act there. A site Administrator label does not establish network authority. WordPress's network administration menu checks manage_network and separate capabilities for network sites, users, themes, plugins, and options. Use those distinctions to locate the responsible owner; the menu code is not an exhaustive permission model for every action. A WooCommerce status report can help identify the installation, but it cannot authorize the handoff.

For: A research-only merchant or authorized project owner handing WordPress administration work to a store maintainer or network operator.

Updated 2026-10-01

Discuss my store project

Identify the installation before assigning the task

Use a current WooCommerce system status report to record the WordPress address, site address, and whether multisite is enabled. Add the report date and relevant WordPress, WooCommerce, and plugin versions. These facts locate the store that the handoff concerns and reduce the chance of assigning work against the wrong installation.

The report also lists active plugins, theme information, template overrides, and assigned store pages. Use those entries to identify the component or checkout page named in the requested change. Treat the report as a snapshot: a later configuration change can make it stale, and the report does not prove who currently has authority.

If multisite status or the target site cannot be established, leave administrative scope unresolved. Obtain that installation fact before describing the work as a single-site change or a network change.

Read the task more precisely than the role label

WordPress's role documentation describes a single-site Administrator as having administration capabilities that include plugins, themes, options, and users. An Editor's default content capabilities differ. Those single-site descriptions are useful context, but they do not turn a site's administrator into the person responsible for a network.

The official wp_admin_bar_my_sites_menu function gates the Network Admin menu with manage_network and checks distinct capabilities for its sites, users, themes, plugins, and options links. This demonstrates that network management has separate capability checks. It does not establish every permission needed to perform the operation behind each link.

Write the requested operation in full: the component, the intended change, the administrative surface where it belongs, and the sites known to be affected. Avoid a vague instruction such as granting admin access to fix checkout. A broad instruction leaves both the required authority and the extent of the change unspecified.

Match technical control to the authorized owner

Record the store administrator and, where a network exists, the network owner or authorized operator separately. They may be the same person, but the handoff should establish that from the real ownership and access arrangements. A business title, a contractor relationship, or possession of a site login does not by itself answer who controls the relevant network action.

Have the current authorized operator confirm the route for the named task. Record the applicable administrative scope and any required approval from the owner responsible for that scope. Technical permission and authorization to make this particular change are separate facts; both belong in the handoff.

If a task reaches a network-controlled component, identify the affected sites with the network operator before work is authorized. Do not assume that a store-specific request has a store-only effect. Conversely, multisite being enabled does not make every content edit a network task. The actual component and operation decide which scope needs confirmation.

Resolve a missing route without bypassing the boundary

When the assigned person cannot reach the required administrative surface, record the unavailable action and ask the responsible owner to confirm the authorized route. A missing menu is a useful observation, but it is not enough to diagnose every role or capability rule in that installation.

Do not solve an ownership gap by sharing an owner's password, changing capability checks, or silently expanding the work to the whole network. The handoff is ready when the target installation, specific operation, authorized actor, approving owner, and affected scope are recorded. If the network owner is unknown, keep that dependency open rather than marking the task ready.

For a Prism checkout-review consultation, send the public website, the research-only product context, the installation type if known, and the requested change in ordinary language. Keep status reports containing private information and account access details out of the public form. Prism will confirm the scope, responsibilities, fees, and terms of requested assistance; a consultation does not itself authorize network administration or determine processing eligibility.

Administration scope map

Use this for one actual administration task. Record site and network ownership separately, even when one person holds both. Complete the last column from the installation and its authorization records. An unknown owner or unconfirmed route remains a handoff dependency, not a reason to bypass permissions.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Administration scope map. The last column is for temporary notes.
Scope factRecord to inspectWhat the handoff must distinguishYour confirmed scope
Installation typeDated WooCommerce status report showing site addresses and multisite state.The specific store and installation; do not infer multisite status from the public site's appearance.
Store administratorCurrent site access record and the merchant's authorization for this work.A person who administers the site versus a person authorized for the particular requested change.
Network owner if presentNetwork ownership or operating agreement and confirmation from its authorized operator.Control of the network versus a role on one site. Record not applicable only when single-site scope is confirmed.
Requested changeWritten task naming the component, operation, target site, and intended result.A content or site setting change versus work on a network-controlled component.
Administrative surface and capability scopeAuthorized operator's confirmation of the route for the exact operation.Separate network sites, users, themes, plugins, and options checks; menu visibility is not an exhaustive permission test.
Affected sites and approverConfirmed scope from the owner of the component being changed.Who can approve the full effect of the change, including other sites if actually affected.
Authorized routeNamed actor, approving owner, and agreed handoff route.Whether the task can proceed within its scope or remains blocked by unresolved ownership or access.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.

Limits

  • WordPress single-site role descriptions do not establish network authority. Installed versions and the actual access configuration must be identified.
  • The cited menu function demonstrates separate capability checks; it is not an exhaustive list of action permissions or a bypass procedure.
  • Do not put passwords, API secrets, private account links, or customer records in the worksheet or consultation form.

Related guides

Sources

  • WooCommerce system status report — checked 2026-09-21. The report records site addresses, multisite status, WordPress and WooCommerce versions, plugins, theme and template information, and assigned store pages. These identify the installation, not authorization for a change.
  • WordPress roles and capabilities — checked 2026-09-21. Default single-site Administrator and Editor roles differ in their administration and content capabilities; the Administrator description covers plugins, themes, options, and users on a single site.
  • WordPress network administration menu capabilities — checked 2026-09-29. The function gates network-admin menu links using manage_network and distinct network sites, users, themes, plugins, and options capabilities. This supports distinguishing site and network control, not an exhaustive permission model.
  • Prism solutions — checked 2026-09-21. Public support includes storefront review, card-processing preparation, and help with a provider's website questions. Scope, fees, and terms are discussed before work; the provider decides eligibility and account terms.
  • Prism contact — checked 2026-09-21. The inquiry asks for the website, products, and question, excluding payment card details, passwords, and customer records. Follow-up is by email; a request is not an appointment, purchase, or processing application.

Discuss my store project

Planning, moving or taking over a store?

Discuss my store projectAll resources