What is a project?

Projects provide a contextual sandbox that controls the scope of all the elements within that project. This allows, for example, a form builder to be given permission to create forms in one project but not another, or for a form user to view submissions in one project but not others.

The various elements that can be contained in a project context include:

• Forms & Resources - Ad-hoc data collecting interfaces

  • Submissions - Data submitted into each form

  • Actions - Actions performed once the form is submitted; such as Email, Webhooks, etc.

  • Logs - Keeps an active report of actions performed.

  • Access - Assign Role-based permissions to certain actions within each form

  • Revisions - If enabled, create new revisions for every form update.

  • Settings - Settings per-form

• Roles - Assigned to users to establish access control. Can be user-defined.

• Stages - Child project contexts used to manage multiple environments and authoring workflows.

• Settings

  • Integrations - Configure integrations with third-party providers, such as Email providers on a per-project basis

  • Authentication - Configure SSO, OAuth, SAML, and LDAP authentication systems.

  • Stage Versions and Deployments - Used to create and manage the versions of a specific stage and to deploy created versions to other stages.

  • On-Premise Environment - Allows you to connect a stage to a remote API server.

  • Project & Stage Settings - Includes CORS, API Keys, Public Configurations, etc.