Skip to main content

Platform Overview

Endatix Hub is the web app you use for running forms or surveys: you build them, decide who can open them, put them in front of respondents, and work with the answers that come back. This section covers what you do in that UI.

If you are integrating Endatix with your own code or running the servers yourself, use the Developers tab instead.

What you can do​

FormsBuild questions, logic, validation, and translations in the Form BuilderData ListsShare one maintained set of answer options, in several languages, across formsSharing and EmbeddingControl who can open a form, share a link, or embed it in your own pageSubmissionsRead, filter, share, and export the responses a form collectsAdministrationWorkspace and platform settings: users, email, authentication, environment

From a form to data​

Four steps, in the order you will do them.

  1. Create the form. Start from the Forms list, or copy a starting point from Form Templates. A new form begins empty and is not reachable by respondents yet.
  2. Design it. The Form Builder holds everything about the form's content: questions and pages, conditional logic, validation, the thank you page, and translations.
  3. Decide who can open it, then share it. Visibility decides whether respondents have to sign in. From there you either hand out the share link or paste an embed code into a page you own.
  4. Collect and review. Answers arrive in the form's Submissions grid, where you filter them, open one to read it, mark your review progress, and export the set.

Where things are in Hub​

The left sidebar in Hub maps to these docs:

  • Forms - every form in the workspace. Opening one gives you Form Overview, the Form Builder, and that form's submissions.
  • Form Templates - reusable starting points for new forms.
  • Folders - grouping for a long form list.
  • Data Lists - choice lists shared across forms, so several questions can draw from one maintained set of options.
  • Settings - your workspace: form defaults, users, roles, export formats, and your own account security.
  • Platform Admin - visible to platform administrators only. Tenants, platform admins, authentication, email, storage, and the environment audit.

Terms you will see​

  • Form - the thing a respondent fills in. It has one identity and one URL for its whole life, even as you keep editing it.
  • Form definition - the saved version of a form's questions and settings. Each submission is tied to the definition that was active when it was answered, so editing a live form does not rewrite responses you already collected.
  • Submission - one respondent's answers to one form. Endatix saves a submission from the respondent's first answers, not only when they press submit.
  • Partial submission - a submission that was started and not finished. The respondent can come back and continue until the session expires.
  • Complete and Status - two different things in the submissions grid. Complete says whether the respondent reached the end. Status (New, Read, Approved) is your own review marker, and Endatix never changes it for you.
  • Visibility - Public forms open for anyone with the link. Private forms make the respondent sign in first.
  • Workspace - your organization inside Endatix: its forms, users, roles, and shared settings.

If you also work with the API​

Several things in this section have a developer counterpart in the Developers tab: embedding a form via iframe, webhooks for reacting to a submission, pre-filling from a URL, and the API reference.

Next steps​

Form BuilderQuestions, logic, validation, and the thank you pageVisibility (Public / Private)Decide whether respondents have to sign inViewing SubmissionsFilter, sort, and choose columns in the submissions grid