Custom submission fields allow you to capture vulnerability-specific information that can differ from one report to another. They are designed to track context that is unique to each submission, such as internal workflow states, custom risk scores, or follow-up actions.
💡Note: Custom submission fields are visible only to company users. To enrich the default submission form for researchers, use submission questions instead.
Custom submission fields provide a structured alternative to submission tags. This makes it easier to consistently track, filter, and report on submission-level data across programs, while keeping information standardized.
🔓 Subscriptions: Core, Premium, Enterprise
Configure custom submission fields
⚙️Roles: Company Admin, Program Admin
You can configure custom submission fields at program level.
Go to your program > More > Custom field.
Click Create a custom field.
Choose a type, such as text, dropdown, or toggle.
Enter a name for the field and define options if applicable.
Click Save.
Once saved, the field appears on all submissions for that program and you can manage it from the program’s Custom fields overview. Existing fields can be edited to update the field name or adjust the available options. If a field is no longer needed, it can be archived so it no longer appears on submissions or in exports.
Complete custom submission fields
⚙️Roles: Company Admin, Program Admin, Program Editor, Program member, Group member (only when the group is linked to the submission)
Custom submission fields are completed as part of the submission handling process.
Open a submission.
Find the Custom fields section.
Enter or select a value.
Save your input.
The information entered is stored with the submission and is visible to users who have access to that submission.
Best practices
Use custom submission fields for information that varies per report and supports internal workflows, such as internal states, risk scoring, or follow-up actions.
Keep field names and dropdown options clear and consistent to support reliable filtering and reporting across programs.
Avoid creating overlapping fields that capture similar information, as this can reduce data quality over time.
Review and clean up unused custom submission fields periodically by archiving fields that are no longer relevant.
Use submission questions instead of custom submission fields when information needs to be provided by researchers during submission.