Docs

PluginShield basics

PluginShield is built around a simple flow: Organizations → Projects → Plugins → Reports. This page explains what each area does and how to get value fast.

Go to organizationsContact support
Organizations
Pick an org, create one, or switch org context.
Open
Projects
Projects group sites/environments. Open an org first.
Open
Reports
Export-friendly views for audits, clients, and stakeholders.
Open

Quickstart

  1. Go to Organizations and open the org you want to work in.
  2. Open Projects and pick the project/environment you’re reviewing (prod, staging, etc.).
  3. Use the Plugins table to search, filter, and spot outdated or drifting versions.
  4. Click a plugin to open the Plugin detail view for versions, lifecycle signals, and notes.

Core concepts

Organization

A customer/account boundary. Billing, users, and projects live here.

Project

A logical grouping of sites or environments (e.g. “ACME – prod”, “Client X – staging”).

Plugin inventory

The list of plugins and versions in a project. This is where you spot drift, outdated installs, and risk.

Reports

Export-friendly output for audits and client delivery: what’s installed, what’s behind, and where.

Daily workflows

1) Audit a project’s plugin posture
  • • Search for a plugin (by name or slug).
  • • Sort by “Updated” to find stale dependencies.
  • • Look for “Behind” / drift signals and prioritize production first.
2) Review a plugin in detail
  • • Open the plugin detail page for installed vs latest versions.
  • • Capture context in Notes (why it exists, owner, upgrade plan).
  • • Use lifecycle signals to decide whether it’s safe to keep.
3) Produce a client/audit-ready summary
  • • Use Reports to export what’s installed and what’s lagging.
  • • Include Notes for exceptions (“approved legacy plugin”, etc.).
  • • Re-run after remediation to show improvement over time.

Reports and exports

Reports are designed for audit workflows: clear inventory, version status, and easy sharing with stakeholders.

Inventory reportOutdated / behindVersion driftNotes / annotations
Go to Reports to see what’s available in your plan.

Roles and access

Access is scoped by organization. If you can’t see an org or project, it’s usually a membership/role issue.

Owners / Admins

Manage org settings, users, projects, and exports.

Members / Viewers

Review inventory and plugin posture. Some write/export actions may be restricted.

Troubleshooting

+I switched theme, but a page looks “stuck” in one mode.
That page is likely using hard-coded colors (e.g., bg-slate-950, text-white). Use semantic tokens instead: bg-background, text-foreground, bg-card,border-border, text-muted-foreground.
+I can’t see an organization or project.
You probably don’t have org membership or the right role. Ask an org owner/admin to add you or adjust permissions.
+My plugin list looks stale.
Use the Refresh button if available, then re-check. If it still looks off, capture the org + project name and email support.

FAQ

+What should I do first after signing up?
Create or open an organization, then create a project that represents your production environment. Start there.
+What is a “project” in PluginShield?
A project is a grouping boundary for reporting — usually an environment (prod/staging) or a client/brand.
+How do I report a bug or ask for a feature?
Use the Contact page. Include the page URL and what you expected vs what happened.
Want a tighter “how-to” doc for auditors/clients? Tell me your target audience (agency vs enterprise vs auditor), and I’ll tailor this page to match their workflow.