Client Craft Hub Search documentation /

Search documentation

Implement and extend Client delivery

Browse documentation

Preview Version 0.1.0-alpha.16

Connect an Umbraco installation to the customer workspace

Use the installation connection flow to establish an approved server-side connection, then confirm the local acknowledgement and the intended workspace. Installation credentials, workspace selection and a person’s permissions are separate checks.

ClientCraft 0.1.0-alpha.16 installed, an approved local Umbraco administrator and an authorised Client Craft administrator for the customer. Secret storage must be ready before connecting.

Implementation steps

  1. Choose the installation and native website root

    As an authorised installation administrator, open Connect to Client Craft. Enter the Installation name and use Choose website root to select this customer’s existing Umbraco content root. Other websites in the same installation are not included. Select Start connection. Do not choose the agency root simply because you can administer it.

  2. Approve the matching registered website in Client Craft

    Select Sign in with Client Craft. In the secure central review, choose the customer organisation, intended workspace and registered self-hosted website, then review and authorise this installation. If the customer has not completed account verification, commercial setup or website registration, complete those prerequisites first. Your Client Craft password is not copied into the Umbraco installation.

  3. Save the approved connection on the installation

    Return to the original Umbraco tab, choose Check authorization and then Save approved connection when the approved state is shown. Connection saved securely confirms the installation credential was validated and stored on the server. Do not copy credentials into a CMS field, code sample or visitor script. If a request expires, use Restart authorization; Resume authorization checks an existing request rather than inventing a new customer association.

  4. Check connection health and separate permissions

    Inspect the final installation status before configuring CRM or accepting website enquiries. Pending local acknowledgement is not a completed connection. Website approval, native content permissions and the operator’s CRM seat remain separate checks; a connection does not grant all three. A standalone Visual Builder installation does not require this CRM connection or replace native Umbraco sign-in. Do not bypass a failed workspace or permission check.

Continue the integration