ClientCraft.uCRM 17.0.133

Client Craft uCRM

ClientCraft.uCRM brings CRM workflows into the Umbraco 17 backoffice.

It is designed for teams that want leads, contacts, accounts, deals, notes, tasks, attachments, and CRM dashboards inside Umbraco instead of maintaining a separate editor workflow.

What This Package Focuses On

• CRM workspaces inside the Umbraco backoffice
• Tenant-aware CRM connectivity through a tenant identifier and integration key
• Lead capture plumbing for Client Craft CRM integrations
• Activity history, notes, tasks, and attachments on CRM records

This release is focused on the backoffice CRM experience. Form and onboarding flows are still evolving and will be presented more fully in a later iteration.

Installation

dotnet add package ClientCraft.uCRM

After installing:

1. Restart the site.
2. An Umbraco administrator must open Users → User Groups, edit or create the group intended to use uCRM, and enable uCRM in its allowed sections. Save the group and assign only the intended users to it.
3. Enable that section for the administrator performing initial setup as well. Refresh the backoffice, or sign out and back in, if the section does not appear.
4. Open uCRM, create the workspace, and verify the owner's email. Save the credentials shown once in application configuration, then restart the site and check the connection.

Section access is a manual setup step. Installing or upgrading the package does not automatically enable uCRM for all administrators or create uCRM Users / uCRM Admins groups. You can use a dedicated group to keep the section available only to the selected users; ordinary CRM users do not need Umbraco Administrator membership.

The section permission makes the uCRM interface visible. CRM tenant membership and permissions determine which workspaces and data each user can access. Both are required when adding users after setup.

On Client Craft's hosted installation, Settings → Workspaces is reserved for Client Craft administrators. Enabled agencies with management permission see Client workspaces. Ordinary customers see only Workspace details, with ownership and subscription management shown read-only. People & access requires tenant administrator authority. A single accessible workspace is shown by name without a switching dropdown.

Client Craft is the API tenant whose existing IsDefault flag is true. The directory's legacy isDefault field identifies an installation owner; its additive isPlatformRoot field is a read-only projection of the database flag. These are distinct: an agency can own an installation without owning the platform. Deploy the updated API before the dependent package/website.

The API migration attaches only unparented, non-default tenants to the existing default tenant, preserving agency children and billing ownership. It rejects missing or ambiguous defaults in populated databases. The existing unique index prevents multiple defaults; database guards prevent removing, replacing or reparenting the established root and committing unparented customers. Application rollback retains these ownership repairs and guards.

Configuration

{
  "uCRM": {
    "tenantIdentifier": "YOUR-TENANT-GUID",
    "integrationKey": "YOUR-INTEGRATION-KEY",
    "tenantName": "YOUR TENANT NAME"
  }
}

Website Bootstrap

Add this once near the end of the main site layout, before </body>:

@await Html.PartialAsync("~/Views/Partials/ucrm/client-bootstrap.cshtml")

This single bootstrap line resolves the tenant, sends first-party analytics page views, and loads storefront scripts only when the current site has a uCRM commerce root. Tenant roots with both tenant fields empty inherit the appsettings tenant.

Popup Forms

Render one uCRM Form Block in the layout or page area and select a popup Marketing Form.

Popup forms can open either After delay or When browser event fires. Use the event trigger for CTA-driven forms; site buttons stay site-owned and only emit the configured browser event:

window.dispatchEvent(new CustomEvent('ucrm:open:schedule-demo-call'));

Any number of buttons can emit the same event. The popup form markup is rendered once and stays hidden until the event is received.

Use After delay when the form should appear automatically after the configured time instead of waiting for a CTA event.

The form block forwards Umbraco's current UI culture to uCRM when it fetches state and when it submits, so multilingual forms should store translated labels/placeholders in the Marketing Form localizations definition.

Current Release Highlights

• Leads, contacts, accounts, and deals workspaces
• CRM dashboards for backoffice users
• Record activity history
• Notes, tasks, and attachments on entity detail views
• Package assets and shared schema provisioning on startup

Support

• Website: https://client-craft.com
• Contact: arthur.nassar@client-craft.com