Safeguarding

A named officer, a way to report, and a record of every look

Access to sensitive material is possible, recorded, and impossible to do quietly.

The safeguarding page of a SeeUAll organisation, naming the responsible officer and the reporting route.
A named officer, a route to report, and a record of every look.

What it is

An organisation names who is responsible. There is a route for reporting something, and the material a report concerns can be opened by that person — only on a report, and never without an entry saying who looked and why.

The design principle

Safeguarding features fail in one of two ways: nobody can reach what they need, or anybody can reach anything. The answer to both is that access exists and is always recorded. An unlogged look is the thing that turns a safeguarding tool into a surveillance tool.

Read next

  • Moments

    Off unless the organisation turns it on, never between staff and a member, sealed at rest — and reportable, which is the whole reason it is built this way.

  • A log of what was done

    Every moderation action, role change and integration change, with who did it — and the database refuses to let it be altered.

  • Who may do what

    Owner, administrator, host and member — checked at the door, in the page, and in the database, rather than only in the menus.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    Safeguarding — SeeUAll · SeeUAll