One data source
Keep supported slash commands, OCR results, and dashboard changes aligned instead of syncing two unrelated tools.
Discord automation
Connect Discord guild commands to the same operational record
Guild members already coordinate in Discord, but a generic moderation bot does not understand the rest of a guild’s operations. ForgeKeep connects supported slash commands, OCR submissions, and notifications to the same guild-scoped records used by the web dashboard, reducing duplicate entry and conflicting versions.
Dashboard field guide
See discord bot in motion.
A sample view of the ForgeKeep dashboard, with the exact records and handoffs this feature is designed to keep together.
Why it matters
Replace disconnected updates with a reviewable workflow.
Timely notifications
Send operational reminders and updates to the channels and roles chosen by guild leaders.
Scoped permissions
Require linked identities and server-side authorization for sensitive guild actions.
Operational flow
How the workflow fits together
- 01
Connect the server
Authorize the integration, select the guild workspace, and choose command and notification channels.
- 02
Map roles and rules
Decide which Discord roles can run supported operations and which events should trigger messages.
- 03
Operate from chat
Use supported slash commands such as /spawn, /kill, /attendance, /cpupdate, and /link while ForgeKeep preserves the corresponding web record and permissions.
Related guild operations
Start with your current operation
Bring discord bot into the same guild record.
Create a workspace, invite the right officers, and migrate one workflow at a time. Private guild data stays behind application authorization.