Projects
Create a project, configure it, and know what deleting one actually does.
A project is one website or application. It owns a project key, a widget configuration, its own inbox, and its own environments.
Creating one
Click New project from the dashboard home and give it a name. That's the whole form — everything else is configured afterwards.
Every project starts with:
- A project key (
pj_...) - A Production environment, which can't be deleted
- Default widget appearance
- Analytics and Live chat off
The Free plan allows 2 projects per workspace. Paid plans are unlimited.
Naming and identity
Under Settings → Configuration you'll find the project key — the public identifier that goes in your script tag. It isn't a secret credential: what actually protects a project is the environment allowlist, which rejects the widget on any hostname you haven't authorised.
Projects also carry a square mark colour and, optionally, a custom logo, which is how you tell six of them apart in the sidebar at a glance.
Visitor audience
Also under Settings → Configuration, and more consequential than it looks:
| Audience | Effect |
|---|---|
| Unknown | Safest defaults. No visitor-facing AI |
| Business users aged 18+ | Visitor-facing AI is permitted |
| General public / mixed | No visitor-facing AI |
| Likely accessed by people under 18 | No visitor-facing AI |
This gates the live chat AI agent and transcription of visitor-submitted media. It's fail-closed by design — the model provider's terms prohibit services likely to reach under-18s. Team-facing AI is unaffected.
Features
Settings → Features carries three switches:
| Switch | Effect |
|---|---|
| Analytics (Pro) | Adds the Analytics section; still needs visitor consent to collect |
| Live chat (Pro) | Adds the Messages tab and the Live chat inbox |
| Show widget in production | Makes the widget visible on production hosts |
The first two add a section to the project's sidebar when enabled.
One project or several?
One project per site. Two sites that need separate inboxes are two projects, because the inbox, labels, issue types, automations, and appearance are all per-project.
Not one project per environment. Staging and production belong to the same project as separate environments — that's the whole point of environments, and it keeps one project key covering everything.
Deleting a project
Settings → Danger zone. Deletion removes the project and its feedback permanently and is not undoable. Owners and admins only.
If the goal is just to stop collecting, remove the script tag or delete the project's non-production environments instead — the widget stops loading and the data stays.