Pupils using vGSW may occasionally need help with a system or a situation on campus. A door may fail to respond, an armguard may be unrecognised, or an activity may require Faculty, administrative, or Porter attention. Clear reporting helps the School identify the problem and respond appropriately.

Choose the route that fits the concern. Security Consoles provide campus reporting points, the School's Bug Thread records persistent technical problems, and an instructor or administrator should be told promptly when an issue affects attendance or another official record. An urgent disruption during an activity should be brought to the person directing it or the appropriate authority present.

Security Consoles

Security Consoles are located across the campus regions so pupils can report concerns without travelling to a particular office. They may be used to report disruptive conduct, inappropriate objects, broken systems, concerns about a space, or other matters requiring review.

Give the location, time, names involved if known, and a concise description of what occurred. The console is an official reporting tool and should be used honestly and carefully. Submitting a report allows the matter to be reviewed; it should not be assumed that a particular official is immediately available to respond.

Porters and the Porter's Office

The School may appoint Campus Porters to assist with order, access, disruptions, reports, and the daily operation of vGSW. Porters serve under the direct authority of the Headmaster.

The Porter's Office is near the Ritual Space and can be reached by the nearby stairs. It may not always be occupied. When a Porter is unavailable, Security Consoles remain the preferred campus route for reporting a concern that needs attention.

Porters have full moderation authority on campus. Their delegated duties may include giving directions, issuing warnings, removing people from spaces, issuing demerits where appropriate, and formally recommending suspension, expulsion, or other corrective action. These campus powers remain subject to the Headmaster's authority and the School's disciplinary framework.

Treat a Porter's direction as official School direction while on campus. A pupil who disagrees should comply at the time and seek review afterward by contacting the Headmaster at Headmaster@GreySchool.com. Public argument, refusal to follow instructions, or attempts to undermine the Porter's authority become separate conduct concerns.

Technical Issues

Technical problems may involve armguards, uniforms, the Hub, access points, doors, class objects, Lodge or Patron systems, Presence Beacons, Sanctums, kiosks, terminals, or other tools. Do not force, bypass, reset, or manipulate a system unless Faculty, Administration, or a Porter acting within their authority instructs you to do so.

If a system fails to respond, check that the required tools are worn and current. Try again calmly where appropriate. If the problem continues, report it through The Bug Thread, describing the object or system, its location, the action attempted, and any response received. Repeated guessing can make a problem harder to identify.

When an issue affects attendance, Campus Standing, class participation, or another record, also notify the instructor, host, appropriate administrator, or Porter as soon as possible. Reports made near the time of the problem give the School a better opportunity to check what happened.

Access Problems

Some areas or tools require a current armguard, a particular role, Lodge membership, Campus Standing, class enrolment, event participation, or Faculty authorisation. Check the stated requirements first if access is denied.

If the denial appears to be an error, report it instead of bypassing the restriction. Include the location or object, what you attempted, any message received, and your current role or reason for expecting access. That information helps distinguish an eligibility requirement from a technical fault.

Conduct Concerns

Reporting channels are also available for harassment, griefing, impersonation, inappropriate avatar presentation, misuse of objects, disruptive scripts, unauthorised access, interference with classes or events, and other conduct that prevents a space from serving its purpose.

Keep reports factual and focused. Explain what happened, when and where it happened, who was involved if known, and its effect on the activity or space. Avoid speculation, exaggeration, or public argument while the matter is being reported.

During an urgent class or event problem, notify the instructor, host, Faculty member, Porter, or administrator present. If none is immediately available, use a Security Console or another approved reporting channel.

Reports and Review

Submitting a report does not guarantee a particular outcome. Porters and Administration may examine the information, check records, speak with those involved, inspect a location, reset a tool, remove an object, correct access, issue a warning, or take other appropriate action.

Some matters are resolved through maintenance or correction without visible disciplinary action. Others require conduct review. Pupils should allow that process to take place and avoid using reporting systems to pursue personal disputes.

False, malicious, or careless reports undermine reliable campus support. Provide accurate information to the best of your ability and make reports in good faith.

Prompt, useful reporting helps everyone who shares vGSW. It allows faults to be repaired and conduct concerns to be assessed while giving the School the information it needs to make a responsible decision.