# Custom form end-user experience

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

Based on the custom form experience you configured, these are some scenarios the end-user may see when they add an app from the Zoom Marketplace.

## Pre-auth configuration: app-level

Zoom displays the custom form and the user must provide information for any app-level fields before they can proceed with authorizing the app.

![](/img/pre-auth-entry.png)

### Admin Options

If the user is an admin for their Zoom account, they may have additional controls:

-   **Set as Default:** Admins can mark the values they provide as default for their entire account. When other users in their account add the app, these values will be pre-filled. Regular users can typically override these defaults unless the fields are locked.
-   **Lock Field:** Admins can choose to lock certain app-level field values. If locked, these values are enforced for all users in the account, and individual users cannot see or change them.

    ![](/img/admin-settings.png)

---

## Pre-auth configuration: connection-level

After completing app-level pre-auth fields, the users are presented with connection-level fields specific to the individual connection they are setting up.

### Connector authorization

Once the pre-auth values are filled, the user proceeds to the app's main authorization flow (e.g., OAuth with a third-party service).
A common scenario has the app using the provided values to facilitate or complete the connection (e.g., an API key or instance URL might be passed).

## Post-auth configuration

Zoom displays post-auth custom forms after a successful connection. The form can include fields for settings that are only relevant after the connection is live, including Dynamic Fields (e.g., a dropdown populated with data fetched from the newly connected service).

![](/img/post-auth2.png)

---

## Zoom scope consent (if applicable)

If the app also requires permission for Zoom-specific scopes (accessing recordings or calendar information), Zoom directs the user to the standard Zoom OAuth consent page to grant these permissions.

---