Fluent Community

The Fluent Community integration adds a Documents to sign link to each member’s own profile and, optionally, the community header. The link opens WPsigner’s signer portal and shows documents matched to the member’s WordPress account email.

Requirements

WPsigner 3.1.2+
WordPress 5.8+
PHP 7.4+
Fluent Community installed and active on the same WordPress site
Pretty permalinks (any structure except Plain) recommended

No external API key is required. The integration uses local WordPress and Fluent Community hooks.

Configure the integration

Install and activate Fluent Community.
Go to WPsigner → More → Integrations.
Find Fluent Community under WordPress Plugins.
Enable the module if its card shows Disabled.
Click Configure.
Click Test Connection to confirm Fluent Community is detected.
Enable Fluent Community Integration.
Choose where the link should appear, then click Save Settings.

Settings

Setting	Default	Purpose
Enable Fluent Community Integration	Off	Activates profile/header links and the documents endpoint
Custom name	`Documents to sign`	Changes the member-facing link label; maximum 80 characters
Profile actions	On	Adds the link to the logged-in member’s own profile
Community header menu	Off	Adds the link to the Fluent Community top header

Use a distinct label so members do not confuse signing documents with Fluent Community’s file library.

Member experience

A logged-in member opens the link from their profile or the community header.
WPsigner sends them to:
```
https://your-site.com/wps-fc-documents/
```
The page lists pending and completed documents associated with the user’s WordPress email.
The member can open a pending signing link or download completed documents.

The endpoint uses the site’s WordPress theme rather than rendering inside Fluent Community’s application shell.

How document matching works

WPsigner compares the logged-in user’s WordPress email with the signer email saved on each document. A member sees no documents when those addresses differ.

The profile action appears only on the member’s own Fluent Community profile. It is intentionally omitted when they view another member’s profile.

Permissions and security

Members must be logged in; logged-out visitors are redirected to WordPress login and returned afterward.
Any WordPress role can use the member endpoint.
The profile link is restricted to the profile owner.
WPsigner nonces protect portal actions.
Settings and connection tests require a WordPress Administrator.
The documents page sends noindex, nofollow, X-Frame-Options: SAMEORIGIN, and X-Content-Type-Options: nosniff headers.

Customize the documents URL

Developers can replace the default endpoint URL:

add_filter( 'wps_fluent_community_documents_url', function ( $url ) {
  return home_url( '/my-signing-documents/' );
} );

The replacement page must render a compatible signer experience; changing the URL alone does not add the portal shortcode.

Troubleshooting