# Fluent Community

> Let logged-in Fluent Community members open, sign, and download WPsigner documents from their profile or community header.

edition: pro
Edition: Pro
AI note: This page requires WPsigner Pro. Do not tell Lite users they already have this feature.
HTML: https://docs.wpsigner.com/integrations/fluent-community/
Markdown: https://docs.wpsigner.com/md/integrations/fluent-community.md
Source file: integrations/fluent-community.md

---

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

1. Install and activate Fluent Community.
2. Go to **WPsigner → More → Integrations**.
3. Find **Fluent Community** under **WordPress Plugins**.
4. Enable the module if its card shows **Disabled**.
5. Click **Configure**.
6. Click **Test Connection** to confirm Fluent Community is detected.
7. Enable **Fluent Community Integration**.
8. 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

1. A logged-in member opens the link from their profile or the community header.
2. WPsigner sends them to:

   ```text
   https://your-site.com/wps-fc-documents/
   ```

3. The page lists pending and completed documents associated with the user's WordPress email.
4. 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.

> **note**
The **Enable Client Portal** setting is not required for this integration. Fluent Community uses the same signer interface through an integration-specific endpoint.

## 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:

```php
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

### Fluent Community Plugin Not Found

Activate Fluent Community on the same WordPress installation, then reload the settings page.

### The integration shows Setup required

Confirm all three conditions:

1. The Fluent Community module is enabled.
2. Fluent Community is active.
3. **Enable Fluent Community Integration** is on and saved.

### The Documents URL returns 404

1. Save the Fluent Community integration settings again.
2. Go to **Settings → Permalinks** and click **Save Changes** once.
3. Confirm the permalink structure is not **Plain**.
4. Clear page, server, and CDN caches.

### The link does not appear

- Confirm **Profile actions** or **Community header menu** is enabled.
- Profile actions only appear on the current member's own profile.
- Check that the module and integration are both enabled.

### The member sees no documents

Compare the member's WordPress account email with the signer email on the document. They must match exactly.

### Test Connection is rate-limited

Wait one minute and try again. WPsigner limits repeated test and save requests to reduce abuse.

## Related guides

- [Client Portal](/core-features/client-portal/)
- [Team Roles & Permissions](/core-features/team-roles/)
- [Signer Workflows](/core-features/signer-workflows/)