Submission questions allow you to extend the default submission template with additional, structured questions that researchers must answer when submitting a report. By collecting this information upfront, you reduce back-and-forth during triage and make submissions easier to evaluate and reproduce.
Configure submission questions
⚙️Roles: Company Admin, Program Admin, Program Editor
You can configure submission questions at program level.
Open your program.
Go to Program details and find the Submission questions section.
Click Add question.
Choose the question type: Yes/No, Dropdown, Free text.
Enter the question text.
Choose whether the question is required or optional.
Click Save.
Once saved, the question is added to the default submission form for that program and can be completed by researchers. Once submitted, the answers are visible to every user who has access to the submission.
Submission question answers are exposed to integrations with some limitations. When creating Jira issues, the answers are fully included and visible in the issue content. They are also fully accessible through the Intigriti API for automation and reporting purposes. However, submission question answers can't be added to Slack notifications.
Question types
You can choose from different formats depending on the information you want to collect.
Yes or No
A simple toggle for binary questions, such as whether multi-factor authentication was enabled during testing.Dropdown
A predefined list of options researchers can choose from, for example the browser, operating system, device, or environment used during testing.Free text
An open field where researchers can provide details in their own words. This is useful for information such as test account names, tool versions, or specific reproduction notes.
Best practices
Ask only for information that directly supports triage or reproduction of the vulnerability.
Use clear and concise wording so researchers understand exactly what is expected.
Avoid duplicating information that is already captured in the standard submission form, such as URLs, severity, or proof of concept.
Limit the number of required questions to avoid unnecessary friction during submission. Focus on the one to three most important details.
Review submission questions periodically and remove or update questions that are no longer relevant.