=== Enrove Creative ===
Contributors: studioen
Tags: project management, client portal, creative brief, deliverables, agency
Requires at least: 6.3
Tested up to: 7.1
Requires PHP: 8.1
Stable tag: 0.5.2
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Run creative projects from brief to sign-off, with a tracker your client opens with a link, their email and a password of their own.

== Description ==

Enrove Creative is for freelancers and small agencies. You create a project from a brief template, manage its deliverables in the WordPress admin, and share a tracker page with your client.

**Projects and briefs**

* A three-step wizard creates the client, the brief and the project together.
* Reusable brief templates with short answer, paragraph, rich text, dropdown, checkbox, date and number fields. Files are shared as links. A template can be duplicated as a starting point for a new one.
* Projects can be saved as drafts and finished later.
* A finished or paused project can be archived: it becomes read-only and its tracker closes, and unarchiving it opens the same link again. Nothing is deleted.
* Import clients from a CSV file exported from a spreadsheet, address book or CRM, merging a client whose email address is already in use into that client's record, or skipping them. Administrators can export the clients they tick in the list to a CSV file.
* The Projects list shows as a timeline or a list. Under Screen Options each user chooses the columns of the list, the number of days the timeline shows and the number of projects per page. The Clients and Templates lists have their columns and page size there too.

**Deliverables**

* Each deliverable has a title, a status, a thread of updates and its own list of links (a design file, a staging site, a shared folder), which the client sees on the tracker.
* Messages are written as in a chat, with bold, italic, code, lists and links, by your team and by the client on the tracker; web addresses become links.
* An update can be sent at once or queued and sent with others as one batch. The client sees a queued update, and the status it sets, only when the batch is sent. A new deliverable, and a change to a deliverable's title, type or scope, wait for the batch too.
* Project status moves from Discovery to In Progress to Complete as deliverables change.

**Client tracker**

* The client opens a private link and signs in with their email address and a password only they know, which they create the first time with an invitation code from you. Recovery codes let them reset it themselves. They do not need a WordPress account, and no email is sent.
* They read the brief, see every deliverable with its latest update and links, approve a deliverable or ask for a revision with a note, and leave messages.
* Under Sign-in and security they change their password, make new recovery codes and see every sign-in and every change to their access, including a new invitation you send them, marked when they did not ask for it.
* The page refreshes itself while it is open.

**Dashboard**

* Active projects, deliverables waiting on a revision and client totals.
* A status chart, a 14-day activity chart and a feed of recent activity.

**Slack notifications (optional)**

* Internal alerts to your own channel, and project updates to a channel you share with a client.
* The opening lines of a project update are editable in Settings.

The plugin itself sends nothing anywhere until you add a Slack bot token. See "External services" below.

**AI assistants (optional, off by default, WordPress 6.9 or later)**

* An administrator turns it on under Settings → AI assistants. Then, with an MCP server plugin installed, an assistant such as Claude or ChatGPT can list your projects and what waits on you, read a project's deliverables and threads, look up clients, and draft updates.
* An assistant's update is always queued: nothing reaches the client until someone on your team sends it from Review & send.

**Privacy tools**

* Your clients' data is included in the WordPress tools under Tools → Export Personal Data and Tools → Erase Personal Data.
* Settings → Data can download a copy of everything held about one client and then erase it, or reset the plugin to how it was when first installed.

== Installation ==

1. Install the plugin from the Plugins screen, or upload the `enrove-creative` folder to `/wp-content/plugins/`.
2. Activate it.
3. Open **Enrove Creative → Settings** and enter your agency name and logo.
4. Open **Templates** to review the brief templates, then **Projects → New Project**.

The client's tracker link is `/project/{token}/` under your site's address, so it works when WordPress is installed in a subdirectory. The plugin adds its rewrite rules when you activate it and restores them itself if they go missing; on plain permalinks the link takes the form `/?enrocr_tracker={token}`.

To use Slack, create a Slack app in your workspace with the `chat:write` scope, install it, and paste its bot token into **Settings**. You can define the token as the `ENROCR_SLACK_BOT_TOKEN` constant in `wp-config.php` instead, which keeps it out of the database.

== Frequently Asked Questions ==

= Do my clients need a WordPress account? =

No. They open the tracker link you send them and, the first time, enter their email address and the invitation code shown to Administrators on the project screen, then create their own password. If they forget it they use a recovery code, or ask you for a new invitation.

= Which WordPress users can use it? =

Administrators and Editors. Projects, clients, briefs and templates are shared by everyone with access, so the plugin's screens are closed to Authors, Contributors and Subscribers. Only Administrators can change the settings. Under Enrove Creative → Settings → Permissions they choose what Editors can do: use the plugin at all, delete projects, deliverables, clients and templates, and import clients. By default Editors cannot delete projects or clients. Moving a client to the Trash archives their projects, and restoring the client reopens them. Deleting a client for good keeps their projects without what the client wrote or answered, so when they have projects it takes the right to delete projects as well.

= Where is the data stored? =

In your WordPress database, as private post types and post meta. Nothing is stored on any other server.

= What happens to the data when I delete the plugin? =

Deactivating keeps everything. Deleting the plugin from the Plugins screen removes its projects, clients, briefs, templates, deliverables and settings.

= A client asked for a copy of their data, or to be forgotten. What do I do? =

Use the WordPress tools: Tools → Export Personal Data and Tools → Erase Personal Data, with the email address on the client's record. The export holds their client record, their briefs with their earlier answers, their projects, the messages they left on the tracker, and their tracker sign-ins and the dates their password and recovery codes changed. Erasing deletes the client record with its briefs, its projects and their deliverables, for good and without the trash. You can also erase a client directly from Enrove Creative → Settings → Data, after downloading a copy of their records, projects and deliverables there as an HTML file. Messages already posted to Slack are not removed: delete those in Slack.

= How do I start over? =

Enrove Creative → Settings → Data has a Reset plugin tool for Administrators. It deletes every project, client, brief, template and setting the plugin stored on the site and adds the default templates again. It cannot be undone.

= Can I use Claude, ChatGPT or another AI assistant with it? =

Yes, on WordPress 6.9 or later, once an administrator turns it on under Enrove Creative → Settings → AI assistants; it is off by default. It is experimental: use it with caution. The plugin then registers abilities with WordPress's Abilities API; it does not run an MCP server itself. Install an MCP server plugin, such as the MCP Adapter from the WordPress project, and connect your assistant to it as a WordPress user: Claude Desktop and coding tools through a config file and an Application Password, or Claude and ChatGPT with a link, through a server plugin that offers connectors (OAuth). Enrove Creative → Settings → AI assistants has the steps. The assistant can list projects, read a project with its deliverables and threads, list clients, and queue an update on a deliverable, which waits in Review & send until someone on your team sends it. It can do only what its user can do in the plugin, and never sees an invitation code, password, tracker link or phone number; it sees clients' email addresses only when its user is an Administrator. The project screen marks each update an assistant wrote, in the thread and in Review & send. Give the assistant its own Editor account rather than an Administrator's, and keep the server to the abilities you mean to give: abilities or tools for any post or post meta, which some server plugins add, would let an Administrator's assistant read the plugin's records directly (client names, contact details and messages). An invitation code is stored encrypted, so they do not return it in a usable form. What the assistant reads goes to its provider.

= Does the plugin work without Slack? =

Yes. Slack is optional and is the only notification channel at present. Without a bot token the plugin itself makes no outside requests.

== Screenshots ==

1. The dashboard: active projects, deliverables waiting on a revision, a status chart and recent activity across every project.
2. A project's deliverables, with their status, the client and the client's private tracker link. Review & send holds updates until you send them.
3. A deliverable's thread: your team's updates and the client's replies, revision requests and approval.
4. The client's tracker, opened with a link, their email and their own password: each deliverable with its latest update.
5. Settings → Permissions: choose what Editors can do in the plugin.

== External services ==

This plugin can connect to Slack to post notifications about your projects. It is optional and off until an administrator saves a Slack bot token in Enrove Creative → Settings (or defines `ENROCR_SLACK_BOT_TOKEN`).

* When, to your agency channel: when a client approves a deliverable, asks for a revision or leaves a message on the tracker; when someone on your team records a client's approval or revision request; when a new tracker invitation is asked for from the tracker's sign-in screen; and when an administrator presses the test button in Settings.
* When, to a client's channel (set on the client record, with a copy to your agency channel): when someone on your team sends a project update.
* When, to a client's channel only, as a receipt: when the client approves a deliverable or asks for a revision on the tracker, or someone on your team records either on their behalf; when their tracker password is set, changed or reset, or they make new recovery codes; when an administrator sends them a new invitation; when a new invitation is asked for in their name; and when one of their project trackers closes (the project was archived or moved to the trash) or opens again, a minute later, unless the change was undone within that minute.
* Who makes the request: your site's server, to `https://slack.com/api/chat.postMessage`. A visitor's or client's browser never contacts Slack.
* What is sent: your bot token (to authenticate), the ID of the channel you configured, and the message text. Depending on the message, the text contains the client's name, the project name, deliverable names and statuses, the message the client or your team wrote (with any links in it), your agency or site name, the display name of the team member who recorded a client's response for them, for a request for a new invitation the browser and system it came from (for example "Chrome on macOS"), and a link: to the project in your WordPress admin for agency messages, or the client's private tracker link for client messages (a project update's copy to your agency channel is the same text, so it carries the tracker link too). As with any request WordPress makes, your site's address is included in the request's User-Agent header.
* Service provider: Slack Technologies, LLC, a Salesforce company (https://slack.com)
* Terms of use: https://slack.com/terms-of-service/user and https://slack.com/terms-of-service/api
* Privacy policy: https://slack.com/trust/privacy/privacy-policy

The plugin contacts no other host. Scripts, styles and fonts are bundled with it. It has no analytics and no usage tracking.

== Privacy ==

The plugin stores what you enter about your clients (name, email address, phone number, company, Slack channel and the brief for each project) and what they write on the tracker (approvals, revision requests and messages). For each project it keeps the date and time of the last 10 tracker sign-ins with the browser and system they came from (for example "Chrome on macOS"), shown to the client on the tracker. It does not record IP addresses. A client's tracker password and recovery codes are stored hashed, as WordPress stores its users' passwords, and the dates of changes to them (and of new invitations) are kept and shown to the client. When a client signs in to a tracker, the plugin sets a cookie that keeps them signed in for 24 hours, or until they sign out, and counts failed sign-in attempts for that client for 30 minutes to block guessing of passwords and codes.

If you connect an AI assistant through an MCP server plugin, what it reads (client names, and their email addresses when its user is an Administrator; project and deliverable names; and messages) goes to that assistant's provider. The plugin itself sends nothing to it.

Your team members' data is also kept: the plugin saves the user ID of the WordPress user with the records they work on (who sent an update, recorded a client's response, sent an invitation or changed a brief, and which records they created), and their view settings as user meta (dashboard layout, items per page, timeline view, hidden columns). The display name of a team member who records a client's response for them is shown to your team and sent to Slack.

This data is registered with the WordPress personal data tools, so it can be exported or erased by email address under Tools, and the plugin adds suggested wording to Settings → Privacy → Policy Guide. Erasing a client deletes their record, briefs, projects and deliverables permanently. Erasing a team member (found by the email address of their WordPress account) deletes their settings and replaces their user ID in the records with 0; the records stay, because they are also your history and your clients'. Neither can remove messages already posted to Slack or copies in your database backups.

== Source code and build ==

The client tracker in `build/` is compiled with Vite from the React source in `src/`, which is included in this plugin together with `package.json`, `package-lock.json` and `vite.config.js`. To rebuild it with Node.js 18, 20 or 22 and later: `npm ci && npm run build`, which installs the exact versions in `package-lock.json`. The tracker uses the React and the translation functions (`wp.i18n`) that WordPress includes (the `react`, `react-dom` and `wp-i18n` scripts); no copy of either is bundled. The build keeps function and variable names and the shape of the code (it removes only whitespace), so the translation tools can read each `__()` and `_n()` call in `build/assets/`.

Bundled third-party code, with licences and sources, is listed in `assets/vendor/README.md`:

* D3 7.9.2, ISC licence, https://github.com/d3/d3 (the unminified `d3.js` is included)
* Gridstack 14.0.0, MIT licence, https://github.com/gridstack/gridstack.js/tree/v14.0.0 (`gridstack-all.js` is the release's own bundle from npm, unmodified but for its source-map comment, as no map ships; its TypeScript and SCSS source is included in `assets/vendor/gridstack/src/`)
* Material Symbols icon font, Apache License 2.0, https://github.com/google/material-design-icons (Apache 2.0 is compatible with GPLv3, so the font combines with this plugin under "GPLv2 or later")
* Syne and DM Sans fonts, SIL Open Font License 1.1 (licence files for all three fonts are in `assets/vendor/fonts/`)

== Changelog ==

= 0.5.2 =
* Initial release.
