Engage Workspace

Engage is the CRM half of Leed: the businesses your site has identified, the people inside them, the scores Leed computes over both, the personas and campaigns you plan against them, and the tracked links that bring them in. It is not six screens. It is one screen with six sections behind a picker, and every one of them lives at a URL you can copy and send to someone else.

Getting to Engage

Engage is the third tab in the left rail, between Design and Plan. Selecting it takes you to /engage, which immediately rewrites itself to /engage/accounts — Accounts is the default section. Type a section name Leed does not recognize and the same thing happens, so /engage/nonsense lands you on Accounts rather than on an error.

Reaching Engage at all needs the contact:read privilege, which every role from Read Only upward carries. Reaching Engage is not the same as being able to change anything in it: editing a contact or an account needs contact:write, which starts at Content Publisher. The full grid is in the privilege matrix, and someone can be given contact access without being given it workspace-wide — see resource-level access overrides.

Engage is one of six rail tabs; the rest of the shell is described in Touring the Workspace.

The three zones

Every section renders into the same frame:

• A resizable left panel — a search box, the section picker, and the active section’s list.
• A floating header over a center card — the selected item’s mark, name and chips on the left, its actions and Recompute scores on the right. There is no rule or bar between the header and the card; the two flow together, and the header is completely empty until you select something.
• A collapsible right facet rail — a stack of panels the active section declares for itself.

Why the URL is the state

The section and the selected item are both path segments: /engage/<section>/<id>. Nothing about which contact you were reading is held in browser memory. That has three consequences worth relying on.

Browser back and forward move between the things you looked at, not between screens. Every view is a link — paste /engage/contacts/4182 into a message and the recipient opens exactly that person. And a create form is a real page, not a modal that vanishes when the tab reloads.

flowchart TD
  A["/engage"] -->|normalize| B["/engage/accounts"]
  U["/engage/{unrecognised}"] -->|normalize| B
  B --> C{"Section in the URL"}
  C --> D["/engage/{section}"]
  D -->|"Accounts, Contacts, Contact Filters, Shortcodes"| E["auto-select the first row"]
  D -->|"Personas, Campaigns"| F["center card shows a prompt"]
  E --> G["/engage/{section}/{id}<br/>header + center card + facet rail all change"]
  D --> H["/engage/{section}/new<br/>center card becomes the create form"]
  D --> I["/engage/contacts/import<br/>center card becomes the CSV importer"]

The six sections

The picker sits at the top of the left panel. Opening it shows all six sections with an icon, a label and a one-line blurb.

Accounts, Contacts, Contact Filters and Personas carry no entitlement gate at all — they work on Free exactly as they work on Enterprise. The two that are gated say so on their own pages:

Sections that auto-select land you straight on a record, which is why Accounts opens with an account already showing. Personas and Campaigns instead open with a prompt in the center card — “Select a persona, or create one to segment your audience” and “Select a campaign, or draft one to start engaging your audience” — because in both cases an empty workspace is the normal starting condition and a forced selection would hide the create button behind a record you did not ask for.

The left panel in detail

Search is placeholder’d per section — Search accounts…, Search contacts…, Search personas… — and it searches different things in each. On Accounts it matches the account name and its industry, and nothing else. On Contacts it is a server-backed, debounced search over name, email and title. On Contact Filters it filters the names of the saved views and groups themselves, not the contacts inside them.

Filter & view (the sliders icon) opens one of two menus. Most sections get the simple one: Section default, Sort by name, and a readiness sort labeled Sort by readiness on Accounts and Contacts and Sort by signal on Personas, Campaigns and Shortcodes. Picking a sort applies its natural direction — names ascending, readiness highest first — and picking the same key again reverses it, with a ↑ or ↓ shown beside the active row. An option whose backing data is missing from the current rows is shown grayed rather than silently doing nothing. Shortcodes gets the richer Group by / Sort by menu instead, because a short-link list is worth grouping by UTM source or by on-site versus external.

Contact Filters hides the sort menu entirely. Its groups are fixed categories in a deliberate order, and re-sorting them would only scramble that.

+ appears only on the sections that can create something — Contacts, Contact Filters, Personas, Campaigns and Shortcodes — and only when you have the privilege to create it. Accounts has no + at any permission level, because accounts are never created by hand.

Import CSV appears on Contacts alone, beside the +, and opens the contact importer.

The divider between the panel and the center card drags. The panel clamps between 240 and 520 pixels, starts at 320, and remembers the width you left it at in this browser.

Reserved URLs

Two slugs are reserved and never collide with a real record id:

Both are ordinary pages. Bookmark /engage/contacts/new if adding people by hand is a routine part of your week.

The header and Recompute scores

On the left of the header sit the selected item’s mark, its name, and a row of chips — an account’s industry and headcount, a contact’s title, opt-out marker, committee role and journey stage. Any per-section actions sit to the right of them.

At the far right is Recompute scores, styled as an AI action and shown only to people carrying ai:write, which starts at Content Writer. It is the only write this header performs, and it is worth being precise about its scope: it recomputes every contact and every account in the workspace, not the record you happen to be looking at. While it runs the button reads Recomputing… and is disabled. What it actually recalculates — readiness, fit, intent, journey stage, committee role, persona match — is described in Engage scores.

Note the shape of that gate: it is a permission question, not a billing one. Scores compute on every plan; the button is simply hidden from Read Only users.

The right facet rail

Each section declares its own facets. Collapsed, the rail is a 40-pixel column of icons, some carrying a count badge; selecting an icon expands the panel beside it, and selecting the same icon again closes it.

What your plan gates, and what that looks like

Below Growth, the Campaigns and Shortcodes rows stay in the picker. Selecting either gives you a left panel that reads “Campaigns are available on the Growth plan.” or “Short URL tracking is available on the Growth plan.” and a center card holding an upgrade prompt. Neither section fetches anything, so there is nothing to be slow and nothing to fail — the section is present and inert.

Below Starter, a different gate applies across the whole category. The readerIdentity feature covers per-person site history: the Site engagement block on a contact and on an account, and the Activity facet. Below Starter the server returns the profile with empty activity arrays and a flag, and the UI replaces those panels with an upgrade prompt rather than with a misleading “no activity yet”. The contact’s own profile stays fully readable — only the history goes.

Both gates behave the way When a feature is gated describes, and the authoritative minimum tier for every feature is on Feature availability by plan.

Where the people come from

Most contacts arrive from your published forms — a submission is what creates a contact in the first place, as How forms work explains. Bringing an existing list in is the CSV importer. Contacts can also arrive from an outside CRM, though only through one bespoke Salesforce webhook and never through a self-serve panel in this workspace; CRM integration says exactly what is and is not connected.

Account, contact, persona, readiness and journey stage are all Leed terms rather than generic marketing words, and the glossary defines each one as Leed uses it.