Skip to main content
Your organization permits audited Erdo staff views by default. An authorized staff member can explicitly open a one-hour read-only window and include a reason. This window grants no permission to send messages, change settings, approve work or edit pages.

Control staff views

An organization admin can change the setting in Settings, under Access. Choose Turn off staff view to refuse new staff views and close any active window. Erdo checks this preference on each protected read.

Review the access log

The Access section shows the latest 100 window openings with the staff member, optional reason and entry resource, start time and expiry. The audit entry is written before the window opens; a failed write leaves access closed. Entries remain stored after a window expires. An entry records the opening of a window; it does not count every read during that window. The existing support-access grant is separate. It remains time-limited and keeps its own controls.

How staff open a view

A staff member opens a view with a button on the thread or page they were sent to. There is no API, command-line or MCP tool for opening one: the decision is made by a person, in the product, each time. A thread or page can belong to more than one organization. A view opens in every owning organization together, and is refused if any of them has turned staff view off, in which case no entry is recorded for any of them. Each audit entry names the staff member from Erdo’s user records.