• Blog
  • Changelog
  • Roadmap
  • Pricing
  • FAQ
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
    • Dashboard
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Claims
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview before saving
    • Save and version history
  • Member code query
  • Support desk
    • Support desk settings
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
    • Anonymize a membership
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Frontends
    • Create a frontend
    • Frontend keys
    • Released claims
    • Sign-in settings
    • Guest access
    • Sign-in branding
    • Sign-in texts
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Vouchers
    • Partners
    • Create a voucher offer
    • Voucher pools
    • Activate, pause and end a voucher offer
    • Voucher settings
    • Import from the Portal
  • Redemptions
    • Handle a redemption
    • Redemption settings
  • Forms
    • Form inbox settings
    • Handle a form submission
  • Booking requests
    • Handle a booking request
    • Booking settings
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Permissions
    • Billing
    • Roadmap and feature requests

appsolut ONE – enterprise community server. One platform for your internal and external communities, with membership and sign-in built in.

About
  • Blog
  • Contact
Documentation
  • Studio
  • Portal
  • Developers
Product
  • Roadmap
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Impressum

© Copyright 2026 appsolut ONE. All Rights Reserved.

  • Blog
  • Changelog
  • Roadmap
    1. Documentation
    2. Studio
    3. Forms
    Studio

    Forms

    The submissions of your website's forms, the form inboxes that receive them, and who they are mailed to.

    A form submission is what a person sends with one of your website's forms, such as a contact form. The Studio keeps the form as the person saw it, with its title and its fields in order, the values they entered, the page they sent it from and their language, and gives it a reference starting with FS-. A submission starts open.

    Every form has one form inbox: where your organisation receives its submissions, and who they are mailed to. A form inbox is named after the form's title and knows the form by its form reference, the form's ID in your website's CMS. You can create a form inbox before the form's first submission. A submission of a form without one opens its form inbox itself, marked "Recipients not set": until someone sets its recipients, its submissions are mailed to your organisation's support address from the sign-in branding.

    You find the form inboxes under "Forms", "Form inboxes" in the sidebar, with each one's form reference, whether its recipients are set, whether it sends a confirmation, its number of submissions and the last one.

    The mails of a submission

    After every new submission the Studio sends, in your organisation's branding:

    • To the form inbox's recipients: the form's title, the page it was sent from and every field under its label, with the FS- reference. Its subject is the one you set for the form inbox, or else one naming the form. A reply goes to the first email field of the form that holds an address, so the recipients answer the person directly. The addresses your website's editors enter in the CMS's form are not used.
    • To the person who sent it, where you switched it on: a confirmation with your own subject and text, in the person's language, or in German where that language has no text. A signed-in sender gets it at their verified email, a guest at the form's first email field. The text may take short values of the submission, such as a first name, through placeholders.

    How each mail went is shown on the submission's page. A mail that fails never undoes the submission.

    Signed in or a guest

    A person signed in to your frontend sends a form with their frontend user: the Studio keeps their verified email and, where they hold one, their organisation membership. A person who is not signed in sends it as a guest, which a frontend accepts only where its guest access for forms is on.

    How long submissions are kept

    A form submission is deleted 7 years after its last status change. When an organisation membership is anonymized, the submissions made under it, by its frontend user, or carrying that frontend user's email are anonymized too: the sender's email, the note and every value but the choices from the form's own options are removed.

    Previous pageRedemption settingsNext pageForm inbox settings