Skip to content

The Admin Dashboard

The dashboard is the home page for forms. It answers three questions: how responses are coming in across the org, what needs your attention today, and where every form is.

Counts run across the top. Below them, the list of forms fills the left side. The right-hand column holds three panels, from top to bottom: Delivery, the settings panel, and Needs attention.

The Sliick Forms Admin Dashboard: overview tiles across the top, the forms table filtered to one folder on the left, and the Delivery, settings and Needs attention panels on the right

A few upgrade tasks cannot happen automatically when you install a new version. If your org still has one to finish, the dashboard opens with this notice:

This org was upgraded from an earlier version. Run the following to finish the upgrade. You need to have the Customize Application permission.

  1. Read the list of steps in the notice.
  2. Click Finish upgrade steps.
  3. Each step then says what it did. If a step could not finish, it says why and how to do it by hand.

When every step is done, the notice reads Upgrade steps finished. and does not come back.

To run the steps you need the packaged Sliick Forms Admin permission set and the Customize Application permission. Only people who can edit forms see the notice.

Today there is one step, for orgs that first installed a version before 1.0: it adds the Column value that Columns blocks need. Orgs that first installed 1.0 or later never see the notice.

Five counts across the top:

TileWhat it counts
FormsEvery form, and how many are accepting responses
PublishedForms with a published version live
Responses · 7 daysResponses in the last seven days, not counting test responses
Failed processingResponses that could not be written to your records
ExperimentsA/B tests running now

When Failed processing is above zero, click it to open the responses console showing only the failed ones.

At the top of the right-hand column, the Delivery panel shows every place your forms are published. It has three tabs: Edge (your Sliick Edge address), Experience Cloud and Custom. Each tab has a status dot, so you can see what is set up without opening it. This is where you set your org-wide form addresses. See Choosing how to host a form.

The dashboard settings panel with Theme, File uploads and Email tabs, showing the daily upload limit for each form in megabytes

Under Delivery, a settings panel has three tabs:

  • Theme holds the Default theme, the look every form starts from. See Themes and branding.
  • File uploads sets how many megabytes of files each form can accept in 24 hours through Sliick Edge. Uploads on an Experience Cloud site or inside Salesforce do not count. Type a whole number and click Save, or leave it blank to use the default of 250. See File uploads.
  • Email chooses which organisation-wide email address form emails are sent from. It warns you if that address is not ready to send.

The Needs attention panel listing items to act on, each with a button such as Open log, Open in Builder or Review in Console

Under the settings panel, when something needs action, the Needs attention panel lists it:

  • responses that failed processing
  • a running experiment
  • a form that closes within seven days
  • a form at or near its response limit
  • a form holding responses that failed validation

Each row has a button to fix it: Review in Console or Open in Builder. The panel covers every form in the org, not just the forms your search or folder is showing.

One row is about the org, not a form: Refused. It appears when Sliick Edge, or your own system connected to Sliick Forms, sent responses in the last seven days that your org turned away. Those responses were not saved. The row names the form affected most and the most common reason, in plain words such as Request incomplete or malformed (from 1.2).

  • Show breakdown (labelled Breakdown before 1.2) lists every reason, including turned-away file uploads and save-for-later requests. Hover over a line to see the code the log records for it.
  • Open log opens the Integration refusals list view, where each entry names the form and the reason. The log records a limited number of entries each hour and each day, so it stays a manageable size.

On the left, under the Forms heading, is every form in the org, one row each:

ColumnWhat it shows
FormFrom 1.2, the form’s name, with its Form ID below it and, when the form has a public link, the link with a Copy button. Before 1.2, the External ID, with the form name below it. Click it to open the form in the Form Builder
StatusAccepting or Paused, then Published vn or Draft only, plus an Experiment badge while an A/B test runs
ResponsesHow many responses, with a failed badge if any failed processing
Last responseThe date of the latest response, or a dash
ActionsTwo icons. Submissions (the list icon) opens this form’s responses in the console. Duplicate (the copy icon) makes a paused copy of the form

Above the table you can:

  • Search forms by name or Form ID.
  • Filter by folder.
  • Sort by Recently edited (the default), Name A to Z, or Most responses.
  • Click New Form to create a form.
  • Click the upload icon, Import blueprint, to create a form from a blueprint file. See Blueprints.

When you pick a folder, a Rename folder button appears. Renaming moves every form in the folder. If you rename it to the name of a folder that already exists, the two folders are merged.

Note: the status badges here are for reading only. To pause or resume a form, open it in the builder. See Accepting responses.