---
title: "Access and Submission Conditions"
slug: "access-and-submission-conditions"
updated: 2026-08-04T15:47:33Z
published: 2026-08-04T15:47:33Z
canonical: "knowledge.technolutions.net/access-and-submission-conditions"
stale: true
---

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

# Access and Submission Conditions

When creating a form, event, or interview, you can restrict who is eligible to open the form or submit a response.

In each of these cases, you can display a message to the respondent explaining why their action was rejected.

## Accessing form access and submission conditions

To edit submission conditions, select **Edit Conditions** at the right side of the Edit Form page.

![Screenshot showing the location of the "Edit Conditions" button](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image-U83822YH.png)

The edit conditions interface is split into two sections:

![Screenshots showing the location of 'Access Conditions' and 'Submission Conditions'](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Access and Submission Conditions.png)

#### Access Conditions

Only available if the respondent will be known prior to the form loading.

For example, access conditions appear if the form is application-scoped, or is person-scoped and flagged to require login.

#### Submission Conditions

Available for all scopes except *Application Page*.

## Configuring form access and submission conditions

Each of these sections has two configuration options, an **“Access Denied” message** and **filters**.

#### Access Denied message

Customize the message displayed when the action is denied.

- Merge fields are not currently supported within the messaging.
- For both access and submit conditions, the message is written for people that cannot access/submit the form, while the filters are written to define those that can. That is, the message is shown when the registrant does not meet the filter criteria.

#### Filters

Filters identify the records permitted to perform access or submit the form.

Application and person-scoped filters used in Submission Conditions are evaluated inclusive of the data on the form. If the data entered via the form will update a system field in such a way that the filter criteria is met, then submission will be permitted.

## Prevent access to, submission of a form unless an application has been submitted

In the case where an application-scoped form should only be accessible if the associated application has been submitted, the configuration might look like something like this:

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image-P30Y8T0I.png)

In the event of the application not being submitted, attempting to access the form will result in the following error message:

```plainText
You have not submitted your application. This form is only available for those who have 
submitted their application. Please submit your application and try again.
```

## Prevent an applicant from creating more than one application in the same round when using an Application Creation form

In the case where an application creation-scoped form should not be submitted if an application for the same round already exists, the configuration might look like something like this:

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Filter logic - prevent form resubmission.png)

1. Join to **Application**, then to **Person** at the base level.
2. In a subquery, join from **Person** to **Applications** and rename of the join to “All Applications” for clarity, since Application and Applications can be difficult to distinguish while building filter criteria.
3. In the subquery create two additional subquery comparison filters:

If these are both **true**, the applicant has another application in the same round, and they won’t be allowed to submit the Application Creation form.
  - **GUIDs are not the same** uses a `Comparison` aggregate to check whether the `Application GUID` matches any GUIDs in `All Applications GUID`.
  - **Rounds are the same** uses another `Comparison` aggregate to check whether the `Application Round` matches any rounds in `All Applications Round`.

> [!WARNING]
> **Note:**
> 
> This submission condition should only be used with an **application creation-scoped** form.

💼 Try a Slate example

You can import this filter logic, along with the application-creation form that goes with it, using the following [Suitcase](/v1/docs/suitcase-import) ID:

```ID
f1de28ec-b440-4416-8185-94f32fd79e8a:slate-examples
```

If the application has already been submitted, attempting to access the form results in the following error message:

```plainText
You have already submitted this application.
```