Install and apply a reusable reception form template
Identify the definition and its destination
A reception-form add-on supplies reusable template definitions to the editor. Installing that definition and applying its configuration to a receptionist are separate steps. Work in the intended desktop workspace with the required access: updating the shared asset pack requires OWNER or ADMIN authority. The result is a workspace resource, not a private preset or evidence that an integration is running.
For a fictional example, use Workshop enquiry with two harmless fields, Topic and Question, and an empty webhook URL. Give its add-on and template coherent, unique identifiers. Reusing a built-in identifier does not replace its form definition, and duplicate template identifiers can make selection ambiguous. An accepted JSON file is normalized data, not proof that every capability label implements a working feature.
Import and inspect the available template
In Objects, open Asset library, then Custom assets and add-ons. Choose Import add-on for the understood manifest file. This differs from Import pack for mixed resources and Import JSON under Save & files for a whole map layout. Do not use a whole-layout import to install a form template.
Inspect the returned feedback and Installed add-ons row. An unusable manifest can report Add-on JSON has no usable manifest. The import updates a workspace pack and then reloads its catalog. A failed update and a failed reload after a successful update can both prevent Installed success feedback. Read the error and inspect the reloaded library before retrying; the latter failure does not establish rollback.
The isolated checks used memory-only pack replies and synthetic files. Their caught failure messages do not prove that a real workspace imported anything. A visible row is the next configuration check, not a receipt for a visitor submission.
Apply a copy to one receptionist
Select the intended editor-added receptionist and find Reception NPC. In Template, choose Workshop enquiry. Inspect the copied Visitor form enabled state, title and fields before saving. Selecting a template copies its normalized configuration, including settings that can enable the object's form; it does not merely rename the existing selection.
The fictional example should still contain exactly Topic and Question. Empty field definitions can fall back to default intake fields, so clearing the list is not a reliable way to make a harmless empty form. Keep the webhook empty for this example.
Use the ordinary layout export to inspect the intended custom object's receptionForm data, and keep its identifier with the check. Confirm a separate authorized map save through the normal workflow. The isolated native selection and source checks do not establish a real save or later visit.
Distinguish library availability from the copied form
In Installed add-ons, Disable removes that definition's templates from the current editor's available choices after a successful reload. It does not remove the manifest or clear a form configuration already copied into an object. Enable can make the template available again. Do not assume every other open client updates instantly.
After Disable, the select may retain a value whose option is absent. Its apparent label is not evidence that the object's form changed. Inspect the copied enabled state, title and fields or exported object data. The per-object Visitor form toggle is a separate control; library disable is not a substitute for it.
Keep the definition and result checks separate
Export add-ons downloads the current normalized definitions, including disabled and built-in entries. It is not a byte-for-byte copy of the original file or a saved map. Check the resulting file separately from the object's configuration.
The guide image shows a native template picker in an isolated synthetic fixture. Finish with an identified definition, an inspected object copy and the actual save outcome you obtained. No visitor intake, staff response or webhook delivery follows from those checks.
