Submission Data lets Intellistack Streamline save the data produced during workflow sessions. Authorized users can review the steps that ran, inspect the data produced by each step, and open linked files from the project's sessions table.
This feature is in Early Access and is available to all customers. You can use it today while we gather feedback and continue improving it. Features, availability, and how it’s included in plans may change before general release.
Who Has Access?
Default role access is:
- Admin: Configure Submission Data for the organization and individual projects, view Submission Data, mark fields as Sensitive, and reveal sensitive values.
- Manager: Enable or disable Submission Data for individual projects and view Submission Data.
- Builder: View Submission Data.
- Operator: View Submission Data.
- End User: No Submission Data permissions.
You can grant these permissions to other users through Custom Roles. A user can view Submission Data only for projects they already have access to.
Note: Manager, Builder, and Operator can view Submission Data, but they cannot reveal sensitive values or mark fields as Sensitive by default. Permission to view Submission Data does not automatically include permission to manage sensitive data.
Key Capabilities
Organization and project controls
- Enable Submission Data as the default for projects created afterward.
- Enable Submission Data separately for projects that already exist.
- Stop collection for one project, or stop collection for every workflow by turning off Save submission data, without deleting data already stored.
- Set an organization-level retention policy for Submission Data.
Session and step data
- View data from completed, failed, canceled, and expired sessions.
- Review the steps that ran during a session.
- Open a step to see its field labels, data types, and submitted values.
- View repeating groups as tables and open groups nested inside other groups.
- See the workflow version and available session and step details connected to the stored data.
Files
- Open uploaded files through the file storage service integrated with the workflow.
- Open files generated by the workflow through links to the Document Repository.
Sensitive data
- Automated classification helps identify fields likely to contain sensitive data and masks those fields by default. It may not identify every sensitive field.
- Reveal one sensitive value at a time when your role allows it.
- Mark a field as Sensitive when it should be masked.
Deletion
- Delete one session or select multiple sessions for bulk deletion.
- Delete the Submission Data associated with a deleted session.
Enable Submission Data for your organization
- In the left navigation, under Organization, select Security.
- Open Submission data.
- Turn on Save submission data.
- To set how long Submission Data is kept, open Data retention on the Security page.
Available options are 30, 60, 90, 180 days, 1 year, 2 years, 5 years, 7 years or custom days.
When you change the retention policy, Streamline recalculates expiration dates for existing Submission Data. This processing may take time. Streamline deletes records after their expiration date.
Important: Enabling Submission Data for the organization does not enable projects that already exist. Enable each existing project separately.
Turning off Save submission data stops collection for every workflow. It stops collection for existing projects and prevents collection for new projects. It does not delete data already stored.
Enable Submission Data for an existing project
- Open the existing project.
- Open the project Settings.
- Turn on Submission Data for the project.
- Save changes.
Submission Data is collected only from sessions that run after the project is enabled. Data from earlier sessions is not added automatically.
View data from a session
- Open the project.
- Open the project's sessions table.
- Find a completed, failed, canceled, or expired session.
- Select View data.
- Review the list of steps that ran during the session.
- Select a step to view its stored fields and values.
For nested groups, open a group to view its contents. Use the navigation links to return to each earlier group.
Note: Sessions still in progress are not available. Submission Data appears after a session ends with a supported status.
Reveal a sensitive value
Sensitive values are masked by default.
- Open the step containing the masked value.
- Select the reveal action for that field.
- Review and confirm the reveal message.
- View the revealed value.
You must confirm each reveal separately. There is no option to reveal all sensitive values at once.
Mark a field as Sensitive
If your role allows it, mark or clear a field's Sensitive classification from the workflow builder. These settings apply to the published workflow.
- Open the workflow in the builder.
- Next to the workflow name, open the menu.
- Select Data classification.
- In Sensitive data classification, expand the step that contains the field.
- In the Sensitive column, select the checkbox to mark the field. Clear the checkbox to remove the Sensitive classification.
- Select Save changes.
Marking a field as Sensitive updates stored records and masks them. Clearing a Sensitive classification leaves previously stored records masked.
The panel shows the published workflow version, the classifier status, and when the classifier last ran. An icon beside a field shows who last changed that field's classification and when.
Changes saved confirms that the classification was saved.
Note: Classification settings apply to the published workflow. Draft submissions are classified separately and can't be customized, so their results may differ once published.
Understand published and draft classifications
When a workflow is published, automated classification helps identify fields likely to contain sensitive data and saves the results for that workflow version. The classification settings show results for the latest published version, even when the builder currently displays a draft.
When you run a test session from a draft, Streamline classifies the data stored for that session. This classification is provisional:
- It covers only the steps and fields included in that test session.
- It protects the data stored for the test session.
- It does not replace the published classification shown in the settings.
- It does not inherit manual classification changes from the latest published version.
Delete Submission Data
To delete Submission Data, delete the session from the project's session list. You cannot delete individual fields separately from the session.
Delete one session
- Open the project.
- In the session list, select the checkbox next to the session.
- Select Delete.
- In Delete 1 session?, select Delete session.
The confirmation states that this terminates the session and any data collected, then removes them from the session list. This action cannot be undone.
Delete multiple sessions
- Open the project session list.
- Select the checkbox for each session. To select every session on the current page, select the checkbox in the column header.
- Select Delete.
- Review the confirmation. The title shows the number of sessions, for example Delete 10 sessions?.
- Select Delete session.
The confirmation states that this terminates those sessions and any data collected, then removes them from the session list. This action cannot be undone.
Note: The header checkbox selects only the sessions on the current page. Sessions on other pages stay unselected.
Important: You cannot delete individual fields or other parts of the collected data separately from the session.
Feature Considerations
Collection and availability
- Enabling Submission Data for the organization does not enable existing projects.
- Enabling an existing project does not add data from sessions that ran while Submission Data was off.
- Data from sessions still in progress is not available in the Viewer.
Viewing and reporting
- Stored values cannot be edited.
- Exporting Submission Data is not supported.
- Submitted values cannot be searched from the Viewer.
- Submission Data fields cannot be added as columns in the project sessions table.
- Cross-project reporting, pivot tables, advanced reporting, and saved views are not included.
Files
- Submission Data stores links to uploaded and generated files, not the files themselves.
- An uploaded file is accessible only when a file storage service is integrated with the workflow.
- Generated files follow the Document Repository retention policy, which is separate from the Submission Data retention policy.
- Bulk file download and file export are not supported.
Sensitive-field classification
- Automated classification helps identify fields likely to contain sensitive data. It may not identify every type or instance of sensitive data. Customers remain responsible for marking known sensitive fields and for configuring workflows and access controls for the information they collect.
- Automatic classification may mark a field as Sensitive when it is not or miss a field that should be Sensitive.
- Streamline evaluates what a field appears designed to collect. It does not inspect general text fields for sensitive information entered into their values.
- Customer-specific sensitive categories are not automatically detected.
- A later automatic classification does not remove an existing Sensitive classification.
- Marking a field as Sensitive updates stored records and masks them.
- Clearing a Sensitive classification leaves previously stored records masked.
Data reuse
- Submission Data cannot be used as a Data Search source.
- Cross-workflow prefill is not supported.
- Submission Data is not automatically mapped or synchronized to external systems.
Privacy and security
Intellistack will collect and store structured submission data from enabled workflows in your organization. Stored submission data is retained until deleted by an authorized user or otherwise removed in accordance with applicable retention requirements.
To help protect Submission Data:
- Data is encrypted at rest.
- Streamline uses automated classification to identify and mask fields likely to contain sensitive data.
- A user whose role allows it can mark a known sensitive field as Sensitive. Values in a field marked Sensitive are masked.
- Access to masked values is permission-controlled. Authorized users must take an affirmative action to reveal masked values, and reveal events are logged.
- Access permissions and relevant configuration changes are controlled and auditable.
- Uploaded files remain in the configured file-storage location; Submission Data stores a reference to the file rather than the uploaded file itself.
- Automated classification may not identify every type or instance of sensitive data. Customers remain responsible for configuring workflows and access controls appropriately for the information they collect and for complying with their applicable legal, regulatory, and organizational requirements.
Troubleshooting
A new project is not collecting Submission Data
Confirm that:
- Save submission data is turned on under Organization > Security > Submission data.
- The project was created after Save submission data was turned on.
An existing project is not collecting Submission Data
Confirm that Submission Data is enabled in the project's settings. Enabling the organization setting does not enable projects that already existed.
View data is unavailable
Confirm that:
- Submission Data is enabled for the project.
- The session ended as completed, failed, canceled, or expired.
- Your role allows you to view Submission Data.
- You have access to the project.
A session has no stored data
The project may not have been enabled when the session ended, the session may still be running, or storage may have failed. Contact our Support team if the problem persists.
A field is masked
Sensitive fields are masked by default. If your role allows you to reveal sensitive values, use the field's reveal action and confirm the reveal. Otherwise, contact an organization Admin about your role permissions.
A field should be masked but is not
If your role allows it, open the workflow in the builder, select Data classification, and mark the field in Sensitive data classification. Then select Save changes.
A linked file does not open
Confirm that:
- The workflow has an integrated file storage service for uploaded files.
- You have permission to access the file.
- The file still exists in the connected file storage service or Document Repository.
- The generated file was not deleted by another user or by the organization's data deletion policy.
Data remains after Submission Data is turned off
This is expected. Turning off Save submission data stops collection for every workflow. Turning off Submission Data for a project stops collection for that project. Neither action deletes data already stored. Delete the associated sessions to remove their Submission Data.
Summary
Submission Data stores workflow-session data and makes it available from the project's sessions table. Configure the organization default from Security, set retention from Data retention on that page, enable existing projects from their project settings, and use Custom Roles to control access.
Comments
0 comments
Please sign in to leave a comment.