Submission & Connectors¶
After a gate is approved, a submission workflow files the application. How it files depends on the authority, Scroll supports both live API submission and prepare-and-download packages, and chooses the right mode per connector.
Two submission modes¶
| Mode | When it's used | What happens |
|---|---|---|
| Live submission | The authority exposes a usable transactional API and credentials are configured. | Scroll submits directly and records the confirmation/reference. |
| Prepare & Download | No public submission API, or the portal requires interactive auth (UAE Pass, Absher, 2FA). | Scroll generates a formatted submission package (PDF) you upload manually to the portal. |
Many UAE/Saudi portals fall into the second category by design, e.g. DEWA, DED, DTCM, STA have no public transactional API, and SAMA, CMA, MOHRE, and MOJ require government identity sign-in that can't be automated. For these, Scroll does all the preparation and hands you a clean package for the final manual upload.
On the intake form¶
For workflows with a connector, the intake form shows a submission mode selector:
- Prepare & Download, no portal credentials needed; download a formatted package for manual upload.
- Live Submission, submit directly via the API (credentials required).
Workflows whose connector is manual-only show a banner indicating a package will be prepared.
The submission package (PDF)¶
The prepared package is a Claude-generated, print-ready PDF summarising the filled form data and analysis. Download it from the run with Download Submission Package. Filenames are sanitised for safe download across Arabic and Latin titles.
After submission¶
Whether live or manual, the run proceeds to its seal step, recording the outcome in the Provenance Vault. Live submissions store the authority's confirmation/reference number; prepared packages record that a package was generated for manual filing.