Approval Workflows

Two entirely different approval systems share the word "approval" — one gates schema changes, the other gates entry data. This page covers both.

ℹ️ Two Systems, Not One Schema/Revision Approval (this page's original scope) governs changes to a SmartTable itself — its fields, layout, or settings — before they go live. Entry-Level Approval Workflow (further down) is a separate, much more configurable system that governs whether a submitted entry's data gets signed off before it counts as final — multi-step chains, a submitter-chosen approver, and any-one-vs-all-must-approve per step. They don't share any configuration or data.

Part 1 — Schema/Revision Approval

When a non-admin edits a SmartTable's schema, the change is versioned but held back from users until an admin approves it.

Why It Exists

Every SharePoint refresh or settings change creates a new smarttable version (see Refreshing a SmartTable). If a SmartTable Admin (rather than a System Admin) makes that change, it doesn't go live immediately — it's held as a pending revision until someone with approval rights reviews it. This prevents an unreviewed schema change from silently altering a smarttable everyone else is actively using.

The versioning underneath

Each refresh creates a new entry-version row carrying its own full field schema and an approved flag, rather than overwriting the previous one in place. Every existing entry stays permanently linked to the specific version it was created under, so an unapproved (or even a later-rejected) revision can never retroactively change how an already-submitted entry's data is interpreted — only newly created entries pick up whichever version is currently approved. This is also why a rejected revision doesn't need any cleanup step: the smarttable simply keeps pointing at the last approved version, and the rejected one is just an unused row.

A brand-new smarttable (created for the first time from a SharePoint URL, not a refresh of an existing one) goes through the same approval gate at the smarttable level itself, not just at the version level — until approved, it exists but isn't live for anyone but its creator and approvers.

Status Icons

A small icon next to each smarttable name in the sidebar shows its approval state:

IconMeaning
✅ Green checkSmartTable is approved and live
🟠 Orange, clickableA new revision is pending approval (visible to approvers)
🟡 Yellow, not clickableSmartTable is not yet approved (visible to non-approvers, informational only)

Approving a Revision

  1. Click the orange pending-revision icon next to the smarttable name
  2. The Approve Revision modal opens
  3. Optionally add a comment
  4. Choose Approve or Reject
💡 Who Can Approve Approval rights belong to the System Admin account and any user granted user-management access — the same population that can manage users and licenses org-wide. See User Management.

Previewing a Pending Version

Before approving a new version, you can see exactly what it will look like. Open the SmartTable, then More → Preview. This option appears for SmartTable Admins and System Admins. The preview has two tabs:

  • Entry SmartTable: the entry form as it will be in the new version. Saving and submitting are turned off.
  • Display: the print layout (display sheet) of the new version, without any entry's data in it.

Both tabs show the latest version even if it isn't approved yet, so you can check a SharePoint change before it reaches users.

⚠️ Rejected Revisions A rejected revision does not delete the previous approved version — the smarttable keeps running on its last-approved schema until a new revision is submitted and approved.

Part 2 — Entry-Level Approval Workflow

A full multi-step sign-off chain for an entry's data, configured per SmartTable in Settings → Approval.

Turned on via Enable Multi-Step Approval in SmartTable Settings's Approval tab. Once enabled, a submitted entry doesn't count as finally approved until it's cleared every configured step, in order.

Entry-level Approval tab, showing Step 0 and two Approval Steps

Step 0 — the submitter-chosen approver

An optional first gate, separate from the numbered steps below: before submitting, the user filling in the entry must pick who should approve it first. That person approves, and only then do the configured Approval Steps begin. A separate toggle, Notify step 0 approver(s) when subsequent steps are approved, controls whether that person keeps getting notified as the entry moves through the rest of the chain or is only involved at the start.

Approval Steps

Add as many numbered steps as needed with + Add Step. Each step independently configures:

SettingDescription
ApproversWhich users can act on this step
Any one approves vs. All must approveWhether a single approver's decision clears the step, or every listed approver must individually approve before the step is considered done
Notify these approvers when later steps are approvedSame idea as step 0's notify toggle — keep this step's approvers in the loop as the entry moves further down the chain, or not

Steps run in order — step 2's approvers can't act until step 1 is fully cleared.

Interleaved Mode

A separate toggle: Interleaved Mode — Each data entry step requires approval before the next step unlocks. This only matters for a SmartTable where data entry itself happens in stages (multiple observations, or a multi-part form filled in over time) — with Interleaved Mode on, each data-collection stage must clear its own approval before the next stage of data entry even becomes accessible, rather than all data being entered first and the whole thing approved at the end as one lump. This is what a "step" being tied to a specific entry_step rather than the generic post-submission approval means under the hood.

ℹ️ Looking for SmartTable Steps? A data-entry "step" here refers to which observation of a repeated entry an approval gate is tied to — it doesn't restrict who can edit which fields. If you want different fields of the same entry assigned to different people, that's SmartTable Steps, a separate settings tab. The two can be combined: a SmartTable Step can have an interleaved approval gate configured after it, same as any entry_step here.

Approval Deadlines

Each approval step, and step 0, has an Approval deadline setting: the number of days approvers have to act, counted from when the entry was submitted. 0 means no deadline.

When a step has a deadline, the email asking approvers to act includes a Due line with the date and the time remaining, highlighted once it has passed. A missed deadline doesn't approve or reject anything by itself: the step keeps waiting for a decision.

Acting on an Approval

Approvers act the same way described on the Notifications page — via a notification with Approve/Reject action buttons, optionally with a comment and/or a signature attached to that specific decision.

Checking an Entry's Approval Status

In the entries table, the approval badge in the Action column shows progress as steps done out of total (for example 2/3). Click it to open the Approval Status panel, which lists each step with:

  • its status (approved, rejected or pending) and whether any one or all of its approvers must approve
  • who approved it and their comment
  • for a pending step, who it's still waiting on

If the entry was rejected and resubmitted, the panel also shows the earlier approval rounds at the top. The latest rejection is shown first, with who rejected it and why, and each round's full list of decisions can be expanded. Approvers see the same summary above their Approve and Reject buttons when they open the entry, so they know what was wrong last time.

When an Entry Is Fully Approved

Once the last step is approved, the entry is published. The person who created it is notified, and the Approval tab of SmartTable Settings controls who else hears about it:

SettingWhat it does
App Notification UsersThese users get an in-app notification that the entry was published
Email Notification UsersThese users get an email with the entry's PDF attached
Email SubjectThe start of the email's subject. The values of the SmartTable's PDF filename fields are added after it; the settings screen shows the final subject as you type.
Email Body and Email SignatureThe text of the email

To send that email again, for example after fixing a recipient's email address, open the entry's Approval Status panel and click Send Email. You can adjust the subject and body before sending; the resent email doesn't include the signature. The button appears once the entry is published and an email subject, body and recipients are set.

Which Email Address Approval Mails Come From

By default, approval mails are sent from the server's own mail account. To send them from your organization's own mailbox instead (for example approvals@yourcompany.com):

  1. The systemadmin account opens the profile menu → Communication Channels and clicks New Channel. Choose the provider (Office 365, Gmail or another SMTP server), enter the sender email, an optional sender name, and how to sign in: the mailbox password (for Gmail, an app password), or, for Office 365, an app registration with the Mail.Send permission (Tenant ID, Client ID, Client secret). Passwords and secrets are stored encrypted and never shown again; leave them blank when editing to keep them.
  2. Use Send a test mail (the paper-plane icon) to check the account works. The list shows the result of the last test, with the reason when it failed.
  3. A SmartTable admin opens SmartTable Settings → Approval and picks the channel under Approval Mail Sender → Send approval mails from, then saves.

The chosen channel sends that SmartTable's approver emails, its publish emails, and Send Email from the Approval Status panel. Changing it applies at once, also to entries already waiting for approval. If the channel is later turned off or deleted, the mails go out from the server's default account again; nothing is lost.

💡 Only the systemadmin manages channels SmartTable admins can choose among the channels the systemadmin has set up, but cannot see or change their passwords. The Communication Channels list shows which SmartTables use each channel.
💡 Editing a step's approvers clears stale notifications If you edit which users are listed as approvers on an active step, any pending (unactioned) notification tied to the old approver list is automatically cleared out — so a removed approver doesn't keep seeing a prompt for a decision they're no longer authorized to make.