Sharing a form

Once a form is published, the Share tab is where you get the link to hand out. With nothing selected on the canvas, open Share on the right rail.

How the link is resolved

The link is resolved, never guessed, in this order, stopping at the first hit:

1. The form’s own Share URL, from Form settings, Availability. Paste the address where you actually placed the form. This is the answer for a form on a hand-built Experience Cloud page, embedded on a customer’s own site, or anywhere else only you know about.
2. Your public Sliick Edge address, for a form with Allow on your public Sliick Edge address ticked. This one is delivered to the org when you connect Sliick Edge, which is why it outranks the template below.
3. The org-wide Experience Cloud address from the Admin Dashboard’s Delivery panel, used as a template, with {form} replaced by this form’s external ID.
4. Nothing.

What you get when a link resolves

The URL plus Copy link, Show QR, Download blueprint, and Open as test respondent, which fills in the live form without counting toward results, caps, or experiments.

When nothing resolves

The panel says so and offers Download blueprint and nothing else: no link, no QR code.

This is intentional. A form can be placed anywhere, so there is no address the org can derive for every case, and showing an incorrect link is worse than showing none. That is particularly true of a QR code, which is often printed before anyone tests it.

If you expected a link, check Choosing how to host a form: either the form needs its own Share URL, or the org needs an address set in the Delivery panel.

A link filled in from a record

The Share tab’s Create prefill link panel makes a link that opens this form with one record’s values already in it: pick the object, pick the record by name, see what the link will carry, and generate it.

That panel is one of four ways to make the same thing, and the rules are the same from all of them. They have their own page: Record links.

A form that maps no fields says so rather than offering a picker that could not work, and a form that has not been published yet tells you to publish it first, because a link against an unpublished form returns nothing.

Values from the page link

A field can also be filled in straight from the link’s own URL, separate from a record link: tick Accept a value from the page link on the field, and a link carrying that field’s name seeds it. A field whose API name is utm_source is filled by ?utm_source=partner-x.

This is off by default, set per field, and never offered on a field used for matching, so a link cannot steer which record a submission updates. A record link always takes priority over it.

The key in the link is the field’s own API name, unless you give it another one. Ticking the box reveals a URL Parameter Name input: fill it in and the link answers to that name instead, so a link already printed or in circulation keeps working even after the field is renamed. Leave it empty and the field’s API name is the key.

A multi-select can take several values from a repeated parameter, such as ?topics=a&topics=b. Record links and record-page prefill also fill an unanswered multi-select. This needs Sliick Forms 0.9.0 or later.

Publishing refuses two fields that would answer the same parameter, and a parameter name the form runtime already uses for something else. That reserved list is complete as of v0.8: three names the public form owns were missing from the check before it, so a field could be created that silently never filled from the link.