TEAMWORK
Review client sites without centralizing recordings.
Bring authorised site health summaries together while recordings stay on each site.
In this guide 5 sections
Connect a remote site
#Connections use HTTPS and do not follow redirects with credentials. Use the final canonical site address. Application passwords are encrypted on the central server using its WordPress salts.
- Install and activate compatible ClickClue Free and Pro packages on the remote HTTPS site.
- Create a dedicated ClickClue reviewer account there. Generate a WordPress application password in that user’s profile.
- On your central site, open Workspace → Your sites → Connect another WordPress site.
- Enter the remote site address, reviewer username and application password. Select Connect site.
Understand the overview
#The overview includes the local site and up to 25 remote connections. It reports capture state, retained recording counts, issue counts and other summary information. Remote summaries may be cached for five minutes.
Open WordPress takes you to that site’s workspace. Each site keeps its own recordings, access controls, sampling and storage settings. The overview does not pool storage or increase a single site’s capacity.
- Download client report exports a CSV of site summaries with their observation time.
- It does not export recording payloads, customer identities or a branded PDF.
- Review the report’s site names and contents before sending it to a client.
End a connection
#Disconnect removes the saved connection from the central workspace. Revoke its application password at the remote WordPress account when access should end completely. A changed site address, password, certificate or security rule may require reconnecting.
Save and export an investigation report
#Investigations saves filter recipes combining clues, journeys and feedback. Report totals and exports share their retained population and coverage. Reopening a report reloads live eligible evidence instead of preserving hidden copies of removed recordings.
CSV and JSON exports require the appropriate administrative access. Keep exported files private; the plugin cannot recall files already downloaded. Connected-site summaries remain aggregate health overviews rather than a central store of remote recordings.
Separate the overview from the evidence
#| Review task | Where it happens |
|---|---|
| Check capture state and retained counts across authorised sites | Connected-site health overview; summaries can be cached. |
| Inspect the replay behind a client’s question | That client site’s own WordPress workspace, with its access controls. |
| Share aggregate site summaries | Review the client CSV before sending through your own approved channel. |
| Keep a repeatable investigation | Save the report/filter scope; retained evidence is reloaded when opened. |
Connected sites do not pool storage or form a central replay library. Exported files need their own access and retention decisions.
See a WordPress agency review example or compare site licence coverage.