moderate visitor submissions

Visitor post submissions land in a moderation queue. They are not visible to anyone else until you act on them. Posts from your own team (org members) skip the queue.

the queue

In the admin dashboard, open moderation. Each pending post shows the title, body, the contact who submitted it, and how long ago it arrived. Newer submissions are at the top.

You can filter the queue by board if you want to focus on one surface at a time. The pending count is shown in the dashboard nav so you know when something is waiting.

actions

For each post you can:

• approve: moves it to approved moderation status. The post becomes visible on the board immediately.
• reject: moves it to rejected. The submitter does not get a notification; the post stays in the database but is hidden everywhere.
• mark as spam: moves it to spam. Same visibility effect as rejected, but spirby uses the spam signal for rate-limit and abuse tracking.

Bulk actions cover the same three options. Select multiple rows and apply to all in one shot.

why moderation exists

Every public-board action requires sign-in via a magic-link, so anonymous spam waves can’t reach the queue. Visitors are still rate-limited per (user, tenant) and per IP, and the queue is the trust boundary on top of that: nothing from outside your team becomes public without an admin’s say-so.

If you trust your audience, approve everything as it comes in. If your board is a target, lean on mark as spam for repeat offenders so the rate-limit signal tightens.