WordPress.com

Ownership and availability#

You own the WordPress.com site. Obelo manages the OAuth application and stores the granted token server-side.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

CMS publishing requires an active Starter Pro plan or higher.

Before you connect#

• A WordPress.com account that can publish to the target site
• A completed Obelo company profile and brand voice
• An Obelo workspace owner or admin must authorize the connection

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Sign in to the WordPress.com account that owns or administers the site
3. Authorize Obelo when WordPress.com shows the access request
4. Return to Obelo; the selected site is verified before publishing is enabled

If you need a new resource#

1. Create a WordPress.com site and choose its public address
2. Add the site administrator who will connect it to Obelo
3. Publish or prepare the categories and media library Obelo should use

Permissions to check#

• Obelo needs permission to create and update posts and upload media
• The authorization screen is hosted by WordPress.com; do not paste your password into Obelo

Verify and troubleshoot#

After the site is ready, return here and check again before starting OAuth.

No eligible WordPress.com site was returned. Confirm the signed-in account can administer a WordPress.com or Jetpack-connected site, then try again.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.