People named on an incoming lead are invited to your workspace, not added to it

When a lead arrives through your inbound webhook, the email address on it decides who the lead belongs to. If that address already had a Sustentus account, the person behind it used to be added to your workspace outright — no invitation, nothing to accept, and quite possibly no idea it had happened.

They are now sent an invitation instead, and they join your workspace only by accepting it. The lead is created either way and behaves exactly as it did before: it starts as pending, and the customer shows as inactive until they sign in. An address that has no Sustentus account is unaffected — an account is created for it and added to your workspace as before.

What this means when you read a lead

A customer on a new lead is not necessarily someone who can see your workspace yet. If they were invited, they are reachable by email — that is where the invitation went — but they are not a member until they accept, and nothing you do in the workspace will reach them before then.

If you send leads from your own system

The reply to a successful post now carries a customerAdmission field, so your system can tell the two apart rather than assuming every accepted lead means a contact who is already inside your workspace. It answers one of joined, invited, already-member, or not-provisioned, and the inbound lead webhook reference in the developer documentation explains each. Existing integrations keep working — the field is added, nothing was removed or renamed.