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.

The edit conditions interface is split into two sections:

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

Identifies the population permitted to perform said action by using filters.

• 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.

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:

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

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 applicant from creating more than one application in the same round

In the case where an application-creation-scoped form should not be accessible after the application has been submitted, the configuration might look like something like this:

This filter logic uses two subquery filters:

• 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.

If these are both true, the applicant has another application in the same round, and they won’t be allowed to submit the form.

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:

You have already submitted this application.