Title: Senvarel
Author: elghamdi
Published: <strong>November 12, 2026</strong>
Last modified: November 12, 2026

---

Search plugins

![](https://ps.w.org/senvarel/assets/icon-256x256.png?rev=3798674)

# Senvarel

 By [elghamdi](https://profiles.wordpress.org/elghamdi/)

[Download](https://downloads.wordpress.org/plugin/senvarel.1.4.2.zip)

 * [Details](https://wordpress.org/plugins/senvarel/#description)
 * [Reviews](https://wordpress.org/plugins/senvarel/#reviews)
 *  [Installation](https://wordpress.org/plugins/senvarel/#installation)
 * [Development](https://wordpress.org/plugins/senvarel/#developers)

 [Support](https://wordpress.org/support/plugin/senvarel/)

## Description

Senvarel connects a self-hosted WordPress website to the Senvarel service through
a verified and revocable pairing flow.

The connector can:

 * Verify the WordPress site, multisite blog and administrator permissions.
 * Synchronize authorized posts and pages with Senvarel.
 * Send signed content-change events to Senvarel.
 * Create and update WordPress drafts requested from Senvarel.
 * Publish an existing draft only after an explicit manual approval in Senvarel.
 * Revoke the connection locally or from Senvarel.

Connecting WordPress does not enable automatic publishing. This plugin does not 
contain an automatic publishing scheduler. Draft creation, draft updates and manual
publication remain separate operations with separate permission checks.

Senvarel is a hosted service. A Senvarel account and an OWNER or ADMIN role for 
the matching Senvarel site are required to complete pairing. The WordPress user 
who starts pairing must have the `manage_options` capability. Feature availability
in the service may depend on the customer’s Senvarel plan.

For service terms, see https://senvarel.com/terms. For the privacy policy, see https://
senvarel.com/privacy.

### External services and privacy

This plugin communicates with the Senvarel service at `https://senvarel.com`. It
does not contact Senvarel merely because the plugin files are installed. Communication
begins when an administrator explicitly starts pairing, and continues while the 
verified connection remains active.

During pairing, the plugin sends the WordPress home URL, site URL, REST URL, site
name, generated instance identifier, numeric WordPress user identifier, blog and
network identifiers, multisite status, WordPress/PHP/plugin versions and capability
booleans. It receives short-lived pairing data and dedicated signing credentials.

When synchronization is requested, the plugin can send authorized post or page identifiers,
status, title, excerpt, content, slug, timestamps, categories, author display name
and Senvarel provenance metadata. Private content and author information are included
only when the connected WordPress user has the corresponding permissions.

While connected, the plugin records local content-change events and delivers signed
event metadata to Senvarel. Draft creation, draft updates and manual publication
receive signed operation data from Senvarel. Requests include installation and binding
identifiers, timestamps, nonces and HMAC signatures.

Senvarel processes this data to provide the connector, synchronization, draft-management
and manually approved publication features requested by the customer. See https://
senvarel.com/privacy and https://senvarel.com/terms for the service’s policies.

## Installation

 1. Install the Senvarel plugin from the WordPress Plugin Directory when it becomes
    available, or upload an official ZIP supplied by Senvarel for an authorized test.
 2. Activate **Senvarel** for the intended site. On multisite, activate it for the 
    intended blog or network-activate it.
 3. Open **Settings > Senvarel** in the administration area of the exact blog to connect.
 4. Select **Connect Senvarel**. WordPress requests a short-lived pairing code from
    Senvarel.
 5. Open the verification link and confirm the matching organization, site, domain 
    and blog in Senvarel.
 6. Return to WordPress and select **Finalize verification**.
 7. Confirm that WordPress reports the connection as verified before starting a synchronization.

No WordPress password or manually copied API key is required by the official pairing
flow.

Upgrades from the historical token connector remove the local legacy token. The 
deprecated `geo-growth/v1/status` and `geo-growth/v1/publish` routes return a non-
mutating HTTP 410 response. Reconnect through the verified pairing flow; legacy 
credentials are never converted automatically.

## FAQ

### Does connecting WordPress enable automatic publishing?

No. Pairing verifies identity and permissions only. The plugin has no automatic 
publishing scheduler, and the official connection keeps automatic publishing disabled.

### Can Senvarel publish an article?

Senvarel can create and update drafts. An existing draft can become public only 
through the manual publication flow after an OWNER or ADMIN explicitly reviews and
confirms that operation in Senvarel. WordPress permissions are checked again immediately
before publication.

### Is my WordPress password sent to Senvarel?

No. The plugin never asks for or sends a WordPress password. Pairing exchanges dedicated
random signing credentials over HTTPS after confirmation on both sides.

### Which WordPress permissions are required?

manage_options is required to pair or revoke the connector. Read, draft and publish
operations additionally require the relevant WordPress capabilities for the connected
user and content type. If those capabilities are removed, the operation is rejected.

### Does the plugin support WordPress multisite?

Yes. Credentials and signed requests are scoped to the exact WordPress network and
blog. A request for a different blog is rejected.

### What happens when the plugin is deactivated?

The connector endpoints and event delivery stop. Connection credentials remain stored
so reactivation can restore the connection. Disconnect first if you want Senvarel
to revoke the remote installation.

### What happens when the plugin is deleted?

Uninstallation removes Senvarel credentials, pending pairing data, connector options,
replay nonces, scheduled events and the plugin’s custom journal tables from every
affected blog. WordPress posts and pages are not deleted. Because uninstall code
does not contact an external service, disconnect before deletion when possible so
the remote credential is revoked as well.

### Where are connection credentials stored?

Dedicated HMAC credentials are stored as non-autoloaded WordPress options in the
database of the connected blog. They are never displayed in the WordPress interface
or included in connector logs.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Senvarel” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ elghamdi ](https://profiles.wordpress.org/elghamdi/)

[Translate “Senvarel” into your language.](https://translate.wordpress.org/projects/wp-plugins/senvarel)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/senvarel/), check out
the [SVN repository](https://plugins.svn.wordpress.org/senvarel/), or subscribe 
to the [development log](https://plugins.trac.wordpress.org/log/senvarel/) by [RSS](https://plugins.trac.wordpress.org/log/senvarel/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.4.2

 * Internationalize the WordPress administration and connector error messages.
 * Bundle the French translation and the source translation catalogue.
 * Complete the final WordPress.org compatibility and packaging review.
 * Keep the legacy writer retired and automatic publishing disabled.

#### 1.4.1

 * Retire the historical bearer-token writer and remove its token controls.
 * Delete the historical token on upgrade without changing WordPress content.
 * Return a non-mutating HTTP 410 response from the deprecated legacy routes.
 * Require the verified pairing, scoped HMAC credentials and official operation 
   engine for every mutation.

#### 1.4.0

 * Add manually approved publication of an existing WordPress draft.
 * Recheck WordPress publication permissions, binding scope and remote version before
   mutation.
 * Reuse the durable operation journal for idempotency and reconciliation.
 * Keep automatic publishing disabled.

#### 1.3.0

 * Add signed, durable content-change events with retry and replay support.
 * Add idempotent draft creation, draft updates and remote-state reconciliation.
 * Preserve multisite blog isolation and reject writes after revocation.

#### 1.2.0

 * Add signed connector health and capability diagnostics.
 * Add initial and incremental synchronization for authorized articles and pages.
 * Bind signed requests to the paired WordPress network and blog.

#### 1.1.0

 * Add short-lived, double-confirmed Senvarel pairing.
 * Add signed identity verification and anti-replay protection.
 * Add capability reporting and bidirectional revocation.

#### 1.0.0

 * Initial connector with legacy token compatibility.

## Meta

 *  Version **1.4.2**
 *  Last updated **5 days ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 5.8 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [AI](https://wordpress.org/plugins/tags/ai/)[automation](https://wordpress.org/plugins/tags/automation/)
   [content](https://wordpress.org/plugins/tags/content/)[publishing](https://wordpress.org/plugins/tags/publishing/)
   [seo](https://wordpress.org/plugins/tags/seo/)
 *  [Advanced View](https://wordpress.org/plugins/senvarel/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/senvarel/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/senvarel/reviews/)

## Contributors

 *   [ elghamdi ](https://profiles.wordpress.org/elghamdi/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/senvarel/)