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

# Staff Rules and Email Account Policy at Core Developments

> Rules for Core Developments staff and @coredevelopments.org email accounts, including acceptable use, suspension rights, and our policy on contacting schools.

This policy sets the rules every Core Developments staff member must follow, including how official `@coredevelopments.org` email accounts may be used. All staff agree to this policy when they join the team or receive an email account.

> [!WARNING]
>
> **Core Developments reserves the right to suspend or terminate any** `@coredevelopments.org `**email account at any time, for any reason, with or without notice.** That decision rests solely with Core Developments.

## Email Accounts

### Ownership

All `@coredevelopments.org` email accounts, and everything sent or stored in them, belong to Core Developments. An email account is provided to help you do your role and is not a personal account.

### Acceptable Use

> [card] Do
>
> * Use your account for Core Developments work only
> * Communicate professionally and respectfully
> * Keep your password private and use two-factor authentication
> * Report suspicious emails or security issues right away

> [card] Do Not
>
> * Share your login with anyone
> * Use your account for personal sign-ups or business
> * Send spam, harassment, or inappropriate content
> * Speak on behalf of Core Developments without approval

### Suspension and Removal

Core Developments may suspend, restrict, or delete any email account at any time and for any reason. This includes, but is not limited to:

* Breaking these rules or our [Terms of Service](https://coredevelopments.org/terms-of-service.md)
* Leaving or being removed from the team
* Inactivity
* Security concerns

When an account is suspended or removed, you lose access to it and its contents. Core Developments is not required to give a reason.

## Contacting Schools

> [!NOTE]
>
> **Core Developments does not email schools.** Staff must not contact any school, teacher, or school staff using a Core Developments email account or on behalf of Core Developments.

The only exception is a genuine **emergency**, such as a risk to someone's safety. In an emergency, staff should notify Core Developments leadership first whenever possible.

## Staff Rules

> [accordion] 1. Professional conduct
>
> Treat community members, users, and other staff with respect at all times. Harassment, discrimination, and abuse are not tolerated.

> [accordion] 2. Confidentiality
>
> Do not share private project information, user data, or internal discussions outside the team.

> [accordion] 3. Representing Core Developments
>
> Only make public statements, promises, or agreements on behalf of Core Developments if leadership has approved them.

> [accordion] 4. Account security
>
> Protect every Core Developments account you have access to, including email, Discord, and project tools. Never ask a user for their password.

> [accordion] 5. Bots and tools
>
> Use staff access to bots and tools only for your assigned role. Do not misuse moderation powers.

> [accordion] 6. Following decisions
>
> Follow reasonable directions from leadership and your department lead.

## Breaking the Rules

Breaking this policy can lead to a warning, suspension of your email or other accounts, loss of staff access, or removal from the team. Core Developments decides the outcome.

## Questions

Staff with questions about this policy can email [admin@coredevelopments.org](mailto:admin@coredevelopments.org).


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