Documentation
This page covers the quick setup and all slash commands of the bot. Everything published from the panel follows exactly the same rules as the commands.
Overview
- Attendance publishing — Messages with automatic reactions (✅ 🕐 ❌)
- Reaction tracking — See who responded and non-reactors
- Absence management — Members declare unavailability via a button
- Automation — Scheduled automatic publishing and reminders
- Reminders — Up to 3 reminders for non-reactors (mention, DM or both)
- External webhook — JSON notifications to Discord, Zapier, Make, n8n…
- Web panel — Modern interface with dashboard and audit log
Installation (simple)
Sign in
Sign in to the panel with Discord and choose your server.
Configure the basics
Fill in: presence role, presence channel, admin role.
Slash alternative
/presence setup
Publish now with /presence create
Bot commands
Quick setup assistant.
Set the mentioned role (ping/tracking).
Choose the channel for presence messages.
Set the admin role allowed to manage.
Create a presence (future date only). Reactions + DB record.
Edit an existing presence (message, time, …).
Cancel a presence (deletes the message; cleans up if needed).
Post/move the absence message with a button (the old one is removed).
The web panel
The panel lets you manage your server from a modern web interface, without using Discord commands.
Activity overview: monthly attendances, participation rate, active absences, 30-day chart and member rankings.
Create an attendance directly from the panel. Choose date, time, message and preview the embed before publishing.
Schedule automatic attendance publishing at regular intervals (every 3h, 6h, 12h or once daily at a set time).
Set up to 3 reminders for members who haven't reacted. Choose between channel mention, DM, or both.
View and manage absences declared by members. Cancel an absence in one click.
Configure presence channel, absence channel, roles (presence, admin, absence) and language/timezone.
Receive a JSON notification on an external service (Discord, Zapier, Make, n8n…) for each publication or cancellation.
Complete history of all actions performed on the server via the panel (publications, settings changes, etc.).
Best practices (bot)
- Use a dedicated role for mentions (e.g., @Members).
- Make sure the bot has permissions in the target channel.
- Use a future date and 24-hour time format.
- For absences, keep a dedicated channel.
Troubleshooting (bot)
- Commands not showing: check the bot is invited to the server and you have sufficient permissions.
- Presence rejected: ensure
- Absence not moved: rerun
/presence absence. - Bot offline: ask an admin to restart the bot (or check the host). Members do not have access to technical endpoints.