Prerequisites
Before integrating Guardyn, you need:
- a published Roblox experience you are authorized to manage;
- a Guardyn workspace with an active subscription or grace period for report intake;
- one enabled game record in the workspace;
- one active Guardyn API key;
- permission to create a Roblox Secret and edit experience security settings;
- a server-validated source of filtered report text.
Values from Guardyn
The dashboard supplies two different values:
| Value | Example | Where it belongs |
|---|---|---|
| Guardyn Game ID | gdn_game_ab12cd34 | Your server-side integration configuration |
| API key | Shown once after creation | Roblox Secret named GUARDYN_API_KEY |
The game ID is an identifier, not a password. The API key is a secret and must never be placed in a Script, LocalScript, attribute, DataStore, screenshot, tutorial description, or source repository.
Supported identity
Guardyn stores the identifier Roblox exposes inside the current experience. An integration should use Player.User.Id, which follows Roblox's domain-scoped identity model for new players and remains compatible with returning players during rollout.
The same numeric value must not be assumed to identify the same person in another game. Guardyn combines the selected game with the scoped identifier when checking restrictions.