d680ade930
Staff naming policy: handles in all internal systems, real names only for outside agency business (legal, financial, vendor contracts). Updated Holly's Pterodactyl account details: unicorn20089@gmail.com, username unicorn20089, handle-only name fields. Created by Chronicler #29
1.8 KiB
1.8 KiB
FFG-STD-005 — Staff Naming Policy
Document Status: ACTIVE STANDARD
Created: 2026-03-10
Created By: Chronicler #29
Authority: Michael "Frostystyle" Krause
Version: 1.0
Applies To: All staff accounts, usernames, and internal communications
The Rule
Staff use handles (not real names) in all internal systems and communications.
Real names are used only when required for business with outside agencies (legal, financial, vendor contracts, etc.).
Examples
| Context | Use |
|---|---|
| Pterodactyl username | Handle |
| Discord display name | Handle |
| Wiki.js account | Handle |
| Firefrost email address | Handle (e.g. unicorn20089@firefrostgaming.com) |
| Internal docs / task attribution | Handle |
| Gitea commits | Handle |
| Legal filings | Real name |
| Vendor contracts | Real name |
| Payment processing | Real name |
| Outside agency communications | Real name |
Firefrost Staff Handles (Known)
| Handle | Role |
|---|---|
| frostystyle | Owner / The Wizard (Michael) |
| gingerfury | Community Manager / The Emissary (Meg) |
| unicorn20089 | Lead Builder (Holly) |
Account Creation Checklist
When creating accounts for new staff:
- Username = handle
- Display name = handle
- Email invitation sent to their personal email (not stored in systems beyond onboarding)
- Firefrost email address (when created) = handle@firefrostgaming.com
- Real name NOT entered into internal systems
Rationale
Handles are how the Firefrost community knows and interacts with staff. Consistency between community-facing and internal identities reduces confusion and maintains the community culture. Real name protection is also a staff privacy benefit.
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️