> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/use-cases/how-to-collect-data-from-recipients.md). # How to Collect Data from Recipients {% hint style="info" %} Use this page when you know what recipients must provide, but you have not chosen the collection method yet. {% endhint %} ### Before you start Before you choose a method, define: 1. Define who enters the data. 2. Define where the data comes from. 3. Define whether the data must be validated, reused, searched, or generated automatically. 4. Define whether the process starts inside DocStudio or through an external link or integration. Then use the table below to choose the collection method and open the related instruction. ### What users often confuse * Text Field is not the same as Number Field, Currency Field, or Date Field. * Dropdown Field is not the same as Dictionary Field. * Lookup Field does not work as a standalone input. * Dynamic Table Field is not the same as a static table. * Public template links are not the same as integrations and API access. ### Choose the right method
Recipient taskUseAvoidGo to
Enter a name, address, comment, ID, or other free-text valueText FieldNumber, Currency, or Date fieldsText Field
Enter a number, quantity, percentage, or other numeric valueNumber FieldText FieldNumber Field
Enter a money valueCurrency FieldNumber FieldCurrency Field
Enter or select a dateDate FieldText FieldDate Field
Choose one answer from a short listChoice Field or Dropdown FieldDictionary FieldChoice Field
Dropdown Field
Confirm a condition or mark a yes/no valueCheckbox FieldText FieldCheckbox Field
Select a value from reusable reference dataDictionary FieldDropdown FieldDictionary Field
How to Create and Manage Dictionaries
Fill a related value from the selected dictionary recordLookup FieldLookup Field without Dictionary FieldLookup Field
Dictionary Field
Upload a supporting document or attachmentFile upload FieldText Field or email attachmentFile upload Field
Add repeated rows of structured dataDynamic Table FieldStatic tableDynamic Table Field
Validate a value formatField masks (RegEx)Manual review onlyField masks (RegEx)
Find envelopes later by collected valuesSearch-enabled fieldsfields without Search enabledHow to Filter Envelopes
How to Customize the Envelope List
Let external users start the flow themselvesPublic template linkManual envelope creation for each caseHow to Create a Public Template Link
Reuse fields that already exist in a PDFEmbedded PDF field importManual field recreationHow to Upload a Document for Electronic Signature
How to Add PDF Documents in a Template
Collect or prefill data from an external systemIntegrations and API accessManual inputIntegrations & API Access
Application Tokens (API Access)
Scenarios
Control recipient language, time zone, and date or number formatRecipient experience settingsfield-level validationHow to set up Recipient Experience in a Template
After you choose a method, use the scenarios below to confirm the correct flow. ### Typical scenarios #### Collect customer application data Use this scenario when recipients must provide basic information in an application form. **Goal:** collect personal, contact, or request details. **Use:** * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) for names, addresses, comments, and IDs * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) for numeric values * [Date Field](/user/template-builder/template-dynamic-fields/date-field.md) for dates * [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) or [Choice Field](/user/template-builder/template-dynamic-fields/choice-field.md) for predefined answers * [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md) when values must follow a specific format **Do not use:** * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) for a short one-time list * [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) for simple single-value questions * public template links only because the form has many fields **Go to:** * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) * [Date Field](/user/template-builder/template-dynamic-fields/date-field.md) * [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) * [Choice Field](/user/template-builder/template-dynamic-fields/choice-field.md) * [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md) #### Collect invoice line items Use this scenario when recipients must enter several rows of similar data. **Goal:** collect repeated structured data. **Use:** * [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) for repeated rows * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) for quantity * [Currency Field](/user/template-builder/template-dynamic-fields/currency-field.md) for prices or totals * [Formula Field](/user/template-builder/template-dynamic-fields/formula-field.md) when values must be calculated **Do not use:** * static tables when recipients must add rows * several separate [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) values for repeated items * [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) when the recipient must enter row data **Go to:** * [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) * [How to Add and Manage Static Tables](/user/template-builder/template-editor/how-to-add-and-manage-static-tables.md) * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) * [Currency Field](/user/template-builder/template-dynamic-fields/currency-field.md) * [Formula Field](/user/template-builder/template-dynamic-fields/formula-field.md) #### Collect company data from a controlled directory Use this scenario when recipients must select values from a managed list. **Goal:** collect standardized values from reusable reference data. **Use:** * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) when the recipient must select a record from a dictionary * [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) when related values must be filled from the selected record **Do not use:** * [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) when values must be maintained in a central directory * [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) without a related [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) when manual input can create duplicates **Go to:** * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) * [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) * [How to Create and Manage Dictionaries](/user/dictionaries/how-to-create-and-manage-dictionaries.md) #### Collect supporting documents Use this scenario when recipients must attach files during the envelope flow. **Goal:** collect files from recipients. **Use:** * [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) **Do not use:** * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) to describe a file instead of uploading it * external documents when the recipient must upload the file during completion * email attachments outside the envelope flow **Go to:** * [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) * [How to Configure Files Included in the Envelope Archive](/user/template-builder/template/how-to-configure-files-included-in-the-envelope-archive.md) #### Let external users start the flow themselves Use this scenario when users outside DocStudio must open a link, fill the required data, and create or complete an envelope flow. **Goal:** start data collection outside the sender’s manual envelope creation flow. **Use:** * public template link * public template iframe when the same public flow must be embedded into a website * registered or unregistered template link flows for recipient-side behavior **Do not use:** * manual envelope creation for every recipient when the same flow must be reused * Quick send when the recipient must start the process * public template links when the sender must approve every envelope before sending **Go to:** * [How to Create a Public Template Link](/user/template-links-and-public-envelope-creation/how-to-create-a-public-template-link.md) * [How Registered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-registered-users-can-create-an-envelope-via-a-template-link.md) * [How Unregistered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-unregistered-users-can-create-an-envelope-via-a-template-link.md) #### Collect data from an external system Use this scenario when recipient data already exists in another system or when the process must be automated. **Goal:** reduce manual input and connect DocStudio to an external process. **Use:** * [Integrations & API Access](/admin-panel/integrations-and-api-access.md) * [Application Tokens (API Access)](/user/authorization-and-security/application-tokens-api-access.md) * [Scenarios](/user/scenarios.md) * [How to Run a Scenario via Integration](/user/scenarios/running-scenarios/how-to-run-a-scenario-via-integration.md) **Do not use:** * manual field input when the data already exists in another system * public template links when the flow must be fully system-driven * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) as a replacement for integration logic **Go to:** * [Integrations & API Access](/admin-panel/integrations-and-api-access.md) * [Application Tokens (API Access)](/user/authorization-and-security/application-tokens-api-access.md) * [Scenarios](/user/scenarios.md) * [How to Run a Scenario via Integration](/user/scenarios/running-scenarios/how-to-run-a-scenario-via-integration.md) #### Use fields from an existing PDF Use this scenario when the uploaded PDF already contains fillable fields. **Goal:** reuse existing PDF fields instead of recreating all fields manually. **Use:** * embedded PDF field import **Do not use:** * manual field recreation as the first option * embedded PDF field import when the PDF fields are not needed * static PDF content when recipients must enter data into DocStudio fields **Go to:** * [How to Upload a Document for Electronic Signature](/user/dashboard/how-to-upload-a-document-for-electronic-signature.md) * [How to Add PDF Documents in a Template](/user/template-builder/template-editor/how-to-add-pdf-documents-in-a-template.md) ### Field-based collection methods #### Simple fields Use simple fields when recipients must type or select one value. **When to use:** Use simple fields for basic values that belong directly in the document. **Best for:** * names * addresses * comments * IDs * numbers * dates * amounts **Do not use this when:** * the recipient must choose from a controlled directory * the recipient must upload a file * the recipient must add repeated rows * the process must start outside DocStudio **Go to:** * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) * [Currency Field](/user/template-builder/template-dynamic-fields/currency-field.md) * [Date Field](/user/template-builder/template-dynamic-fields/date-field.md) #### Predefined answers Use predefined answers when recipients must choose from available options. **When to use:** Use predefined answers to reduce typing mistakes and standardize input. **Best for:** * one answer from a short list * yes/no confirmation * simple selection from prepared options **Do not use this when:** * the list must be centrally managed and reused across templates * the selected value must fill related values automatically * the recipient must enter long free text **Go to:** * [Choice Field](/user/template-builder/template-dynamic-fields/choice-field.md) * [Checkbox Field](/user/template-builder/template-dynamic-fields/checkbox-field.md) * [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) #### Dictionary-based values Use dictionaries when values must come from reusable reference data. **When to use:** Use [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) when recipients must select a record from a managed list. **Best for:** * companies * employees * departments * products * services * regions * reusable business values **Do not use this when:** * the list is short and used only in one template * the recipient must enter a unique free-text answer * related values must be filled without a dictionary selection **Go to:** * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) * [How to Create and Manage Dictionaries](/user/dictionaries/how-to-create-and-manage-dictionaries.md) #### Lookup values Use [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) when a related value must be filled from a dictionary selection. **When to use:** Use [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) after the recipient selects a value in [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md). **Best for:** * company address from the selected company * tax number from the selected company * employee details from the selected employee * related product or service data **Do not use this when:** * there is no [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) in the document * the recipient must type the value manually * the value does not depend on another selection **Go to:** * [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) #### File uploads Use [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) when recipients must provide files. **When to use:** Use [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) when the recipient must upload a file during the envelope flow. **Best for:** * supporting documents * scans * certificates * images * attachments * additional forms **Do not use this when:** * the sender already has the file before sending * the recipient only needs to enter text * the file must be part of the template before the envelope starts **Go to:** * [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) * [How to Configure Files Included in the Envelope Archive](/user/template-builder/template/how-to-configure-files-included-in-the-envelope-archive.md) #### Repeated table data Use [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) when recipients must add several rows of similar data. **When to use:** Use [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) when the number of rows may change. **Best for:** * invoice line items * product lists * service lists * employee lists * expense rows * asset lists **Do not use this when:** * the table is only visual layout * the number of rows is fixed and recipients do not fill them * each value can be collected as a separate simple field **Go to:** * [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) * [How to Add and Manage Static Tables](/user/template-builder/template-editor/how-to-add-and-manage-static-tables.md) ### Related tools that support data collection Use these tools when the collection flow needs more than a single input field. #### Formula Field Use [Formula Field](/user/template-builder/template-dynamic-fields/formula-field.md) when DocStudio must calculate a value from other fields. Best for: * row totals * grand totals * calculated percentages #### Duplicate Field Use [Duplicate Field](/user/template-builder/template-dynamic-fields/duplicate-field.md) when the same collected value must appear in several places. Best for: * repeating an ID * reusing a company name * copying one field into several document areas #### Autonumber Field Use [Autonumber Field](/user/template-builder/template-dynamic-fields/autonumber-field.md) when the value must be generated automatically instead of entered by the recipient. Best for: * request numbers * internal references * sequential document IDs #### QR/barcode Field Use [QR/barcode Field](/user/template-builder/template-dynamic-fields/qr-barcode-field.md) when collected or generated values must be encoded into a scannable code. Best for: * links * tracking codes * internal identifiers **Go to:** * [Formula Field](/user/template-builder/template-dynamic-fields/formula-field.md) * [Duplicate Field](/user/template-builder/template-dynamic-fields/duplicate-field.md) * [Autonumber Field](/user/template-builder/template-dynamic-fields/autonumber-field.md) * [QR/barcode Field](/user/template-builder/template-dynamic-fields/qr-barcode-field.md) ### Validation and search #### Validate recipient input Use [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md) when a value must follow a strict format. **When to use:** Use validation when incorrect input can break the process or require manual correction. **Best for:** * phone numbers * tax numbers * registration numbers * contract numbers * codes * bank account numbers **Do not use this when:** * the value does not require a fixed format * a different field type already solves the problem * manual review is enough for the process **Go to:** * [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md) * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) * [Date Field](/user/template-builder/template-dynamic-fields/date-field.md) #### Make collected data searchable Use Search-enabled fields when users must find envelopes by collected values later. **When to use:** Use **Search** only for values that must appear in mailbox filters or columns. **Best for:** * contract number * customer name * company name * department * region * service type **Do not use this when:** * the value is not useful for search * too many searchable fields would make filtering harder * the field is only useful inside one document **Go to:** * [Template Dynamic Fields Overview](/user/template-builder/template-dynamic-fields/template-dynamic-fields-overview.md) * [How to Filter Envelopes](/user/envelopes/how-to-filter-envelopes.md) * [How to Customize the Envelope List](/user/envelopes/how-to-customize-the-envelope-list.md) ### Advanced collection methods #### Public template links Use public template links when external users must start the flow themselves. **When to use:** Use public template links for reusable self-service flows. **Best for:** * public application forms * external user requests * customer onboarding * website or messenger-based flows * reusable template-based processes **Do not use this when:** * the sender must prepare every envelope manually * the recipient must only sign a prepared envelope * the flow must be fully controlled by an external system **Go to:** * [How to Create a Public Template Link](/user/template-links-and-public-envelope-creation/how-to-create-a-public-template-link.md) * [How Registered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-registered-users-can-create-an-envelope-via-a-template-link.md) * [How Unregistered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-unregistered-users-can-create-an-envelope-via-a-template-link.md) #### Integrations and API access Use integrations and API access when data collection is part of an automated process. **When to use:** Use integrations or API access when data comes from another system or when the envelope must be created automatically. **Best for:** * CRM-based flows * ERP-based flows * website forms * repeated automated processes * system-driven envelope creation * integration-based data prefilling **Do not use this when:** * a user can complete the process manually * a public template link is enough * no technical setup is available **Go to:** * [Integrations & API Access](/admin-panel/integrations-and-api-access.md) * [Application Tokens (API Access)](/user/authorization-and-security/application-tokens-api-access.md) * [Scenarios](/user/scenarios.md) * [How to Run a Scenario via Integration](/user/scenarios/running-scenarios/how-to-run-a-scenario-via-integration.md) ### Import and localization #### Embedded PDF field import Use embedded PDF field import when an uploaded PDF already has fillable fields. **When to use:** Use embedded PDF field import to convert existing PDF fields into DocStudio fields where supported. **Best for:** * existing fillable PDF forms * documents with prepared field structure * faster migration from PDF-based forms **Do not use this when:** * the PDF has no useful embedded fields * you need to redesign the document structure * the document should be rebuilt as a structured template **Go to:** * [How to Upload a Document for Electronic Signature](/user/dashboard/how-to-upload-a-document-for-electronic-signature.md) * [How to Add PDF Documents in a Template](/user/template-builder/template-editor/how-to-add-pdf-documents-in-a-template.md) #### Recipient experience settings Use recipient experience settings when recipients must see localized email, date, time, and number formats. **When to use:** Use recipient experience settings before sending an envelope or publishing a template flow. **Best for:** * external recipients * unregistered recipients * multilingual flows * flows with date and number values * public template link flows **Do not use this when:** * you need to validate a specific field value * you need to change the field type * the issue is about template access, not recipient display settings **Go to:** * [How to set up Recipient Experience in a Template](/user/template-builder/template/how-to-set-up-recipient-experience-in-a-template.md) * [How to Create and Configure a Template](/user/template-builder/template/how-to-create-and-configure-a-template.md) * [How to Create and Send an Envelope](/user/envelopes/how-to-create-and-send-an-envelope.md) ### Common mistakes Avoid these mistakes when you choose a collection method: * Using [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) when the value must be numeric or calculated. * Using [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) when values must come from a centrally managed directory. * Using static tables when recipients must add rows themselves. * Enabling **Search** for too many fields and making mailbox filtering harder. * Using a public template link when the process should run through [Integrations & API Access](/admin-panel/integrations-and-api-access.md). ### Quick decision guide Use these rules to choose faster: * If recipients type values, use [Text Field](/user/template-builder/template-dynamic-fields/text-field.md), [Number Field](/user/template-builder/template-dynamic-fields/number-field.md), [Currency Field](/user/template-builder/template-dynamic-fields/currency-field.md), or [Date Field](/user/template-builder/template-dynamic-fields/date-field.md). * If recipients choose values, use [Choice Field](/user/template-builder/template-dynamic-fields/choice-field.md), [Checkbox Field](/user/template-builder/template-dynamic-fields/checkbox-field.md), or [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md). * If values come from master data, use [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md). * If values depend on another selection, use [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md). * If files are required, use [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md). * If rows repeat, use [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md). * If values must follow a format, use [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md). * If users must search by collected data, enable **Search** only for the needed fields. * If the process starts outside DocStudio, use a [public template link](/user/template-links-and-public-envelope-creation/how-to-create-a-public-template-link.md) or [integrations and API access](/admin-panel/integrations-and-api-access.md). * If the PDF already has fillable fields, use [embedded PDF field import](/user/template-builder/template-editor/how-to-add-pdf-documents-in-a-template.md). * If recipients need localized emails or formats, configure [recipient experience settings](/user/template-builder/template/how-to-set-up-recipient-experience-in-a-template.md). ### Useful links #### Fields * [Template Dynamic Fields Overview](/user/template-builder/template-dynamic-fields/template-dynamic-fields-overview.md) * [Field masks (RegEx)](/user/template-builder/template-dynamic-fields/field-masks-regex.md) * [Text Field](/user/template-builder/template-dynamic-fields/text-field.md) * [Number Field](/user/template-builder/template-dynamic-fields/number-field.md) * [Currency Field](/user/template-builder/template-dynamic-fields/currency-field.md) * [Date Field](/user/template-builder/template-dynamic-fields/date-field.md) * [Choice Field](/user/template-builder/template-dynamic-fields/choice-field.md) * [Checkbox Field](/user/template-builder/template-dynamic-fields/checkbox-field.md) * [Dropdown Field](/user/template-builder/template-dynamic-fields/dropdown-field.md) * [Dictionary Field](/user/template-builder/template-dynamic-fields/dictionary-field.md) * [Lookup Field](/user/template-builder/template-dynamic-fields/lookup-field.md) * [File upload Field](/user/template-builder/template-dynamic-fields/file-upload-field.md) * [Dynamic Table Field](/user/template-builder/template-dynamic-fields/dynamic-table-field.md) * [Duplicate Field](/user/template-builder/template-dynamic-fields/duplicate-field.md) * [Formula Field](/user/template-builder/template-dynamic-fields/formula-field.md) * [Autonumber Field](/user/template-builder/template-dynamic-fields/autonumber-field.md) * [QR/barcode Field](/user/template-builder/template-dynamic-fields/qr-barcode-field.md) #### Template and recipient setup * [How to Create and Manage Dictionaries](/user/dictionaries/how-to-create-and-manage-dictionaries.md) * [How to Upload a Document for Electronic Signature](/user/dashboard/how-to-upload-a-document-for-electronic-signature.md) * [How to Add PDF Documents in a Template](/user/template-builder/template-editor/how-to-add-pdf-documents-in-a-template.md) * [How to set up Recipient Experience in a Template](/user/template-builder/template/how-to-set-up-recipient-experience-in-a-template.md) * [How to Create and Configure a Template](/user/template-builder/template/how-to-create-and-configure-a-template.md) * [How to Create and Send an Envelope](/user/envelopes/how-to-create-and-send-an-envelope.md) * [How to Configure Files Included in the Envelope Archive](/user/template-builder/template/how-to-configure-files-included-in-the-envelope-archive.md) * [How to Filter Envelopes](/user/envelopes/how-to-filter-envelopes.md) * [How to Customize the Envelope List](/user/envelopes/how-to-customize-the-envelope-list.md) #### Public and automated flows * [How to Create a Public Template Link](/user/template-links-and-public-envelope-creation/how-to-create-a-public-template-link.md) * [How Registered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-registered-users-can-create-an-envelope-via-a-template-link.md) * [How Unregistered Users Can Create an Envelope via a Template Link](/user/template-links-and-public-envelope-creation/how-unregistered-users-can-create-an-envelope-via-a-template-link.md) * [Integrations & API Access](/admin-panel/integrations-and-api-access.md) * [Application Tokens (API Access)](/user/authorization-and-security/application-tokens-api-access.md) * [Scenarios](/user/scenarios.md) * [How to Run a Scenario via Integration](/user/scenarios/running-scenarios/how-to-run-a-scenario-via-integration.md)