WPCentrify documentation
How to connect sites, set update and backup policies, control access, brand the client experience and drive everything programmatically. Written for the person doing the work, not the person buying.
First hour
Connecting a portfolio and getting a first health check back.
Connecting your sites
Install the connector, authenticate with a scoped key, and run a first inventory across the portfolio.
Start hereMigrating from another tool
Bulk connector deployment, what transfers, and how to run in parallel with your current platform.
Migration guidesThe portfolio dashboard
How work is ranked by consequence and turned into assigned items.
Read morePolicies and workflows
Set these once at the portfolio level rather than per site.
Update policies and rollback
Risk thresholds, approval requirements, staged rollout and automatic rollback behaviour.
Configure updatesBackup and restore policies
Frequency, retention, storage location and scheduled restore testing.
Configure backupsAutomation rules
Schedules, triggers and conditions that turn routine maintenance into policy.
Configure automationTeams, clients and your brand
Team and client permissions
Site-scoped and action-scoped roles, client portal access, and revoking access in one step.
Read moreWhite-label setup
Brand assets, your own portal domain, sending domain and connector plugin renaming.
Set up white-labelClient reports
Templates, scheduling, approval before sending, and engagement tracking.
Configure reportsAPI and integrations
REST API and webhooks
Authentication, endpoints, rate limits and event payloads for driving WPCentrify from your own systems.
API referenceIntegrations
Slack, Teams, email, Discord and workflow automation platforms.
See integrationsStatus and incidents
Current service status, incident history and how we communicate during one.
Service statusDocumentation during early access
WPCentrify is in early access, and this documentation reflects that: the sections above link to detailed capability pages, and the deeper reference material is being written alongside the product rather than after it.
If something you need is not documented yet, ask us directly. During early access you have a shared channel with the engineers rather than a ticket queue, and the answer usually becomes the documentation.
The changelog records what has shipped and the roadmap records what is coming, both with dates. Neither is marketing copy, and both are the fastest way to check whether a capability exists today.
Something not documented?
Ask us directly. During early access your question usually becomes the next page of documentation.
Free during early access. No credit card required.