From 16ccf9ba7d159f3453301532e10fbde7f0a2d33b Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 17 Feb 2026 22:48:10 +0000 Subject: [PATCH] cleanup: Remove duplicate department structure directory Removed docs/tasks/department-structure-&-access-control-matrix/ which was a duplicate of docs/tasks/department-structure/ The newer department-structure/ directory follows FFG-STD-002 task documentation standard and is more comprehensive. This resolves the duplicate commit issue visible in git history. --- .../README.md | 36 -- .../access-control-matrix.md | 414 -------------- .../department-structure.md | 521 ------------------ 3 files changed, 971 deletions(-) delete mode 100644 docs/tasks/department-structure-&-access-control-matrix/README.md delete mode 100644 docs/tasks/department-structure-&-access-control-matrix/access-control-matrix.md delete mode 100644 docs/tasks/department-structure-&-access-control-matrix/department-structure.md diff --git a/docs/tasks/department-structure-&-access-control-matrix/README.md b/docs/tasks/department-structure-&-access-control-matrix/README.md deleted file mode 100644 index a2fc1fc..0000000 --- a/docs/tasks/department-structure-&-access-control-matrix/README.md +++ /dev/null @@ -1,36 +0,0 @@ -# Department Structure & Access Control Matrix - -**Status:** Planning -**Priority:** Tier 2 - Organization -**Time:** 1-2 hours -**Last Updated:** 2026-02-16 - -## Overview -Define department structure and access control matrix for staff organization. Foundation for Wiki.js permissions and role-based access. - -## Departments -- Operations (Michael/Meg) -- Game Admins -- Community Moderators -- Content Creators -- Support Team - -## Access Matrix -Create comprehensive matrix defining: -- What each role can access -- What each role can modify -- Escalation paths -- Emergency overrides - -## Deliverables -- Department structure document -- Access control matrix -- Wiki.js permission mapping -- Onboarding procedures - -## Success Criteria -- βœ… Departments defined -- βœ… Access matrix complete -- βœ… Ready for Wiki.js implementation - -**Fire + Frost + Foundation** πŸ’™πŸ”₯❄️ diff --git a/docs/tasks/department-structure-&-access-control-matrix/access-control-matrix.md b/docs/tasks/department-structure-&-access-control-matrix/access-control-matrix.md deleted file mode 100644 index 607b8a5..0000000 --- a/docs/tasks/department-structure-&-access-control-matrix/access-control-matrix.md +++ /dev/null @@ -1,414 +0,0 @@ -# Firefrost Gaming - Access Control Matrix - -**Version:** 1.0 -**Status:** Planning -**Last Updated:** 2026-02-17 -**Purpose:** Technical permissions mapping for all systems and roles - ---- - -## How to Read This Matrix - -**Format:** Role β†’ System β†’ Permission Level - -**Permission Levels:** -- ❌ **No Access** - Cannot view or interact -- πŸ‘οΈ **Read Only** - Can view, cannot modify -- ✏️ **Read/Write** - Can view and modify assigned resources -- πŸ”§ **Admin** - Can view, modify, and configure -- πŸ”‘ **Root** - Full control, including security and infrastructure - ---- - -## Discord Access Matrix - -| Role | General Channels | Staff Channels | Moderation Tools | Server Settings | Roles/Permissions | -|------|-----------------|----------------|------------------|-----------------|-------------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Moderators** | ✏️ | πŸ‘οΈ | πŸ”§ (kick, timeout, mute) | ❌ | ❌ | -| **Game Admins** | ✏️ | πŸ‘οΈ | ❌ | ❌ | ❌ | -| **Builders** | ✏️ | πŸ‘οΈ (builder channels) | ❌ | ❌ | ❌ | -| **Social Media** | ✏️ | πŸ‘οΈ (social channels) | ❌ | ❌ | ❌ | -| **Support Team** | ✏️ | πŸ‘οΈ (support channels) | ❌ | ❌ | ❌ | -| **Subscribers** | ✏️ | ❌ | ❌ | ❌ | ❌ | - -**Notes:** -- Moderators cannot ban (escalate to Founding Partners) -- Staff channels segmented by department -- All staff can see announcements channel - ---- - -## Pterodactyl Panel Access Matrix - -| Role | Panel Access | Server List | Console Access | File Manager | Server Settings | User Management | Node Management | -|------|--------------|-------------|----------------|--------------|-----------------|-----------------|-----------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ All servers | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Game Admins** | πŸ”§ | πŸ‘οΈ Assigned only | πŸ”§ Assigned only | ✏️ Configs only | ✏️ Limited | ❌ | ❌ | -| **Builders** | ✏️ | πŸ‘οΈ Creative servers | ✏️ Creative only | ✏️ Creative only | ❌ | ❌ | ❌ | -| **Others** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | - -**Specific Permissions - Game Admins:** -- βœ… Start/stop/restart server -- βœ… View console logs -- βœ… Send console commands -- βœ… Edit server.properties, mod configs -- βœ… Access server files (read/write) -- ❌ Delete servers -- ❌ Allocate resources (RAM/CPU) -- ❌ Change server owner -- ❌ Access other servers - -**Specific Permissions - Builders:** -- βœ… Full access to assigned creative servers -- βœ… Install/remove mods (creative only) -- βœ… Upload/download world files -- ❌ Access production servers -- ❌ Change resource allocation -- ❌ Access other builders' servers - ---- - -## Wiki.js Access Matrix - -| Role | Public Pages | Staff Area | Ops Docs | Community Docs | Content Docs | Admin Panel | -|------|-------------|-----------|----------|----------------|--------------|-------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Game Admins** | πŸ‘οΈ | πŸ‘οΈ | ✏️ | πŸ‘οΈ | πŸ‘οΈ | ❌ | -| **Moderators** | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ | ✏️ | πŸ‘οΈ | ❌ | -| **Builders** | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ | ✏️ Builder section | ❌ | -| **Social Media** | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ | ✏️ Social section | ❌ | -| **Support Team** | πŸ‘οΈ | πŸ‘οΈ | πŸ‘οΈ FAQ only | πŸ‘οΈ | πŸ‘οΈ | ❌ | -| **Subscribers** | πŸ‘οΈ Subscriber wiki | ❌ | ❌ | ❌ | ❌ | ❌ | - -**Page Structure:** -``` -/public (subscribers.firefrostgaming.com) -β”œβ”€ Getting Started -β”œβ”€ Modpack Guides -β”œβ”€ Rules -└─ FAQ - -/staff (staff.firefrostgaming.com) -β”œβ”€ /operations -β”‚ β”œβ”€ Server Management -β”‚ β”œβ”€ Troubleshooting -β”‚ └─ Procedures -β”œβ”€ /community -β”‚ β”œβ”€ Moderation Guide -β”‚ β”œβ”€ Event Planning -β”‚ └─ Conflict Resolution -β”œβ”€ /content -β”‚ β”œβ”€ /builders -β”‚ β”‚ β”œβ”€ Design Guidelines -β”‚ β”‚ └─ Workflow -β”‚ └─ /social-media -β”‚ β”œβ”€ Brand Voice -β”‚ └─ Content Calendar -└─ /general - β”œβ”€ Onboarding - β”œβ”€ Team Directory - └─ Policies -``` - ---- - -## Gitea (Operations Manual) Access Matrix - -| Role | Read Access | Write Access | Admin Access | -|------|------------|--------------|--------------| -| **Founding Partners** | πŸ”‘ All repos | πŸ”‘ All repos | πŸ”‘ | -| **Game Admins** | πŸ‘οΈ Operations docs | ❌ | ❌ | -| **All Other Staff** | ❌ | ❌ | ❌ | - -**Notes:** -- Operations manual is primarily internal -- Claude instances have scoped access as appropriate -- Wiki.js is the staff-facing documentation platform - ---- - -## Uptime Kuma (Monitoring) Access Matrix - -| Role | Dashboard View | Alert Config | Service Config | Admin | -|------|---------------|--------------|----------------|-------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Game Admins** | πŸ‘οΈ All services | ❌ | ❌ | ❌ | -| **All Other Staff** | πŸ‘οΈ Public status page | ❌ | ❌ | ❌ | - -**Public Status Page:** `status.firefrostgaming.com` -- Shows server status for all game servers -- No authentication required -- Read-only - ---- - -## Paymenter (Billing) Access Matrix - -| Role | Customer View | Order Management | Financial Reports | System Config | -|------|--------------|------------------|-------------------|---------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **All Other Staff** | ❌ | ❌ | ❌ | ❌ | - -**Notes:** -- Billing is strictly founding partners only -- No delegation of financial access -- Customer data is protected - ---- - -## Whitelist Manager Access Matrix - -| Role | Access | Add Players | Remove Players | Toggle Whitelist | Bulk Operations | -|------|--------|-------------|----------------|------------------|-----------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Game Admins** | ✏️ | ✏️ Assigned servers | ✏️ Assigned servers | ✏️ Assigned servers | ✏️ Assigned servers | -| **Support Team** | ✏️ (if approved) | ✏️ Request only | ❌ | ❌ | ❌ | - -**Workflow for Support Team:** -1. Receive whitelist request from player -2. Verify subscription status in Paymenter (read-only link) -3. Submit request to Game Admin or use Whitelist Manager if granted access -4. Confirm to player - ---- - -## Server SSH Access Matrix - -| Role | Command Center | TX1 | NC1 | Ghost VPS | Billing VPS | Panel VPS | -|------|---------------|-----|-----|-----------|-------------|-----------| -| **Founding Partners** | πŸ”‘ root | πŸ”‘ root | πŸ”‘ root | πŸ”‘ root | πŸ”‘ root | πŸ”‘ root | -| **Server Ops** (future) | πŸ”§ sudo limited | πŸ”§ sudo limited | πŸ”§ sudo limited | ❌ | ❌ | ❌ | -| **All Others** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | - -**Server Ops Sudo Permissions (Future):** -- βœ… Service restart (systemctl restart) -- βœ… Log viewing -- βœ… Process monitoring (htop, top) -- βœ… Disk usage checks -- ❌ User management -- ❌ Network configuration -- ❌ Firewall modifications -- ❌ Package installation (escalate to Founding Partners) - ---- - -## Social Media Accounts Access Matrix - -| Role | Buffer/Scheduler | Discord (Official) | Twitter/X | Instagram | TikTok | YouTube | Reddit | -|------|-----------------|-------------------|-----------|-----------|--------|---------|--------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ Owner | πŸ”‘ Owner | πŸ”‘ Owner | πŸ”‘ Owner | πŸ”‘ Owner | πŸ”‘ | -| **Social Media Team** | ✏️ Scheduler only | ✏️ Post only | ✏️ Via Buffer | ✏️ Via Buffer | ✏️ Via Buffer | ✏️ Contributor | ✏️ Approved posts | - -**Security Notes:** -- Social Media Team does NOT have account passwords -- Access via Buffer or shared management tools only -- Cannot delete content or change account settings -- Cannot respond to DMs without approval - ---- - -## File Storage Access Matrix - -| Role | Google Drive | NextCloud | Vaultwarden | -|------|-------------|-----------|-------------| -| **Founding Partners** | πŸ”‘ | πŸ”‘ | πŸ”‘ | -| **Game Admins** | πŸ‘οΈ Ops folder | ❌ | ❌ | -| **Builders** | πŸ‘οΈ Asset library | πŸ‘οΈ Assets folder | ❌ | -| **Social Media** | πŸ‘οΈ Brand assets | πŸ‘οΈ Media folder | ❌ | -| **All Staff** | πŸ‘οΈ Staff resources | ❌ | ❌ | - ---- - -## API Keys & Credentials Access - -| Credential | Storage Location | Access | -|-----------|-----------------|---------| -| **Pterodactyl API (Full)** | Vaultwarden | Founding Partners only | -| **Pterodactyl API (Scoped)** | Vaultwarden | Game Admins (assigned servers) | -| **Gitea API (Full)** | Vaultwarden | Founding Partners only | -| **Gitea API (Scoped)** | Vaultwarden | Claude instances (scoped repos) | -| **Discord Bot Token** | Vaultwarden | Founding Partners only | -| **Social Media APIs** | Vaultwarden | Founding Partners only | -| **Payment Gateway** | Vaultwarden | Founding Partners only | -| **DNS API** | Vaultwarden | Founding Partners only | - -**Security Principle:** API keys are scoped to minimum necessary permissions whenever possible. - ---- - -## Emergency Override Access - -**Scenario:** Founding Partner unreachable during critical incident - -**Procedure:** -1. Document incident in detail -2. Take minimum necessary action -3. Notify Founding Partners immediately (all channels) -4. Lock any temporary elevated access after incident -5. Full post-mortem review - -**Who Can Override:** -- No one currently -- Future: Designated emergency contact (to be defined) - -**What Can Be Overridden:** -- None currently -- Future: Limited emergency procedures only - ---- - -## Access Request Procedures - -### Game Admin Requesting New Server Access - -1. Submit request to Founding Partners -2. Justify need (assigned project, coverage, etc.) -3. Await approval -4. Access granted in Pterodactyl (scoped) -5. Logged in access control matrix - -### Builder Requesting Production Deployment - -1. Complete build in creative server -2. Submit for review (screenshots + explanation) -3. Review by Michael or designated reviewer -4. If approved: Access granted for production deployment -5. Access removed after deployment complete - -### Staff Requesting Wiki.js Edit Access - -1. Submit request with section needed -2. Justify need (documentation improvement, etc.) -3. Founding Partners review -4. Access granted (scoped to section) -5. Changes reviewed periodically - ---- - -## Access Revocation Procedures - -### Routine (Staff Departure) - -1. Founding Partners notified of departure -2. All access revoked within 24 hours: - - Discord roles removed - - Pterodactyl access removed - - Wiki.js access removed - - Shared tool access removed -3. Incentive instance preserved for 30 days (data retrieval) -4. After 30 days: Instance deleted -5. Exit interview if appropriate - -### Emergency (Security Incident) - -1. Immediate access revocation (all systems) -2. Password reset on all shared accounts -3. API keys rotated if compromised -4. Investigation conducted -5. Access restored if cleared, or termination - ---- - -## Audit & Compliance - -**Monthly Audit:** -- Review Pterodactyl access logs -- Review Wiki.js edit history -- Verify no unauthorized access -- Check for dormant accounts - -**Quarterly Review:** -- Full access matrix review -- Update based on org changes -- Remove unnecessary access -- Add new roles as needed - -**Annual Review:** -- Complete security assessment -- Access control policy review -- Update procedures -- Staff training refresh - ---- - -## Technical Implementation - -### Pterodactyl Panel - -**Role Creation:** -``` -Role: Game Admin - TX1 Servers -Permissions: -- websocket.connect (assigned servers) -- control.console (assigned servers) -- control.start (assigned servers) -- control.stop (assigned servers) -- control.restart (assigned servers) -- file.read (assigned servers) -- file.write (assigned servers) -- startup.read (assigned servers) - -Servers: [Manually assign TX1 servers] -``` - -### Wiki.js - -**Group Creation:** -``` -Group: Operations Staff -Permissions: -- Read: ALL -- Write: /staff/operations/* -- Write: /staff/general/ -- Admin: NONE - -Group: Community Staff -Permissions: -- Read: ALL -- Write: /staff/community/* -- Write: /staff/general/ -- Admin: NONE - -Group: Content Staff -Permissions: -- Read: ALL -- Write: /staff/content/[subgroup]/* -- Write: /staff/general/ -- Admin: NONE -``` - -### Discord - -**Role Hierarchy (Top to Bottom):** -1. Founding Partner -2. Operations Lead (future) -3. Community Lead (future) -4. Content Lead (future) -5. Senior Staff (future) -6. Game Admin -7. Moderator -8. Builder -9. Social Media -10. Support -11. Subscriber -12. @everyone - -**Permission Template - Moderator:** -- Manage Messages -- Kick Members -- Timeout Members -- View Audit Log -- No Ban Members -- No Manage Roles -- No Manage Server - ---- - -**Fire + Frost + Foundation = Where Love Builds Legacy** πŸ’™πŸ”₯❄️ - ---- - -**Document Status:** COMPLETE -**Next Steps:** Implement in Wiki.js, Pterodactyl, Discord -**Review Schedule:** Monthly audits, quarterly reviews, annual assessment diff --git a/docs/tasks/department-structure-&-access-control-matrix/department-structure.md b/docs/tasks/department-structure-&-access-control-matrix/department-structure.md deleted file mode 100644 index da4b4c8..0000000 --- a/docs/tasks/department-structure-&-access-control-matrix/department-structure.md +++ /dev/null @@ -1,521 +0,0 @@ -# Firefrost Gaming - Department Structure - -**Version:** 1.0 -**Status:** Planning -**Last Updated:** 2026-02-17 -**Purpose:** Define organizational structure for staff, permissions, and access control - ---- - -## Executive Summary - -This document establishes the department structure for Firefrost Gaming, defining clear roles, responsibilities, and reporting relationships. This structure supports role-based access control (RBAC) in Wiki.js, Discord, Pterodactyl, and other systems. - -**Philosophy:** Clear boundaries create trust. Everyone knows what they can and cannot do. - ---- - -## Organizational Chart - -``` - β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” - β”‚ FOUNDING PARTNERS β”‚ - β”‚ Michael (The Wizard) β”‚ - β”‚ Meg (The Emissary) β”‚ - β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ - β”‚ - β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” - β”‚ β”‚ β”‚ - β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β” - β”‚ OPERATIONS β”‚ β”‚ COMMUNITY β”‚ β”‚ CONTENT β”‚ - β”‚ DEPARTMENT β”‚ β”‚DEPARTMENT β”‚ β”‚ DEPARTMENT β”‚ - β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ - β”‚ β”‚ β”‚ - β”Œβ”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β” β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β” - β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ - β”Œβ”€β”€β”€β”€β–Όβ”€β”€β”β”Œβ”€β”€β–Όβ”€β”€β”€β”β”Œβ”€β”€β–Όβ”€β”€β”€β” β”‚ β”Œβ”€β”€β”€β–Όβ”€β”€β”β”Œβ”€β”€β–Όβ”€β”€β”€β”β”Œβ”€β–Όβ”€β”€β”€β”€β” - β”‚ Game β”‚β”‚Serverβ”‚β”‚Supportβ”‚ β”‚ β”‚Socialβ”‚β”‚Build-β”‚β”‚Videoβ”‚β”‚ - β”‚Adminsβ”‚β”‚ Ops β”‚β”‚ Team β”‚ β”‚ β”‚Media β”‚β”‚ ers β”‚β”‚ Teamβ”‚ - β””β”€β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”˜ β”‚ β””β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”˜ - β”‚ - β”Œβ”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β” - β”‚ Moderators β”‚ - β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ -``` - ---- - -## Department Definitions - -### 1. Founding Partners (Executive) - -**Members:** -- Michael "Frostystyle" Krause (The Wizard) - Owner/Operator -- Meg "Gingerfury" (The Emissary) - Community Manager/Partner - -**Authority:** -- Full access to all systems -- Final decision-making authority -- Strategic direction -- Financial management -- Hiring and termination - -**Unique Permissions:** -- Root/admin access to all servers -- Full Pterodactyl panel access -- Billing system administration -- DNS management -- API key management - -**Accountability:** To each other, to the vision - ---- - -### 2. Operations Department - -**Purpose:** Keep the technical infrastructure running - -**Sub-Teams:** - -#### 2A. Game Administrators -**Roles:** -- Monitor server health -- Troubleshoot player issues -- Manage whitelist/bans -- Configure game settings -- Respond to technical tickets - -**Access:** -- Pterodactyl panel (assigned servers only) -- Server console access -- File management for game configs -- Uptime Kuma (read-only) -- Wiki.js Operations section (read/write) - -**Cannot Access:** -- Root server access -- Other servers' files -- Billing information -- Infrastructure configs -- API keys - -#### 2B. Server Operations (Future) -**Roles:** -- System administration -- Performance optimization -- Backup management -- Update deployment -- Infrastructure monitoring - -**Access:** -- SSH to assigned servers (sudo limited) -- Pterodactyl Wings management -- Netdata dashboards -- Infrastructure documentation -- Automation scripts - -**Cannot Access:** -- Production database passwords -- API keys for critical services -- Billing systems -- Customer data - -#### 2C. Support Team -**Roles:** -- Answer player questions -- Process whitelist requests -- Escalate technical issues -- Document common problems -- Maintain FAQ - -**Access:** -- Support ticket system -- Wiki.js FAQ section (read/write) -- Discord support channels -- Whitelist Manager (if approved) - -**Cannot Access:** -- Server administration -- Game server files -- Player account details beyond username -- Moderation tools - ---- - -### 3. Community Department - -**Purpose:** Foster healthy, engaged player community - -#### 3A. Community Moderators -**Roles:** -- Enforce Discord rules -- Welcome new members -- Facilitate events -- Mediate conflicts -- Report serious violations - -**Access:** -- Discord moderation tools (kick, timeout, mute) -- Community Wiki.js section (read/write) -- Event planning channels -- Player reports - -**Cannot Access:** -- Ban permissions (escalate to Meg/Michael) -- Server administration -- Private staff channels (unless specifically invited) -- Financial information - -**Escalation Path:** -- Minor issues: Handle directly -- Major issues: Escalate to Meg (The Emissary) -- Severe violations: Immediate escalation + temporary action - ---- - -### 4. Content Department - -**Purpose:** Create engaging content that attracts and retains players - -#### 4A. Social Media Team -**Roles:** -- Create and schedule posts -- Engage with community on platforms -- Monitor brand mentions -- Track analytics -- Coordinate with Meg on strategy - -**Access:** -- Buffer/social media scheduler -- Canva/design tools -- Content calendar (Google Sheets) -- Wiki.js Social Media section (read/write) -- Analytics dashboards - -**Cannot Access:** -- Account passwords (use shared tools only) -- Financial information -- Server systems -- Player data - -**Reporting:** To Meg (The Emissary) - -#### 4B. Builders -**Roles:** -- Design spawn areas -- Create custom builds -- Maintain aesthetic consistency -- Test modpack integration -- Document builds - -**Access:** -- Assigned creative servers (full permissions) -- Pterodactyl (assigned servers only) -- Wiki.js Builder section (read/write) -- Discord builder channels -- Design asset library - -**Cannot Access:** -- Production game servers (until spawn approved) -- Other builders' work servers -- Infrastructure systems -- Player data - -**Workflow:** -1. Receive assignment from Michael -2. Build in creative server -3. Submit for review -4. Deploy approved builds to production - -#### 4C. Video/Streaming Team (Future) -**Roles:** -- Create YouTube content -- Stream gameplay -- Create tutorials -- Produce promotional videos -- Edit and publish - -**Access:** -- Gameplay footage permissions -- Brand assets (logos, colors) -- YouTube channel (contributor) -- Wiki.js Media section (read/write) - -**Cannot Access:** -- YouTube channel admin -- Financial information -- Server systems - ---- - -## Role Hierarchy & Permissions - -### Permission Levels (Lowest to Highest) - -**Level 0: Public** -- Access: Public website, Discord guest -- Can: View public information -- Cannot: Anything restricted - -**Level 1: Subscriber** -- Access: Subscriber Discord, game servers -- Can: Play, chat, request support -- Cannot: Moderate, administrate - -**Level 2: Support/Junior Staff** -- Access: Support tools, FAQ editing -- Can: Answer questions, escalate issues -- Cannot: Moderate, punish, administrate - -**Level 3: Moderator** -- Access: Moderation tools, community management -- Can: Timeout, mute, warn, remove content -- Cannot: Ban, access servers, modify critical settings - -**Level 4: Content Creator** -- Access: Creative tools, assigned resources -- Can: Create content, manage projects -- Cannot: Deploy to production, access infrastructure - -**Level 5: Game Admin** -- Access: Game server administration -- Can: Configure servers, manage whitelists, troubleshoot -- Cannot: Access infrastructure, other servers - -**Level 6: Senior Staff** -- Access: Multiple systems, broader permissions -- Can: Cross-department collaboration, mentoring -- Cannot: Financial, infrastructure, strategic decisions - -**Level 7: Department Lead** (Future) -- Access: Department-wide resources -- Can: Manage team, approve work, allocate resources -- Cannot: Override founding partners, access other departments - -**Level 8: Founding Partner** -- Access: Everything -- Can: Anything -- Cannot: Nothing (full authority) - ---- - -## Access Control Matrix - -See separate document: `access-control-matrix.md` - ---- - -## Onboarding by Department - -### Operations (Game Admin) -**Week 1:** -- Pterodactyl panel training -- Server restart procedures -- Console command basics -- Whitelist management -- Escalation process - -**Week 2:** -- Advanced troubleshooting -- Log analysis -- Performance monitoring -- Common mod issues -- Documentation contribution - -### Community (Moderator) -**Week 1:** -- Discord moderation tools -- Community guidelines -- Conflict resolution basics -- Report filing -- Escalation process - -**Week 2:** -- Event facilitation -- Advanced moderation scenarios -- Community engagement strategies -- Documentation contribution - -### Content (Builder) -**Week 1:** -- Fire vs Frost aesthetics -- Creative server access -- Build assignment workflow -- Review process -- Asset library - -**Week 2:** -- First spawn assignment -- Modpack integration -- Testing procedures -- Documentation - -### Content (Social Media) -**Week 1:** -- Brand voice guide -- Content calendar -- Scheduling tools -- Analytics basics -- Approval process - -**Week 2:** -- Content creation -- Engagement strategies -- Analytics review -- Campaign planning - ---- - -## Cross-Department Collaboration - -**Common Scenarios:** - -**New Modpack Launch:** -- Operations: Server setup and testing -- Content (Builders): Spawn area creation -- Content (Social Media): Announcement campaign -- Community: Event planning and moderation - -**Player Issue Resolution:** -- Support: Initial response and triage -- Game Admin: Technical investigation -- Moderator: If behavioral component -- Escalation: To Meg/Michael if needed - -**Content Creation:** -- Social Media: Plans campaign -- Builders: Create visual content -- Video Team: Produces video -- Community: Amplifies in Discord - ---- - -## Emergency Procedures - -### Security Incident -1. Founding Partners notified immediately -2. Affected systems isolated -3. All staff passwords reset -4. Incident logged and reviewed -5. Procedures updated - -### Staff Misconduct -1. Report to appropriate department lead or Founding Partner -2. Investigation conducted -3. Action taken per severity -4. Documentation maintained -5. Team informed as appropriate - -### Technical Outage -1. Operations team assesses -2. Founding Partners notified -3. Status updates to community (via Meg) -4. Resolution prioritized -5. Post-mortem conducted - ---- - -## Performance & Review - -**All Staff (Quarterly):** -- Performance review -- Goal setting -- Skill development -- Feedback session -- Compensation review (if applicable) - -**Key Metrics by Department:** - -**Operations:** -- Server uptime -- Ticket resolution time -- Player satisfaction - -**Community:** -- Community health metrics -- Event participation -- Conflict resolution effectiveness - -**Content:** -- Content output quantity/quality -- Engagement metrics -- Project completion rate - ---- - -## Growth & Advancement - -**Career Paths:** - -**Operations Track:** -Support β†’ Game Admin β†’ Senior Game Admin β†’ Ops Lead - -**Community Track:** -Moderator β†’ Senior Moderator β†’ Community Lead - -**Content Track:** -Builder/Social Media β†’ Senior Creator β†’ Content Lead - -**Cross-Functional:** -Exceptional performers may move between departments based on interest and need - ---- - -## Compensation & Benefits - -**All Staff Levels:** -- Incentive instance (private Minecraft server) -- Sovereign-tier subscriber access -- Recognition in credits -- Portfolio/resume material - -**Senior Staff (Future):** -- Revenue share -- Equity/ownership stake -- Additional perks - ---- - -## Terminology - -**Founding Partners** - Michael and Meg -**Department** - Major organizational division -**Team** - Sub-group within department -**Role** - Specific job function -**Permission** - Technical access granted -**Authority** - Decision-making power -**Escalation** - Moving issue up the chain - ---- - -## Implementation Notes - -**Phase 1: Foundation (Current)** -- Founding Partners only -- Document structure -- Prepare for first hires - -**Phase 2: First Hires** -- 2-3 Builders -- 1 Social Media Helper -- Implement access controls - -**Phase 3: Expansion** -- Add moderators as community grows -- Add game admins as server count increases -- Add support team - -**Phase 4: Maturity** -- Department leads emerge -- Cross-functional teams -- Formal review processes - ---- - -**Fire + Frost + Foundation = Where Love Builds Legacy** πŸ’™πŸ”₯❄️ - ---- - -**Document Status:** COMPLETE -**Next Steps:** Create access control matrix, map to Wiki.js permissions -**Review Schedule:** Quarterly or as organization grows