Appearance
Government Portal
County and municipal reviewers get one page: a read-only list of every event flagged as needing government permitting.
It exists because the alternative is emailing a spreadsheet to the county every few weeks. The reviewer logs in and sees the current list — always current, because it is the same booking data your office is working from.
Who it is for
The permitting officer, the fire marshal, the health department contact — whoever at the county needs to know what is happening on your grounds before it happens.
They are not a renter and not a portal contact. A reviewer is a member of your account with the Government role, and that role is corralled: no matter what they navigate to, they land on the review list. They never see bookings that are not flagged, and never see the rest of the app.
Owners and admins can open the same page, which is the easiest way to check exactly what your county contact is looking at.
Setting a reviewer up
Settings → Team → invite by email, and set their role to Government.
That is the whole setup. Per-side access does not apply — the Government role overrides it and sends them to the review list regardless.
Invite the person, not the department
A shared [email protected] login works, but a named person gets you someone to call. You can invite several reviewers to the same account.
Flagging a booking for review
On the booking form, under the event details:
- Requires county/government permitting — the checkbox that puts this booking on the reviewer's list
- Note for the government reviewer — optional free text, up to 2,000 characters
Once flagged, a banner appears on the booking: This booking requires government review before it can be confirmed.
The banner is a prompt for your staff, not a lock. Nothing in the product blocks the booking from moving forward — the sequencing is yours to enforce.
What the reviewer sees
One table, one row per flagged booking:
| Column | Contents |
|---|---|
| Event | Booking title and event type |
| Contact | The renter's primary contact name, email, and phone |
| Address | The renter's billing address |
| Event date | The start date, in your account's timezone |
| Expected size | Expected attendance |
| Space(s) | Which parts of the grounds are booked |
| Flags | Food and Alcohol chips where those are set on the booking |
| Notes | A button opening the note you wrote for the reviewer |
The Food and Alcohol chips come straight from the booking's own flags, which is usually the first thing a health or licensing reviewer looks for.
Ordering
Upcoming events first, soonest at the top — the ones a reviewer can still act on.
Past events are greyed out at the bottom, most recent first, so the list stays a record without burying what matters.
Declined and cancelled bookings never appear. Nobody should be reviewing an event that is not happening.
Empty state
No events are awaiting review right now.
What reviewers cannot do
The page is read-only. There is no approve, no deny, and no request-more-information action yet — a reviewer reads the list and responds to you however they already do, by phone or email.
They also cannot see money, contracts, documents, other renters, unflagged bookings, or anything on the Fairground side.
Approvals are not tracked in the product yet
Per-permit approve / deny / needs-info against a reviewer's decision is on the roadmap, not shipped. Today the portal answers "what is coming up that we need to permit" — recording the county's answer is still your process.
The page itself
It is a standalone page, not the admin app with things hidden. Your account name is in the header alongside the reviewer's name and a sign-out button, and there is no sidebar to get lost in. It works on a phone.
Related
- Bookings — where the flag and the note are set
- Team & Roles — inviting a reviewer
- Roadmap — what is planned for permit approvals