The Admin Dashboard
The dashboard is the home page for forms. It answers three questions: how intake is going across the org, what needs your attention today, and where every form is.

Overview tiles
Section titled “Overview tiles”Five counts across the top:
| Tile | What it counts |
|---|---|
| Forms | Every form, with how many are accepting responses |
| Published | How many serve a pinned version |
| Responses in the last 7 days | Excluding test submissions |
| Failed processing | Submissions that failed |
| Experiments | A/B tests currently running |
The Failed processing tile is clickable when the count is above zero and takes you to the responses console already filtered to failures.
Delivery
Section titled “Delivery”Under the tiles, the Delivery panel answers one question: every place your forms are published. It has three tabs, Sliick Edge, Experience Cloud and Custom site, each with its own status dot so you can see what is set up without opening it. This is where the org-wide addresses are set, so it is covered with the hosting choice: see Choosing how to host a form.
Default theme
Section titled “Default theme”Beside Delivery, in the right-hand column, the Default theme panel holds the org-wide theme every form starts from. See Themes and branding.
Needs attention
Section titled “Needs attention”When there is anything to act on, a Needs attention panel lists it: failed submissions, a running experiment, a form closing within seven days, forms at or near their response cap, and forms holding responses that failed validation. Each row carries the action that resolves it, either Review in Console or Open in Builder. It is computed over every form in the org, not only the ones your current search and folder filter show.
One row is about the org rather than a form: Refused. It appears when an integration, meaning Sliick Edge or your own system calling the package’s REST routes, sent submissions in the last seven days that the org refused. Those responses were not saved. The row names the most affected form and the most common reason. Breakdown lists every reason, including refused file uploads and save-for-later requests, and Open log opens the Integration refusals list view of Form Log records. Each entry names the form and the reason. Entries are recorded up to a limit each hour and day, so the log stays manageable.
File uploads
Section titled “File uploads”The File uploads panel, under Default theme, sets how much a form accepts in a day over the REST path. Enter a whole number of megabytes and Save, or leave it blank for the default of 250. See File uploads.
The forms table
Section titled “The forms table”Below that, every form in the org, one row each:
| Column | What it shows |
|---|---|
| Form | The external ID on the first line and the form name below it. Click it to open the form in the Form Builder |
| Status | Accepting or Paused, plus Published vn or Draft only, plus an Experiment badge while an A/B test runs |
| Responses | The submission count, with a failed badge when any failed processing |
| Last response | The date of the most recent submission, or a dash |
| Actions | Submissions (open this form in the responses console) and Duplicate |
Above the table sits a Search forms box matching external ID or name, a folder filter, a sort control offering Recently edited (the default), Name A to Z, and Most responses, a New Form button, and an Import blueprint file picker.
When a real folder is selected, a Rename folder button appears. Renaming moves every form in the folder, and renaming onto a folder that already exists merges the two.
Note: the status badges here are read-only. Pausing or resuming a form is done in the builder. See Accepting responses.