Owners deciding whether Aegis is safe enough to invite.
Security Overview
Aegis is designed to help staff manage a Discord server without asking for passwords, Discord tokens, Roblox passwords, or owner account access. The safest way to evaluate Aegis is to start in a test server, give only the permissions needed for the modules you want, and watch the audit logs while features are enabled one at a time.
What Aegis can do
- Use Discord permissions to moderate, log, create tickets, manage roles, and post configured messages.
- Use Roblox OAuth or profile-code verification to connect a Discord account to a Roblox identity.
- Show staff-facing logs for setup actions, moderation actions, verification results, and ticket activity when those modules are enabled.
- Run dashboard actions only for users who pass Discord login and server-management checks.
What Aegis cannot do
- Bypass Discord role hierarchy or server permissions.
- Read a user's Discord password, Discord token, Roblox password, or private Roblox credentials.
- Control a server after the bot is removed from that server.
- Guarantee recovery of messages or logs that were never captured by enabled logging systems.
Owner checklist
- Invite Aegis to a private test server first.
- Enable only one system at a time, starting with low-risk systems such as logs or tickets.
- Keep Discord audit logs open during setup.
- Give Administrator only if you are intentionally testing full automation; otherwise use limited permissions.
Owners who want to know why the invite asks for permissions.
Permissions Explained
Aegis needs different Discord permissions depending on which systems you enable. A basic setup can run with limited permissions, while a full setup needs broader permissions to create channels, manage roles, moderate members, and update automated messages.
What Aegis can do
- Manage roles for verification, role panels, Roblox role sync, booster exceptions, and staff workflows.
- Manage channels for ticket categories, setup channels, logs, verification gates, and showcase areas.
- Moderate members only when moderation or automod features are enabled and the bot role is high enough.
- Send embeds, attach files, add reactions, and manage messages for panels, logs, tickets, and announcements.
What Aegis cannot do
- Manage users or roles above the Aegis bot role.
- See private channels unless the bot role is granted access.
- Fix Discord permission conflicts if another bot or role override keeps changing them.
- Perform owner-only Discord actions such as transferring ownership.
Owner checklist
- Place the Aegis role above roles it needs to assign, but below owner and senior staff roles.
- Avoid giving Aegis permission to manage staff roles unless there is a specific reason.
- Use a test category to confirm channel permission changes before applying them server-wide.
- Review every enabled module that can create, edit, or delete Discord objects.
Owners worried about hidden remote controls.
Dashboard Access and Remote Controls
The dashboard is meant to work like a control center for server owners and managers. Users sign in with Discord, select a server they can manage, and change Aegis settings for that server. Sensitive controls should require the right Discord permissions and should be logged.
What Aegis can do
- Let authorized staff configure modules such as tickets, welcomes, logs, reaction roles, verification, and billing status.
- Show whether Aegis is installed in a server and provide an invite flow when it is not.
- Run safe dashboard actions that map to bot settings or bot commands.
- Use role and permission checks so normal members cannot control server settings.
What Aegis cannot do
- Let random website visitors control your server.
- Override Discord's permission model without the bot being in the server and properly authorized.
- Secretly manage a server if the bot is not installed there.
- Replace your responsibility to review staff access, bot role position, and module settings.
Owner checklist
- Only grant dashboard access to people who should manage the server.
- Use Discord roles and permissions to separate owners, admins, moderators, and support staff.
- Check dashboard changes against Discord audit logs when testing high-risk modules.
- Remove Aegis from the server if you want all dashboard control to stop immediately.
Owners writing privacy notices or reviewing member trust risk.
Data Storage Policy
Aegis stores the minimum practical data needed to operate enabled systems. That usually means Discord IDs, server IDs, channel IDs, role IDs, configuration settings, verification links, moderation records, ticket metadata, billing status, and logs generated by enabled modules.
What Aegis can do
- Store server configuration so setup does not reset after restarts.
- Store Discord-to-Roblox links after successful verification.
- Store moderation and ticket records if those modules are enabled.
- Store billing and premium status so paid features can remain active.
What Aegis cannot do
- Store Discord passwords, Roblox passwords, or member payment card numbers.
- Know private details that Discord or Roblox never provide to the bot.
- Guarantee deletion of copies already exported by server staff.
- Collect data from servers where Aegis is not installed.
Owner checklist
- Tell members what verification and moderation systems are active.
- Avoid putting private personal information into tickets unless necessary.
- Limit staff access to ticket transcripts and moderation logs.
- Ask support before requesting bulk data deletion or migration.
Roblox groups, clans, roleplay servers, and communities replacing Bloxlink or RoVer-style verification.
Roblox OAuth Verification
Roblox OAuth lets members verify by signing in through Roblox instead of copying a code into their profile. Aegis receives the identity result needed to link the Discord account to the Roblox account; it does not receive the Roblox password.
What Aegis can do
- Link a Discord account to a Roblox user ID and username.
- Apply member, ally, pending, or configured roles after verification.
- Use group and rank information for role sync when the server config enables it.
- Provide profile-code fallback when OAuth is unavailable or the Roblox app is in review.
What Aegis cannot do
- Read or store Roblox passwords.
- Verify a Roblox account without the member completing an approved verification method.
- Guarantee Roblox API availability during Roblox outages or review limits.
- Safely replace an existing verification bot without checking role permissions first.
Owner checklist
- Start with a verification test channel and a small group of staff testers.
- Confirm pending, member, allied, and log channels before locking the server.
- Test both normal member verification and ally verification if your server uses allies.
- Keep a manual fallback path ready for members who cannot use OAuth.
Owners who want proof before trusting a new bot.
Safe Test Install Guide
The safest first install is not a full production rollout. Add Aegis to a test server or private category, enable one module, confirm logs, then expand permissions only when the behavior is understood.
What Aegis can do
- Run in a test server with limited roles and channels.
- Post setup panels without changing the entire server.
- Generate logs and setup reports for staff review.
- Scale from test install to production install once owners approve the setup.
What Aegis cannot do
- Make a complex server safe without staff reviewing role and channel permissions.
- Undo every action another bot has taken before Aegis was installed.
- Protect a server if owners intentionally grant dangerous access to the wrong users.
- Replace Discord audit logs as the source of truth for server-level changes.
Owner checklist
- Create a test category named Aegis Test.
- Invite Aegis with limited permissions first.
- Test logs, tickets, welcome messages, and verification separately.
- Only enable server-wide permission changes after a staff review.
Owners reducing bot clutter without breaking roles or tickets.
Migration From Bloxlink, Sapphire, TicketTool, MEE6, Dyno, and Carl-bot
Aegis can replace parts of several common bots, but migrations should be done in phases. Do not remove an old bot until the matching Aegis feature is configured, tested, and confirmed by staff.
What Aegis can do
- Replace Bloxlink-style Roblox verification and role sync after role mapping is checked.
- Replace Sapphire or TicketTool-style tickets after categories, staff roles, and transcript settings are confirmed.
- Replace MEE6, Dyno, and Carl-bot systems such as welcomes, moderation, logs, reaction roles, giveaways, and utility flows where configured.
- Create migration notes so staff know which old bot features are still active.
What Aegis cannot do
- Automatically import every old bot setting without review.
- Detect private settings from bots that do not expose them.
- Safely remove old bots before Aegis has matching channels, roles, and permissions.
- Promise identical behavior for every third-party bot feature.
Owner checklist
- List every old bot and what it currently does.
- Migrate low-risk systems first: welcomes, logs, role panels, and tickets.
- Migrate verification only after role and channel permissions are audited.
- Keep old bots installed until Aegis has passed a real test with staff.
Owners comparing cost before inviting Aegis.
Pricing and Early Tester Offers
Aegis is intended to keep useful basic features available while charging for higher-cost premium systems such as advanced AI, large-scale automation, premium support, and managed setup. Early tester offers may change as the platform grows.
What Aegis can do
- Offer free or low-cost basic server management where practical.
- Offer paid premium access for heavier automation, AI usage, dashboard controls, and support.
- Provide early tester or founder-style deals when they are currently available.
- Keep billing status separate from core safety and server trust information.
What Aegis cannot do
- Guarantee permanent promotional prices unless stated in the active offer.
- Make high-cost AI usage unlimited on free plans.
- Activate premium for a server without the required owner approval or payment path.
- Replace your need to review which features your server actually needs.
Owner checklist
- Confirm the active offer before relying on a price.
- Ask which features are free and which are premium for your server.
- Start with the least expensive plan that covers your actual use case.
- Use a test setup before paying for managed migration.
Owners deciding whether Aegis covers their server stack.
Aegis Feature Overview
Aegis is an all-in-one Discord server management platform. The main goal is to reduce bot clutter while keeping moderation, verification, tickets, logs, automations, role systems, AI tools, analytics, and server setup in one place.
What Aegis can do
- Run moderation, automod, logs, tickets, reaction roles, welcomes, giveaways, leveling, applications, and role management.
- Support Roblox verification, role sync, ally verification, and group-aware setup for Roblox communities.
- Provide AI-assisted utilities, staff summaries, setup help, and command routing where enabled.
- Use dashboard controls to make setup easier for non-technical staff.
What Aegis cannot do
- Be perfect for every niche server without configuration.
- Replace human moderation judgment in serious disputes.
- Safely run every feature with no permissions review.
- Solve all legacy server problems caused by old bots, bad role hierarchy, or conflicting channel overwrites.
Owner checklist
- Pick the three features your server needs most first.
- Avoid enabling every module on day one.
- Create a staff testing channel for command trials.
- Document which old bots each Aegis module is replacing.
Servers that need confidence before depending on Aegis long term.
Owner Away Reliability Plan
Aegis is being shaped to keep working even when the owner is not immediately available. The reliability plan focuses on monitoring, recovery notes, health checks, safe defaults, documentation, and clear support handoff.
What Aegis can do
- Expose status, setup notes, and support routes for owners and staff.
- Keep core systems running through stored configuration and restart-safe design.
- Produce operational reports and health signals where monitoring is enabled.
- Use conservative defaults for risky systems so a server is not changed unexpectedly.
What Aegis cannot do
- Guarantee instant human support at every hour.
- Prevent every outage caused by Discord, Roblox, hosting, payments, or third-party APIs.
- Self-invite back into a server after being removed.
- Replace the need for server owners to keep backup admins and documented procedures.
Owner checklist
- Keep at least two trusted server owners or administrators.
- Document how to disable each high-risk module.
- Keep support and status links pinned for staff.
- Use safe test installs before depending on Aegis for critical workflows.
Need a short trust link?
Use the Security Review page in Discord tickets.
It answers the common owner concerns directly: malicious bots, nuking, hidden remote controls, Roblox login safety, data storage, and safe test installs.