Share and delete templates

Sharing a template makes it available within the workspace according to its access rules. It does not automatically share every user variable, prompt definition, or private asset referenced by the HTML.

Prepare a template for teammates

Inspect its variable manifest. Replace accidental personal references, confirm reusable images are accessible, and tell teammates which saved definitions they need. Generate a test Page as the intended user rather than only as the template owner.

Assets have their own sharing setting. Landit can block making a shared asset private when a shared template or another user’s template or Page depends on it. Resolve those references before changing access.

Understand owner-specific values

user.* and prompt.* definitions resolve for the Page owner. A teammate using the same template may have a different booking link or no matching prompt definition. Sharing should therefore be verified with the actual Page-owning account.

Delete with care

Deleting a template from the library does not necessarily remove Pages already associated with it. Do not use library deletion as a way to revoke public Page links or erase historical data.

Before deleting, identify existing Pages and any shared dependencies. For public-link behavior, read sharing and expiry. For account deletion or data requests, read data lifecycle; these are separate operations.