Integrate a client’s Umbraco website with Client Craft

Implementation steps

1. Agree the customer boundary

   Record who owns the organisation, which workspace this website will use and who can approve the installation. Keep different customers in their intended authorised scope. Installing a plugin does not create CRM licensing, ownership or permission. A self-hosted Umbraco site remains your agency’s hosting responsibility; the connected operational platform is provided by Client Craft.

2. Install the compatible package

   Use the linked installation guide in the existing website project. Pin ClientCraft 0.1.0-alpha.16: it selects Core alpha.29, Visual Builder alpha.15 and SDK preview.14. Build and review native package migrations in the test copy. Preserve document keys, URLs, media and the existing Umbraco authentication flow.

3. Approve and confirm the installation connection

   Use the Client Craft installation connection flow with authorised local and central administrators. Confirm the intended customer before approval, finish the local connection acknowledgement and check its status. Do not copy an installation code or integration key into public content, frontend JavaScript or screenshots. The connection guide explains the boundaries and recovery.

4. Prepare the customer CRM

   Select the authorised customer workspace and agree how enquiries are classified and assigned. Configure the pipeline and stages supported by the installed version; identify a responsible person and the next action. Do not rely on the agency’s default workspace or assume another person’s access proves the customer’s access.

5. Connect one real website form

   Use the Client Craft form block in the page’s normal Content grid. Select the intended available form configuration, review its destination and map the information needed by the CRM. Keep server credentials out of authored content. Follow the form guide to confirm validation, submission and the actual resulting record.

6. Prove the result and the denial path

   Submit one clearly labelled fictional enquiry in the authorised test environment. Record the form/page reference, resulting CRM record, target workspace and responsible person; inspect the actual persisted fields. Confirm that a user without access cannot open the customer workspace. Test a validation failure and a retry without assuming a success message proves persistence. Never use real live payments for this exercise.

7. Hand over a reproducible installation

   Retain the package lock, environment configuration names, connection owner, acceptance record and rollback procedure. Give the customer their authorised entry route and explain who maintains the website and the connected platform. Store secrets separately. Extend through supported Umbraco and package APIs rather than editing installed package files.