> ## Documentation Index
> Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish a Form Page Publicly

> YiDA form pages support public publishing, enabling anonymous organization surveys. This topic explains how to enable public access, walks through the steps, and highlights key considerations.

Before enabling public access, check whether the form contains any incompatible components, then follow the steps below to configure the public access link.

<Note>
  Public access cannot be turned on if the form contains any of the following:

  * Components exclusive to the organization, such as user or department.
  * Premium components that the platform does not yet support for public access, such as associated form, associated lookup, industry components (education industry), or custom components.
</Note>

## Steps

<Steps>
  <Step title="Step 1">
    Sign in to the [YiDA workbench](https://www.yidaapps.com/workPlatform).
  </Step>

  <Step title="Step 2">
    Click **My Apps**, select the target app, and click to open the app details page.
  </Step>

  <Step title="Step 3">
    Select the page you want to publish separately, then click  > **Publish Page**.
  </Step>
</Steps>

4. Select **Publish publicly**, then turn **On** the public access switch.

5. Read the *User Agreement*. If you agree, click **Accept**.

6. Set the access link. When finished, click **Save** to complete public publishing.

<Note>
  The public access link only supports lowercase letters (a-z), uppercase letters (A-Z), numbers (0-9), underscores (\_), hyphens (-), and slashes (/).
</Note>

## Things to Note

When configuring public page access, also keep the following in mind:

* When data is submitted or a workflow is initiated through the public access address, the data submitter or workflow initiator is anonymous.
* Uniqueness validation configured on the page does not apply. That is, restricting one account to a single submit does not work.
* Under public access, the platform does not restrict the page from accessing data of other forms under the current app. Any resulting information leakage risk is borne by the app admin.
* After silent login access is turned on, sending Card messages to individuals or group chats is no longer supported.
* Images and attachments do not support access from outside the organization by default. If needed, replace them with a CDN address accessible on the public network.