Documentation

Getting started

1. Open Sign in and continue with Discord. The first time, you confirm you are 13 or older and accept the Terms of Service.
2. On your Dashboard page, create a server or join one with an invite code (orasty.xyz/invite/your-code).
3. Link your Roblox account in Settings so shifts, logs and lookups know who you are in game.
4. Owners and managers open the server's Dashboard to create roles and invite staff. Everyone with a role opens the Panel.

Press Ctrl/Cmd + K (or /) anywhere in the app to open the command palette.

Panel vs Dashboard

Each server has two separate areas.

• The Panel is for day-to-day staff work: shifts, the toolbox, creating logs, the live ER:LC feed and punishment logs. You only need a role to open it. The Panel deliberately has no link to the Dashboard.
• The Dashboard is for running the server. The sidebar only shows the pages your permissions allow, grouped like this:

You can open the Dashboard if you own the server or hold at least one of: manage_server, manage_roles, approve_joins, manage_activity, view_shifts, manage_infractions, manage_loa or manage_sessions.

Your Settings

Settings is about you, across every server. Its pages are:

• Account and Profile: your account details, linked Roblox account and profile. Your handle is always your Discord username. It updates by itself when you sign in and cannot be edited.
• Notifications: new leave requests to review, leave decisions, and other updates.
• Leave of absence: request leave, cancel a pending request and see your history.
• Punishment logs, Infractions and Shift time: everything you have logged, received or worked. These sit under My staff record in the sidebar.
• Support: a short support code and links to get help (see Support code).

Roles and permissions

People can hold several roles. A strict hierarchy applies: you can only manage people below you, and only grant permissions you hold yourself. Roles can have a colour and a custom quota.

manage_server is the most powerful permission, since it covers the ER:LC key and structural settings. Treat it like admin.

The four command tiers (Helper, Mod, Admin, Co-Owner) are a labelling tool for your own hierarchy. Right now any of them opens the Panel's command box.

Shifts and quotas

In the Panel you can start a shift, take a break, end the break and end the shift, all with a live timer. Quotas are set per role. Users with view_shifts can see everyone's shift history, and users with force_end_shifts can end someone else's shift.

Activity waves

An activity wave runs for 1 to 4 weeks and tracks each member's progress against their role quota. Days a member spends on approved leave of absence are accounted for. Users with manage_activity can start, view and force-end waves.

Punishment logs

Log punishments with or without evidence links, and see a player's history the moment you look them up. Every server has these built-in types:

• Verbal Warning
• Warning
• Kick
• Ban
• Ban Bolo

A Ban Bolo is a ban recommendation. Someone with complete_ban_bolo completes it, which sends the ban to ER:LC (only if ER:LC is connected). You can edit or delete your own logs. Editing or deleting other people's needs edit_others_logs or delete_others_logs.

Custom log types are available too: up to 3 on the free plan, unlimited on Pro. Manage them in Dashboard › Log Types.

Staff infractions

Infractions are for staff, not players. They are typed, with no points system: Verbal Warning, Warning, Strike, Suspension and Termination. Every infraction has a reason and says whether it can be appealed. The Panel shows how many of each a member has. Issuing, viewing and revoking needs manage_infractions, and you can only act on members ranked below you. Members can always see their own history under Settings › Infraction History.

Infractions work in the Dashboard (Infraction Logs › Records) without any Discord set-up. The Discord side is the optional Infractions on Discord module:

Infractions on Discord

• /infract takes the staff member, a reason, the type (a dropdown) and whether it is appealable. All four are required.
• The staff member gets the Infraction Notice in a DM. You can change its wording and add a banner and a footer image under Infraction Logs › Discord & roles.
• Roles are optional and off by default. You can pick roles for Verbal Warning 1, 2 and 3, Warning 1, 2 and 3, Strike 1 and 2, plus the roles a Suspension or Termination gives, and the roles it takes away. A member's tier is how many active infractions of that type they have.
• Revoking an infraction undoes its roles: tier roles step back down, and roles a suspension or termination removed are given back.
• The person must have signed in to Orasty and be a member of your Orasty server. Orasty's role has to sit above the roles it manages. If a member has DMs closed, the infraction is still recorded and you are told the notice could not be delivered.

Leave of absence

Staff request time off from Settings › Manage LOA, for up to 90 days at a time. Users with manage_loa accept or deny requests in the Dashboard, and the owner can too. Everyone who can review (and the owner) gets a notification when a new request comes in, and the requester is notified of the decision. With the LOA Module on they also get the decision as a Discord DM. Approved leave ends automatically when the period is over.

Nobody can review their own request unless they own the server, and a request can be cancelled by the member while it is still pending.

LOA module and Discord requests

The LOA Module is optional and off until a manager enables it under Dashboard › Modules. It adds an LOA Module page to the Dashboard where you can post every new request to a Discord channel, so reviewers can answer without leaving Discord.

1. In LOA Module choose Add the Orasty bot (or reuse the Discord server Session Management already uses) and pick the Discord server.
2. Choose the text channel the requests go to.
3. Turn on Send requests to Discord. It stays off until a Discord server and a channel are set, and you can switch it off again at any time. Use Send test request to check the bot can post there.

Each request is posted as a Components V2 card with the requester, the reason and the dates, plus Accept and Deny buttons. Deny asks for an optional note. The person who clicks must have signed in to Orasty with that Discord account and hold manage_loa in your server (or own it). Once a request is handled, from Discord, the Dashboard, or because the member cancelled it, the card is updated and its buttons are disabled.

LOA commands and the decision DM

With the LOA Module on and your Discord server linked, members can use /loarequest (a reason, how many days, and optionally a start date) and /loaview to see their own requests. People with manage_loa can also look up someone else with /loaview user. When a request is approved or denied, Orasty DMs the member the LOA decision message. It shows the server, the status and the reason, and you can change its wording, banner and footer in the LOA Module page or under Discord › Embeds. If the member has DMs closed, the decision is still saved and the notification inside Orasty still arrives.

With the Discord option off, leave requests work exactly the same in the Dashboard. If a post to Discord fails (missing channel permission, deleted channel), the request is still saved and the LOA Module page shows what went wrong.

Modules

Modules are optional features. They are all off until someone with manage_server switches them on under Dashboard › Modules, and each one adds its own page to the Dashboard when it is on.

ER:LC integration

Add your ER:LC server key under Dashboard › ER:LC Integration (needs manage_server). Keys are encrypted in the database. Once connected you get:

• Who is in game right now
• A live feed of commands, joins and kills
• Sending commands by staff tier from the Panel
• Bans sent straight to ER:LC when a Ban Bolo is completed

This needs the ER:LC API pack on your game server. Without a connection, everything else in Orasty still works.

The Discord bot

The Orasty bot runs the slash commands and posts the messages you set up. Everything about it lives under Dashboard › Discord, which has five pages: Connection, Embeds, Verification, AFK and Log webhooks.

Connecting your Discord server

1. Open Discord › Connection and choose Add the Orasty bot, then go through Discord's add-bot page. The bot is invited with the Administrator permission so it can manage roles and nicknames. You can still limit what it sees with Discord's own channel permissions.
2. Orasty now knows which Orasty server your Discord server belongs to. One Discord server links to one Orasty server.
3. Turn on the modules you want (Session Management, LOA Module, Infractions on Discord, Verification, AFK). Each one can be switched off again at any time.
4. In Discord, drag the bot's role above the roles it should give or take away (Server Settings › Roles). Discord never lets a bot manage a role above its own, and Orasty cannot rename the server owner.

Servers whose owner has Orasty+ see the bot as Orasty Pro in their Discord server, and in the footers of its messages.

Slash commands

Permissions always come from the roles you set in Orasty, never from Discord roles. To use a staff command, sign in to Orasty once with the same Discord account. A command for a module that is switched off tells you so instead of doing anything.

Embeds: change every message

Every message the bot sends is a card you can customise under Discord › Embeds (and from the page of the feature it belongs to): the LOA decision DM, the Infraction Notice, the Verification panel and verified message, and the three AFK messages. For each one you can:

• change the title, the text and the footer text, or hide the footer text,
• add a banner across the top and a footer image (upload a file or paste a Discord image link; Orasty keeps its own copy),
• drop in variables such as {server}, {reason} or {status} with one click,
• see a live preview, send yourself a real preview by DM, switch the message off, or reset it to the default.

Banners and footer images default to nothing.

Verification

Verification links a member's Discord and Roblox accounts on Orasty and swaps their roles. Turn on the Verification module, then open Discord › Verification.

1. Pick the unverified roles (taken away) and the verified roles (given). Both are optional.
2. Choose the nickname: keep it, their Roblox username, their Discord username, Discord | Roblox, or a custom format using (@discordusername), (@discorddisplay), (@robloxusername) and (@robloxdisplay), with any characters of your own around them. Discord limits nicknames to 32 characters.
3. Post the Verification panel in a channel. It has a Verify button, and a Support button that is an invite to your Discord server.

A member presses Verify or runs /verify. If they linked their Discord and Roblox accounts on Orasty before, they are verified straight away and see the verified message. If not, they get a private link to an Orasty page where they sign in with Discord and connect Roblox, and are then verified. The link works once, for 15 minutes, and only for the Discord account that asked for it.

Orasty gives the unverified role to new members only if the person running Orasty has switched on the optional member intent. Otherwise add that role yourself or with another bot, and Orasty removes it on verification. The panel and the verified message can have their own banner and footer.

AFK

Turn on the AFK module so members can use /afk reason.

• Orasty puts AFK | in front of their nickname (where Discord allows it) and posts that they are away.
• The reason can never ping @everyone, @here or anyone else.
• When someone pings them, the bot replies that they are AFK and why, and remembers who pinged.
• When they next talk, the bot welcomes them back, says how long they were away and lists who pinged them. Their nickname is put back.

To see pings Orasty reads which people a message mentions, not what the message says. All three messages can be changed under Discord › AFK.

Session management and the bot

Session Management is a module, and it is off until a manager enables it under Dashboard › Modules. Users with manage_sessions can then run a session from the Dashboard:

• Start a vote so people can say they will join. Members vote with a button on the Discord message and can remove their vote again.
• Start up the session, with a quick join button.
• Boost a running session to ask for more players.
• Shut down the session when it ends, or cancel a vote that is no longer needed.

In Discord the same actions are slash commands, for anyone with manage_sessions: /ssu (Session Start Up), /ssd (Session Shut Down), /ssb (Session Boost) and /ssv (Session Vote). /ssv takes an optional number of votes, and uses the number set in the Dashboard when you leave it empty.

Setting up the bot

1. In Session Management choose Add the Orasty bot and go through Discord's add-bot page. Orasty's bot is invited with the Administrator permission, so you can limit what it sees with Discord's own channel permissions.
2. Back in Orasty, pick the text channel that should get updates.
3. Use Send test message to check it works. Remove bot makes the bot leave that Discord server, unless the LOA Module still uses it.

Session cards (and every other Orasty message) can show a banner and a footer image, plus a footer line. Upload a file or paste a Discord image link: Orasty keeps its own copy, so the picture never expires.

If a notification fails (missing channel permission, deleted channel), the session action still goes through and Orasty tells you what went wrong.

Log webhooks

Under Discord › Log webhooks you can send in-game logs, kills, joins, shift starts and server audit logs to Discord channels using webhooks. Webhooks are separate from the bot, and need nothing but a webhook link from the channel's settings in Discord.

Support code

Open Settings › Support to get a short code like AB3D-9XKM. Read it out to Orasty staff in the official support server so they can tell it is really you. Press Copy code to copy it.

• The code resets every 30 minutes, and the page counts down to the next reset.
• Staff never need your password, your login details or your ER:LC key. If anyone asks for them, it is not Orasty.

Free and Pro

See all plans on the Plans page, and the Refund Policy for billing and cancellation.

Shortcuts and tips

• Ctrl/Cmd + K or / opens the command palette from anywhere in the app. On this page / jumps to the search box.
• The bell in the bottom bar shows notifications, and the clock button opens the Changelog with what changed in each version.
• The bug button sends a bug report straight to the team.

Help and support

• Something not loading? Check the status page.
• Questions or bug reports: the support server or [email protected].
• Banned or warned? Details are on your notice page, and bans can be appealed in the support server.