WritingPolicy and regulation

Connected campus work, with customer boundaries intact

A connected campus platform still needs firm access boundaries. Customer records stay scoped, and support access is visible to the school.

VeramastPublished Updated 3 min read

In this article

A search at one school returns that school’s records, and nothing crosses to another school.

One school, one address

#

Connecting registration, cameras, presence, and cases gives a campus team more context. It does not give that team access to another customer’s records. Each school or district has its own Veramast address, and each member’s access is limited to the organization and campuses their role permits.

One campus, seen from above. Stock footage.

A district member whose role covers several campuses can switch between those campuses. That access stays within the district’s organization. A campus at another customer does not appear, and a district role does not create access to it.

Two schools, each at its own address, each charting its own reads on its own scale. A support session shows on the one school it opened at, and a search across schools does not exist. Illustration with invented data.

There is no search across schools

#

A resource officer types a plate into search at 3:10 in the afternoon. The results are that school’s reads and no one else’s. The same holds for every report and every export: each covers one school, and none returns records from two. If two schools each read the same plate, each sees only its own read. A family with a student at each of two schools registers on each school’s own page, and neither school sees the other’s copy.

Veramast has no way to search for a plate across schools, for anyone, and that includes Veramast’s own staff. There is no such screen and no such report. A person at Veramast who wanted one would find nothing to ask for.

How Veramast staff see a school’s records

#

Veramast staff never sign in to a school’s account. When a school reports that a camera’s reads look wrong and the front office asks for help, a Veramast team member has to state a reason before looking at that school’s records, and the school’s owners receive an email naming the staff member and the reason.

The school can see that the access is open and why, and it can read the list afterward.

Inside a school

#

Not everyone at a school sees everything at that school. What a person can open follows their role, and only an owner can export records. When an export or a live view does happen, it asks for a reason and a second factor and is written into the history the owner can read.

When someone outside asks

#

A detective phones Veramast and asks whether a car was seen at any school on the platform. Veramast cannot answer that, because it has no cross-school view to consult. It refers the caller to the school, and the school’s owners are told that a request arrived. A parent, a lawyer, or another agency gets the same answer: ask the school, which decides.

The school owns its data, and Veramast handles it on the school’s behalf. If valid legal process compels Veramast directly, counsel is involved and the school is notified unless the law forbids it. There is no mechanism, and there will be none, by which an outside agency obtains a feed, a list, or a search across schools.

All writing

See it for your own school

A 30-minute call, with fictional data in every screen we show you. Expect a reply within 2 business days.

Request a demo