Plugin Security & Approvals

Designate SiteWatch security approvers explicitly in Plugin Review → Accounts & Permissions → Security decision authority. The first designation uses the current WordPress password and a fresh code from an enrolled Authenticator; changing approvers, the approval policy, trusted sources or imported references always asks for a fresh code again.

Until an approver is designated, plugin installations and updates made from WordPress accounts wait in Pending Reviews, because no account can yet grant the permission they need. From SiteWatch 2.0.1, SiteWatch opens on its Security Setup step until an approver exists.

An eligible primary approver can verify the current session. A session that signed in with Authenticator records its own proof; an older session can be verified once with Verify this session. That verified session supports routine eligible package work without asking for a fresh code for every ordinary operation, including clean commercial ZIPs that have no public reference; uncertain packages still require deliberate review.

Other eligible administrators can request scoped, revocable permission for up to 24 hours under 24-hour plugin permissions. The grant remains bound to its account, network, operation, policy and session context and does not add WordPress capabilities. Expiry or revocation ends that authority.

Supported update inspection preserves the current installation when the replacement attempt is rejected. Eligible channel updates still receive inspection and target/content verification.

Supported activation paths check the installed content again. New installations and existing-update activation state follow the documented operation, rather than assuming every approved ZIP should immediately activate.

When an approver approves a held activation, or permits activation while approving an installation, the approval covers the reasons shown for those exact files and the plugin can then be activated. Changed files, a new reason or an approver who no longer holds approval authority start a new review.

Plugin package review covers plugins. Theme installations and activations follow WordPress's own permission and nonce checks; theme files remain in scope for File Integrity and File Changes.

Direct hosting writes and arbitrary custom installers are outside universal interception by these WordPress hooks.

Review unresolved package attempts in Pending Reviews. Exact-package decisions are content-, target- and operation-bound, with the documented one-use time limit and context checks.

Each held request explains why it needs review:

• the WordPress session still needs Authenticator verification;
• the account needs permission from a designated security approver;
• supported suspicious code patterns were found;
• package files differ from the available same-version reference;
• the download does not match the plugin's trusted update channel;
• installed files differ from the previous package decision.

A changed package cannot inherit the earlier decision simply by keeping its name. Review the new content and operation.

Removing a review request clears the supported pending decision and hides that request; it does not uninstall the plugin or erase retained audit/source information.