Status Admin and access · Autessa Status Page
Access and audit trail
Autessa Status Page splits reading from writing. Status Admin is a staff-only app where every change runs with the signed-in person's own access and is stamped with who made it. The public status site has no direct access to your data at all: it reads through read-only tools that return public fields only.
- Status Admin (staff, signed in)Writes components, incidents, maintenance, changelog and settings with each person's own access.
- Your dataComponents, events, updates, changelog and settings tables.
- Two read-only toolsStatus and Changelog. Public fields only; approved entries only.
- Public status site (anyone)Reads and displays. Cannot write.
The problem it solves
A public page is a public attack surface
Status pages are seen by everyone, including people looking for a way in. If the public page can reach the same data the admin can, one mistake exposes staff emails, drafts or internal notes. The safer design keeps the public side read-only by construction and the writing side behind sign-in.
What you get
- Status Admin is shared only inside your company and requires sign-in.
- Every read and write in Status Admin runs with the signed-in staff member's own access.
- The public site reads through read-only tools, one for status and one for the changelog.
- Public answers carry public fields only: no staff emails, no source pull requests, no original AI drafts.
- Public text is rendered by a small, safe Markdown renderer that never inserts raw HTML.
- Incidents record who created them; updates record who posted them; changelog entries record who edited and approved them.
- Staff can sign out from the sidebar and switch light or dark.
How it works
How does access and audit trail work?
Staff sign in to Status Admin
Only people in your company with access to the app can open it.
They make a change
It is written with their own access and stamped with their email and the time.
The public page asks for status
Through a read-only tool that assembles the public view and leaves out anything internal.
Visitors read
They can view everything public and change nothing.
Every option
Who can reach what
| Option | What it does |
|---|---|
| Status Admin | Staff only, signed in, company sharing. |
| Public status site | Anyone. No sign-in, no table access, read-only tools. |
| Status tool | Components shown on the page, incidents, maintenance, updates and 90-day history; public fields only. |
| Changelog tool | Approved entries only: date, headline, release notes and publish time. |
| Stamps | Created by, posted by, edited by, approved by, with times. |
| Formatting | Headings, lists, bold, italic, code and https links; never raw HTML. |
Background reading: Building apps in the Autessa docs
Permissions
Who can do what?
| Who | Can |
|---|---|
| Visitors | Read public status, history and approved release notes. |
| Staff in Status Admin | Read and write components, incidents, maintenance, changelog and settings. |
| Company admins | Decide who in the company can open Status Admin, and manage the sealed GitHub token. |
Connected
How it connects to the rest of Status Page
FAQ
Questions about access and audit trail
Can visitors change anything on the status page?
No. The public site can only read, and has no access to your tables.
Are staff emails ever shown publicly?
No. Who posted each update is recorded in Status Admin, but public answers leave it out.
100% customizable, code and all
Make Autessa Status Page fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours