> ## Documentation Index
> Fetch the complete documentation index at: https://coredevelopments.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Developments Staff Guidelines, Roles, and Duties

> Guidelines for Core Developments staff: what each department does, how to communicate with users, and strict rules about never emailing schools.

These Staff Guidelines explain what every Core Developments department is responsible for, how staff should communicate with users, and the rules every team member must follow. All staff are expected to read these guidelines along with the [Staff and Email Policy](https://coredevelopments.org/staff-email-policy.md).

> [!WARNING]
>
> **Staff must never email, message, or contact schools, teachers, or school staff.** The only exception is a genuine emergency where someone's safety is at risk. In that case, tell leadership first whenever possible.

## Roles and Duties

> [card] Executive Administration
>
> Sets the direction of Core Developments, makes final decisions, approves public statements, and handles staff suspensions and removals.

> [card] Development
>
> Builds, tests, and maintains our Discord bots, websites, and software. Fixes bugs and keeps code secure.

> [card] Management
>
> Plans projects, sets timelines, assigns tasks, and keeps teams communicating with each other.

> [card] Design
>
> Creates the look and feel of our products and makes sure they are easy and safe to use for all ages.

> [card] Technology
>
> Runs servers, monitoring, and uptime. Posts maintenance and incidents on [Core Developments Status](https://systems.coredevelopments.org/).

> [card] Community
>
> Supports users, moderates our spaces, answers questions, and enforces our rules fairly and kindly.

> [card] Legal
>
> Maintains our policies, reviews legal and law enforcement requests, and handles privacy questions.

## Contacting Schools

**1. Do not contact schools**

Never email, message, call, or reach out to any school, teacher, or school staff member, using a Core Developments account or on behalf of Core Developments.

**2. Do not share information about minors**

Never share any information about a user, especially a minor, with a school.

**3. Emergencies only**

If someone's safety is at real risk, contact emergency services (**911**) first, then tell leadership. Only leadership may approve contacting a school in an emergency.

**4. Redirect school inquiries**

If a school contacts you, do not respond with user information. Forward the message to [legal@coredevelopments.org](mailto:legal@coredevelopments.org).

## Communicating With Users

* Only use your official `@coredevelopments.org` email for Core Developments work
* Be kind, patient, and professional, remembering that many users are kids and teens
* Never ask a user for their password, personal address, or private information
* Never send direct messages to minors outside official support channels
* Do not help users cheat on schoolwork, and never use AI tools to cheat
* Point users who are struggling to the [Mental Health Resources](https://coredevelopments.org/mental-health-resources.md) page

## Staff Conduct

> [accordion] Stay professional
>
> Treat users and other staff with respect. Harassment, discrimination, and abuse lead to removal.

> [accordion] Keep things confidential
>
> Do not share private project details, user data, or internal discussions outside the team.

> [accordion] Use your access responsibly
>
> Use moderation tools, bot controls, and admin access only for your assigned role.

> [accordion] Report problems
>
> Report security issues, safety concerns, or rule violations to leadership right away.

## Breaking the Guidelines

Breaking these guidelines can result in a warning, suspension of your email or other accounts, loss of staff access, or removal from the team. Core Developments makes the final decision.

> [card] [Questions for Leadership](mailto:admin@coredevelopments.org)
>
> Email [admin@coredevelopments.org](mailto:admin@coredevelopments.org) with any questions about these guidelines.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.