---
title: "Set Student Wall"
method: PUT
path: "/organizations/{org_id}/student-wall"
tags: ["organizations", "organizations"]
---

# Set Student Wall

`PUT /organizations/{org_id}/student-wall`

Raise or lower this school's student wall: {"students_walled": true}.

The rule lives in `services/student_wall.py`, written for Ingrid's under-18s
at TESI: a walled school's STUDENTS may reach only people who share one of
their schools, and only students — staff keep the whole product. What was
missing was any way to turn it on. The flag existed, the server enforced it,
the nav hid CommuniTea for it, and the only way to set it was an UPDATE
typed by an engineer against the database. A safeguarding control nobody can
switch on is a safeguarding control that is off, and TESI started enrolling
with it off.

Owner/admin, like every other school setting. That is a deliberate call over
"platform staff only": the person accountable for those students is the
coordinator, and making them file a ticket to protect their own minors is
how a term starts unwalled. Symmetric, too — a school that can raise the
wall can lower it. A coordinator locked out of undoing their own switch is
a support ticket by another route.

## Path parameters

- `org_id` string, required

## Headers

- `authorization` string, nullable

## Request body

- object

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/fluentea/apis/aurqa-language-learning-platform-refactored.md) · [All operations](https://skmtc.dev/fluentea/apis/aurqa-language-learning-platform-refactored/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fluentea/aurqa-language-learning-platform-refactored/revisions/78f314acd8bf/schema)