Public Playbooks for Real Roblox Operations

Owner Launch Sequence

Start with one pilot workspace before full rollout. Define role policy first, then connect Roblox ingest, then invite staff. Teams that invert this order usually get permission drift and bad attendance data.

1. Create workspace with a valid owner key and Roblox group ID.
2. Create workspace roles and map Roblox ranks before staff invites.
3. Generate ingest token and paste the generated server script in Roblox Studio.
4. Run one controlled test session and verify minutes/sessions update correctly.
5. Enable production invites only after data validation is complete.

Manager Operating Model

Managers should use Kyra as a weekly rhythm system, not only a dashboard viewer. The most reliable teams run the same cadence every week and document decisions in notes/audit trails.

• Plan sessions at least 3-7 days in advance.
• Use assignment scopes so requirements match actual role responsibility.
• Review pending LOA daily and keep decision notes specific.
• Use Manage tab to identify outliers before period close.
• Export weekly report and archive leadership actions.

Developer Integration Model

Developers can extend telemetry without breaking baseline metrics. Keep custom payload keys stable, documented, and explicitly allow-listed. Avoid one-off keys that change every patch because they break downstream analytics.

• Use one server script integration for base events.
• Add custom events only for metrics with clear business meaning.
• Maintain versioned payload conventions (field names + value type).
• Validate ingest responses and retry only on safe conditions.
• Document every custom key in workspace docs for managers.