Storm's AI Form Fill permissions are managed by Org Controllers across three levels — workspace, template, and field — giving teams precise control over where Storm can operate and which fields it can update which forms support data capture, and which fields Storm can update. These settings help teams introduce AI workflows gradually while maintaining existing review and approval processes.
Who Can Control AI Form Fill?
AI Form Fill controls are managed exclusively by Org Controllers and approved administrators. Depending on your team's configuration, governance controls can be applied at three distinct levels: the workspace level, template level, and field level.
Workspace-Level Administration
Workspace-level controls allow teams to enable or disable AI Form Fill across an entire workspace. This widespread control is ideal for:
Testing AI Form Fill with selected pilot teams.
Gradually rolling out AI capabilities across corporate projects.
Restricting AI usage in highly regulated environments.
Evaluating software performance before broader organizational adoption.
If AI Form Fill is disabled at workspace level, users in that workspace will not be able to use AI Form Fill.
Template-Level Controls
Administrators can control AI Form Fill at the individual template level, choosing exactly which forms support automated draft generation based on risk and operational requirements.
Recommended Templates to Enable | Common Templates to Disable |
• Site diaries | • High-risk permits |
• Daily reports & walkthroughs | • Critical safety workflows |
• Inspections & pre-start briefings | • Approval-heavy processes |
• Meeting minutes | • Compliance-critical forms |
Field-Level Controls
Field-level configurations determine exactly which fields Storm can alter during data processing. This helps maintain oversight for sensitive workflows while still reducing manual data entry.
Allowed Actions: You can configure Storm to complete unstructured description fields, fill out tables, or map photos.
Restricted Actions: You can prevent Storm from updating critical review fields or writing to sensitive workflow sections.
Fields Storm Can Never Update
Regardless of your permission settings, Storm does not have the capability to:
Complete signature fields.
Sign approval workflows.
Bypass locked workflow sections.
Edit protected or locked fields (All standard required fields and approval workflows remain strictly mandatory).
Fill system-generated numbers (permit numbers, document numbers, GRNs)
Overwrite prefilled template content.
Human Review and System Confidence
AI Form Fill is strictly a drafting assistant; users remain entirely responsible for reviewing all submitted content. Storm does not automatically approve forms, sign workflows, or submit documents.
Before saving, users should:
Review all AI-generated text responses.
Verify critical financial, safety, or legal information.
Confirm the placement of attached photos.
Complete any missing mandatory fields.
Storm only fills fields when confidence is high enough. If Storm is unsure about spoken audio, photo interpretation, dropdown selections, or linked list matches, it leaves the fields blank for manual review instead of guessing.
When AI Form Fill is run on a form that already contains content, Storm appends new information only. Existing content is never rewritten or reformatted.
Activity Feed and Traceability
To maintain complete transparency, all AI Form Fill activity is permanently recorded in the Form Activity Feed. Depending on user permissions and workspace configurations, this traceable history includes:
Audio transcripts and uploaded photos.
Step-by-step AI processing steps.
Timestamps of the event.
Specific AI-generated updates and changes.
Current Limitations
AI Form Fill currently does not:
work inside Dashpivot Actions
analyse PDF, Word or Excel files
analyse video files
read other Dashpivot forms as context
Additional capabilities may be introduced in future Storm releases.