Staff Quota

Staff Quota lets you enforce in-game activity goals for your staff members. Each quota defines how many minutes a staff member must be active in your Roblox experiences over a given period. When the period ends, staff who fell short generate a pending action that a Discord Administrator reviews and approves or rejects.

Accessing Staff Quota

1. Select your server in the dashboard
2. Click "Staff Quota" under Staff in the sidebar

Requires a registered Roblox game. Quotas are measured from Roblox game-session data. If you haven't registered at least one Roblox experience yet, the page prompts you to add one under Settings first.

How Quotas Work

1. You create a quota with a required number of minutes and a period (e.g. 120 minutes per week).
2. The quota optionally targets specific staff roles. With no roles selected, it applies to every active staff member.
3. While the period runs, every Roblox game session of a staff member (across your registered games) counts toward their quota.
4. When the period ends, Technified checks every targeted staff member. Anyone below the required minutes generates a pending action.
5. A Discord Administrator approves or rejects the action from the dashboard. Approved strikes are issued automatically.

Staff who don't have a linked Roblox account are excluded from quota checks. Otherwise they'd always show zero minutes and be flagged unfairly.

Creating a Quota

Click New Quota to open the create dialog.

Every failure action requires a Discord Administrator to approve before it takes effect. Nothing happens automatically to your staff without human sign-off.

One quota per role

You can't have two enabled quotas targeting the same staff role at the same time. If you try to create or enable a second quota that overlaps an existing one, the dashboard returns a 409 error. This prevents double-counting and conflicting expectations.

If a quota has no role filter, it counts as targeting every staff member, so you can only have one "all staff" quota enabled at a time.

Failure Actions

Rejected pending actions are archived and take no effect.

Active Quotas

The main page shows every quota you've configured. Each row displays:

• Name and enabled/disabled badge
• Required minutes and period (e.g. "2h required every 7d")
• Failure action badge
• Number of targeted roles (if any)

Quota controls:

• Enable / Disable: toggle without deleting. Disabled quotas stop generating pending actions immediately.
• Delete: permanently remove the quota and its pending actions. Approved historical strikes are preserved.

Changing the period of an existing quota re-anchors it to the current time and resets the schedule tracker. Missed periods from before the change are not retroactively processed.

Pending Approvals

The Pending Approvals section lists every quota miss waiting on review. Each entry shows:

• Staff member (username or Discord ID)
• Achieved vs required minutes for the period
• Period end date
• Proposed action and severity

Approving actions

Only Discord Administrators can approve or reject pending actions. Staff with quota edit permission can view them but not resolve them. Quota actions can result in strikes, so final sign-off stays with server owners.

• Approve: executes the failure action (issues the strike for strike, otherwise just marks it approved)
• Reject: archives the action. No strike or warn is recorded.

The /leftquota Command

Staff members can check their own quota progress at any time with the /leftquota slash command in Discord. The response is ephemeral (only visible to them) and shows, for every quota that applies to them:

• A progress bar
• Achieved / required minutes
• Minutes remaining
• When the current period resets

This is the easiest way for staff to know where they stand without asking a manager.

How Minutes Are Counted

Quotas use Roblox game-session data tracked by the Technified Adonis plugin:

1. Every time a staff member joins a registered Roblox game, a session is started.
2. The session keeps a live heartbeat and an end time when they leave.
3. For each staff member, Technified sums the overlap between their sessions and the current quota period.
4. Live (in-progress) sessions count toward the current period. Staff see their minutes increase in real time.

If a quota has specific game IDs configured, only sessions in those games count. With no game filter, every registered Roblox game counts.

Required Permissions

Configure staff permissions under Staff Roles.

Best Practices

Start small

Pick a realistic minute count. A weekly quota of two or three hours is a reasonable starting point for most moderator teams. Adjust based on how your staff actually behave.

Match periods to review cadence

If your leadership reviews staff weekly, use a weekly quota. Monthly quotas mean one month of potential under-performance before you see it.

Use "Notify Only" first

Roll out a new quota with Notify Only for the first period. You'll see exactly who would have been flagged without any strikes being issued. Then upgrade to Strike once you're confident the numbers are right.

Approve in batches

Pending actions stack up at the end of each period. Set aside time right after a period ends to review them all together. The context is freshest then.

Communicate before enforcing

Tell your staff the quota exists, how it's measured, and what happens when they miss it. /leftquota should be something they run voluntarily, not something they discover when they get struck.

Related Sections

• Staff Roles: configure which roles quotas apply to
• Strikes: where approved quota strikes end up
• Staff Activity: live activity tracking and leaderboards
• Adonis Plugin Features: how session tracking is implemented