Skip to main content
Every Seshy setting lives inside a single command: /settings. Run it in any channel where Seshy has permission to send messages and you get an interactive panel that covers all eight modules — general server identity, role and permission mappings, channel assignments, ER:LC API connection, module toggles, and configuration backup. You never need to memorize separate setup commands for individual modules; if you want to change how Seshy behaves anywhere in your server, /settings is the only place to go.
Changing role and permission settings can immediately affect who is authorized to run staff commands, start sessions, approve LOA requests, and trigger other module actions. Review your permission hierarchy carefully before saving changes, and always confirm that your designated staff roles are mapped correctly before removing or replacing a role assignment.

​
Settings Categories

The General section controls how Seshy presents itself across your server. This is where you set the foundational identity that flows through every module’s embeds and announcements.Server Name — sets the display name used in session embeds, staff logs, and announcement headers. This should match your community’s official name so every Seshy message feels native to your server.Embed Color — choose a hex color code for the accent color on all Seshy embeds. Set it to your community’s brand color and every session announcement, moderation log, and staff notification will carry your visual identity.Banner Image — provide a URL to a banner image that Seshy attaches to session startup and shutdown embeds. Use your community’s official banner or a custom graphic designed for your ERLC server.Footer Text — the custom text that appears at the bottom of every Seshy embed. Many communities use their server tag, a short motto, or their official department name here.These branding options are available to every server at no cost — custom-branded embeds are not a premium feature.
The Roles & Permissions section defines who can do what across every Seshy module. Seshy uses a hierarchical permission system — you assign Discord roles to permission levels, and those levels gate specific commands and actions.Staff Role — the base role required to use staff-facing commands across the moderation, sessions, and staff modules.Management Role — an elevated tier above Staff, typically assigned to supervisors or directors. Holders can approve LOA requests, run moderation reports, and manage other staff members’ shift records.Administrator Role — the highest tier in Seshy’s hierarchy. Administrators can change /settings configuration, override module behavior, and access audit logs.Per-Module Ping Roles — for each module that sends notifications (sessions, moderation alerts, community announcements), you can assign a dedicated ping role. This keeps session pings separated from moderation alerts so members only get pinged for what’s relevant to them.Roles are evaluated in hierarchy order — a user with the Administrator role inherits all Staff and Management permissions automatically. You can also grant or deny specific command access to individual roles outside the standard hierarchy using the granular override options in this section.
Removing a role from the Staff, Management, or Administrator mapping takes effect immediately. Any users whose only Seshy access came from that role will lose command access the moment you save.
The Channels section tells Seshy where to send every category of automated output. Designating dedicated channels for each module keeps your server organized and makes logs easy to find.Session Channel — the channel where /ssu and /ssd embeds are posted. This is your primary session announcement channel, visible to your community.Session Log Channel — a separate, typically staff-only channel where session metadata, duration, and attendance records are logged automatically.Moderation Log Channel — every warn, mute, kick, and ban action is posted here automatically as it happens, including the moderator, target user, reason, and case number.Audit Log Channel — Seshy’s administrative audit trail. Settings changes, permission overrides, Ares security events, and configuration modifications are all recorded here so you always know what changed and who changed it.Staff Log Channel — shift start and end events, LOA approvals, and promotion announcements are posted to this channel automatically by the Staff Module.Application Channel — where the Community module posts incoming staff application submissions for your management team to review.ER:LC Feed Channel — if you have the ER:LC Integration connected, this channel receives live updates including player join/leave events, command logs, and kill logs from your private server.You can use the same channel for multiple log types if you prefer a consolidated log, or keep each module’s output in its own dedicated space.
The ER:LC Integration section connects Seshy to your ER:LC Private Server so it can pull live game data directly into Discord. Configuring this unlocks the full ER:LC module: player lists, team rosters, command logs, kill logs, vehicle tracking, ban management, mod call tracking, queue monitoring, and the server status dashboard.Step 1 — Get your API keyOpen Roblox and join your ERLC Private Server. Navigate to the in-game Settings menu, then open the Private Server tab. Copy the API Key displayed there — this is a unique key tied specifically to your private server.Step 2 — Paste the key in /settingsRun /settings in Discord, navigate to ER:LC Integration, and paste your API key into the input field. Seshy validates the format before saving.Step 3 — Test the connectionUse the built-in Test Connection button to verify that Seshy can reach your server’s API endpoint. A successful test returns your current player count and confirms the integration is live. If the test fails, double-check that the API key was copied in full and that your Private Server is currently running.
Your ER:LC API key is encrypted before storage and is never exposed in bot responses, log messages, or Discord embeds. Seshy does not share API credentials with any third party.
Once connected, configure which data to surface by selecting the feed types you want Seshy to post to your ER:LC Feed Channel — join/leave events, command logs, kill logs, and mod call alerts can each be enabled or disabled independently.
The Modules section gives you a master toggle for each of Seshy’s eight modules. Disabling a module hides its commands from your server’s slash command list and stops all automated output from that module.You can re-enable any module at any time from this section without losing your previous configuration for that module. Settings, channel assignments, and role mappings are preserved when a module is disabled.
The Backup & Restore section lets you export your entire Seshy configuration — all settings, role mappings, channel designations, branding, and module states — as a single restorable snapshot.Creating a BackupClick Create Backup in the Backup & Restore section of /settings. Seshy generates a configuration file and sends it to the audit log channel (or directly to you if no audit channel is set). Store this file somewhere safe — your server’s staff channels, a private document, or alongside your other server records.Restoring a BackupTo restore, navigate to Backup & Restore in /settings, select Restore from Backup, and paste or upload your saved configuration file. Seshy validates the file, shows you a summary of what will be restored, and applies the configuration after confirmation.When to back upCreate a backup before making large changes to your permission hierarchy, before adding or removing modules, and periodically as routine maintenance. If you ever need to move Seshy’s configuration to a new server or recover from an accidental settings change, a recent backup makes the process immediate.

​
Custom Branding

Seshy’s custom branding system lets your server’s identity flow through every automated message the bot sends. Set your embed color, banner image, and footer text once in /settings → General, and every session announcement, staff log, moderation action, and community notification will carry your community’s visual style consistently. Many ERLC server owners use this to make Seshy’s output indistinguishable from custom-built server bots. A branded session startup embed with your department’s colors, your official banner, and your server tag in the footer looks and feels like something your team built specifically for your community — because in terms of visual identity, it is. Custom branding is fully available to every server at no cost. There is no premium tier required to access embed colors, banners, or footer customization.

​
Permission Hierarchy

Seshy’s permission system is hierarchical by design. Assign your Discord roles to three levels — Staff, Management, and Administrator — and Seshy enforces access control across every module automatically. Higher tiers inherit all permissions from lower tiers. An Administrator can do everything a Management role can do, and everything a Staff role can do, in addition to their exclusive access to configuration and audit functions. You can also apply granular overrides to specific roles outside the main hierarchy. This is useful for specialized roles — for example, a Dispatch role that needs access to ER:LC feed commands but shouldn’t be able to start sessions, or a Training Supervisor role that can approve promotions but shouldn’t have access to server-wide moderation history. Assign granular overrides from /settings → Roles & Permissions → Advanced Overrides. Each override specifies a Discord role, a Seshy module, and the permission level to grant or deny.

​
ER:LC API Configuration

Connecting your ER:LC Private Server to Seshy unlocks a live data bridge between your in-game server and your Discord community. The integration pulls real-time player counts, team and rank data, in-game command logs, kill logs with weapons and timestamps, active vehicle lists, mod call response tracking, queue status, and ban records — all surfaced as Discord embeds and live-updating status messages. To get your API key, join your Private Server in ER:LC and open Settings → Private Server → API Key. This key is unique to your server and changes if you regenerate it, so store it somewhere accessible for your management team. After pasting the key in /settings → ER:LC Integration and running the connection test, select which event types you want Seshy to log to your ER:LC feed channel. You can enable all of them for full visibility, or limit it to the specific feeds your moderation team needs.
Your API key is encrypted using industry-standard encryption before it is stored. It is never displayed in any Discord channel, embed, or log output after initial setup.

​
Configuration Backup

Back up your Seshy configuration regularly — especially before restructuring your permission hierarchy or enabling new modules. The backup captures everything: all role mappings, channel assignments, branding settings, module states, and ER:LC integration settings (excluding the API key itself, which you re-enter after a restore for security reasons). Restores are non-destructive previewed actions — Seshy shows you exactly what will change before applying anything, so you can confirm the restore matches what you expect. If you’re migrating an ERLC community to a new Discord server, a configuration backup and restore is the fastest way to get Seshy configured identically on the new server.