Choose WordPress site
The customer chooses the WordPress site and content workflow they want to prepare or publish through.
Platform guidance
WordPress workflow guidance
Publishing workflows depend on authenticated account access, configured permissions, and platform/API availability.
Overview
What this page covers
This page gives customers and platform reviewers a public summary of how Braineek describes WordPress workflows. It is not an internal setup guide and does not expose private app configuration, callback URLs, secrets, tokens, or backend implementation details.
Requirements
Account and permission requirements
- Supported account type
- Authenticated WordPress site user with configured publishing permissions.
- Permission and approval caution
- WordPress REST API behavior depends on authenticated access, site configuration, and user permissions.
- User control
- The customer controls which WordPress site and authenticated user are connected to the workflow.
Authorization flow
How WordPress authorization works
Authorize site access
The customer authenticates or configures access using the supported WordPress site connection method.
Confirm user role
The customer confirms the connected user has the required role for draft, scheduled, or published post behavior.
Use granted access
Braineek can prepare content and use post workflows only within the authenticated site permissions.
Disconnect access
The customer can remove access through Braineek support paths and WordPress site controls.
Customer checks
Before authorizing Braineek
- Confirm the WordPress site and user role before connecting a publishing workflow.
- Review whether draft, scheduled, or published status is appropriate for the team.
- Keep editorial review inside the team workflow before publishing.
Use cases
Supported workflow direction
- Blog draft preparation
- Post metadata planning
- Editorial review workflows
Implementation boundary
Public guidance, not internal configuration
Site and user scope
WordPress workflows depend on authenticated access to the target site and the permissions assigned to the connected user.
REST API basis
Official WordPress REST API documentation describes post fields and status behavior for post workflows. Public copy should remain sensitive to site configuration and user role.
Publishing availability caution
Braineek can support draft preparation, metadata planning, and editorial workflows only where the site configuration and authenticated user permissions allow.
Trust links
Disconnection, deletion, and policy pages
Customers should be able to disconnect connected accounts and request data deletion through Braineek support and the platform-specific controls available in their connected account.
WordPress questions
Customer-facing WordPress questions.
What controls WordPress publishing availability?
WordPress workflows depend on authenticated access, configured user permissions, and the available REST API behavior for the site.
Next step
Plan WordPress workflows with clear permissions
Discuss account eligibility, permissions, and review expectations before planning connected platform workflows.