Plutana HR is a project management and team coordination platform. It combines project tracking, task management, hiring workflows, time tracking via the Roblox Studio plugin, and fair payout calculations into one unified studio.

How the platform works end-to-end

First-time setup sequence

1. 1Click Create Studio on the dashboard. Name your studio and create the studio.
2. 2Go to Settings → Invite Members. Select a permission group for new members, choose a link expiry, and click Generate Invite Link. Share the link with your team.
3. 3Still in Settings, open the Departments section. Click New Department to create your teams (e.g. Scripters, Builders). Set a budget weight for each — these control how the payout pool is divided.
4. 4Assign members to departments using the member picker in each department card.
5. 5Go to Groups & Perms and configure permission groups. The three system groups (Owner, HR, Developer) are created automatically — customise or add more as needed. See the Permission Groups section for suggested setups.
6. 6Create a Project from the Projects page. Add milestones to structure the work, then create tasks within the project and assign them to team members.
7. 7If using Roblox Studio integration: have each developer go to their Profile (avatar top-right) → generate their User Token → open the Studio plugin, paste the token, and click Connect.
8. 8At month-end: log revenue in Revenue, then go to Payouts to preview and run the payout cycle.

Projects are the top-level organisational unit. Each project contains milestones (phases of work) and tasks. The Projects page uses a master-detail layout — select a project from the list on the left to see its full detail view on the right.

Project detail view

Creating a project

1. 1Navigate to Projects in the studio nav (requires project:view).
2. 2Click New Project. Enter a name and optional description.
3. 3Once created, select the project from the list — its detail panel opens on the right.
4. 4Add milestones to structure the work: click Add Milestone, give it a name and an optional target date.
5. 5Create tasks via the Projects page or via any task creation flow. When creating a task, set its Project and Milestone to organise it.

Milestones

Milestones represent phases or deliverables within a project — for example, “Alpha Build”, “Beta Testing”, or “Launch”. Each milestone shows a summary of how many tasks are in each status, giving a quick progress read without opening individual tasks.

Project status

Projects have a status (Active, On Hold, Completed, Archived) that is shown as a colour-coded badge in the project list. Archived projects are hidden by default — no tasks can be added to an archived project.

Permissions required

Tasks are the primary unit of work. Each task lives in a project and department, can have one or more assignees, and flows through a status pipeline. Completed and verified tasks directly drive each developer's payout share. Manage tasks from the Projects page — select a project to see and interact with its tasks.

Task lifecycle

Creating tasks

Navigate to Projects, select a project, and click New Task. A modal opens with a bulk-creation grid — you can add as many rows as you need in one go. Each row requires a title and a department; priority, milestone, and assignees are optional.

Multiple assignees & split pay

Tasks support multiple assignees. In the creation modal and the edit overlay, use the assignee picker to add as many team members as needed. Assignees are shown as chips — click the × on any chip to remove them.

In the task table, if a task has no assignees a + Claim button appears for members to self-assign. If a task already has assignees, a small join icon lets non-assigned members add themselves as co-assignees.

Editing tasks

In the project detail view, click any task row to open an edit panel showing title, description, assignees, priority, due date, status, and milestone. Save changes directly from the panel.

Verification workflow

When a developer marks a task Completed, it appears in the Verification Queue on the Dashboard. Managers with task:verify can click Verify to approve it from the dashboard — or navigate into the project to review it in context.

Permissions required

The Hiring system manages the full applicant journey — from the public application link through to onboarding as a studio member. Access it via the Hiring dropdown in the studio nav. Each studio has one permanent hiring link — HR and Owners can open or close applications at any time without changing the URL.

How the hiring link works

Hiring pipeline stages

Setting up hiring

1. 1Go to Hiring in the studio nav (requires hiring:manage).
2. 2On the Links tab, click Create Hiring Link. Enter a title, optional description, and select which group new members will join after acceptance.
3. 3Copy the link URL and post it wherever you recruit. The link is permanent — it does not expire.
4. 4When ready to accept applicants, click Open Applications. To pause hiring, click Close Applications.
5. 5Applicants appear in the Applications tab. Review and move them through the pipeline using the action buttons.

Applicant experience

Applicants can track their own application status from their Profile → Applications tab on the Plutana HR site. Each application card shows the current stage and links through to the interview thread. Application data (form answers, messages) is automatically deleted 7 days after the application is accepted or rejected.

Documents during onboarding

If your studio has any blocking documents enabled — an NDA, studio rules, or anything else — new members who join via a hiring invite are prompted to sign or acknowledge them before they can access any studio content. This is enforced automatically — no manual follow-up needed.

Permissions required

Performance Reviews let managers record formal assessments for studio members. Reviews appear on each member's profile and are visible to members with thereview:view permission.

Review types

Creating a review

1. 1Go to Insights → Reviews in the studio nav (requires review:view).
2. 2Click New Review. Select the member and enter the review title and content.
3. 3Click Save — the review is saved immediately and visible to members with review:view.

Deleting a review

Members with review:manage can delete manual reviews they created. Automated reviews (system-generated) can only be deleted by the studio Owner. A confirmation is required before deletion.

Permissions required

The payout system distributes Robux from each department's budget to developers based on their verified task performance and active Studio time within a selected period.

Payout formula in detail

Payout formula slider (Settings)

In Settings → Studio Settings, the Payout Formula slider controls how much weight is given to tasks vs Studio time. Drag left for more Studio-time emphasis, drag right for more task emphasis. The two percentages always sum to 100%.

Running a payout — step by step

1. 1Navigate to the Payouts tab in the studio nav (requires payout:view).
2. 2Set the Period Start and Period End dates. These default to the current calendar month.
3. 3Click Preview — a per-department, per-developer breakdown appears instantly. Review it carefully before committing.
4. 4When satisfied, click Run & Persist (requires payout:approve). The results are saved to the permanent ledger.
5. 5In the Unpaid ledger section, click Mark Paid for each developer after you have issued their Robux in-game.

Payout ledger

The ledger at the bottom of the Payouts page shows a permanent record of every payout run. Filter by status (Unpaid / Paid) or by department. Each entry shows the developer, department, period, their raw score, and exact Robux amount. Once marked as paid, entries are locked.

Department budgets and weights

Each department has a payout weight (configured in Settings → Departments). The studio's total monthly revenue is split among departments proportionally to their weights. Weights should sum to 100% — the settings page will warn you if they don't.

The Revenue page is where you log your studio's monthly Robux earnings. Logged revenue feeds into the payout calculation — the monthly figure is multiplied by each department's weight to determine the department budget for that cycle.

Logging revenue

1. 1Navigate to Revenue in the top studio nav (requires workspace:settings).
2. 2Select the month and year using the dropdowns.
3. 3Enter the total Robux earned for that month. Optionally add notes (e.g. "includes game-pass launch boost").
4. 4Click Log Revenue. The entry is saved and appears in the bar chart.
5. 5To update a previously logged month, select the same month/year, enter the corrected amount, and submit again — it overwrites the previous entry.

Reading the chart

The bar chart shows the last 12 months at a glance. Hover over a bar to see the exact Robux amount. The current month is highlighted in green. Months with no logged revenue appear as empty bars.

Departments represent the distinct teams within your studio — for example, Scripters, Builders, UI Designers, or QA. Every member must be in a department to receive payouts. New studios start with no departments — you create them yourself.

Creating departments

1. 1Go to Settings (requires dept:manage or workspace:settings).
2. 2Click New Department and enter a name.
3. 3Once created, set a Payout Weight — this is a percentage that controls how much of the total revenue pool this department receives. All department weights should add up to 100%.
4. 4Use the member picker at the bottom of each department card to assign studio members to that department.

Deleting departments

Click the trash icon on a department card. Members assigned to the deleted department are unassigned — reassign them manually. Tasks that belonged to the department are also deleted.

Permission Groups control what each member can see and do in Plutana HR. Every member inherits the combined permissions of all groups they belong to. Studio owners always have full access regardless of group membership.

System groups

Six system groups are created automatically when a studio is made. They cannot be renamed or deleted:

Managing groups

1. 1Go to Groups & Perms in the studio nav (requires group:view).
2. 2Click New Group to create a custom group. Give it a name, description, and a colour.
3. 3With the group open, tick the permission tokens it should grant. Changes save immediately.
4. 4Add members to the group via the member picker. Members can be in multiple groups — they receive the union of all their groups' permissions.

All permission tokens

Suggested custom group setups

The Member Context Menu (right-click any member card on the dashboard) gives quick access to common member actions without navigating away. The options shown depend on your permissions.

Context menu actions

Firing a member

Members with member:terminate can access the Admin → Fire Member page. It lists all active members — excluding yourself and the studio owner, who cannot be removed this way.

1. 1Go to Admin → Fire Member in the studio nav.
2. 2Search for the member by name using the search box.
3. 3Click Fire next to the member.
4. 4Enter a reason (minimum 10 characters) — this is logged and sent to the member as a notification.
5. 5Click Confirm Fire. Their access is removed immediately.

Permissions required

The Plutana HR Studio Plugin runs inside Roblox Studio. It tracks each developer's active editing time, shows their assigned tasks, and lets them update task status without leaving Studio.

Installing the plugin

1. 1Open Roblox Studio and click the Plugins tab in the ribbon.
2. 2Click Manage Plugins, search for Plutana HR, and click Install.
3. 3A Plutana HR toolbar button will appear in Studio.

Plugin V1.2 — User TokenCurrent

V1.2 uses a single User Token that works across all your studios. The correct studio is auto-detected from the PluHR_Config ModuleScript in ServerScriptService.

1. 1Click your avatar (top-right of the Plutana HR web app) → Profile → click Generate to create your User Token.
2. 2Click Show to reveal the full token, then copy it.
3. 3Open Roblox Studio → click the Plutana HR toolbar button → paste your User Token and click Connect.
4. 4The plugin reads PluHR_Config in ServerScriptService to detect your studio automatically.
5. 5Developer view opens: assigned tasks, session timer, and task status controls.

What the developer plugin shows

How time tracking works

V1.2 tracks time via script editor keystrokes — every time you type in the script editor, a heartbeat is sent to Plutana HR. Sessions are auto-closed after 15 minutes with no heartbeat. Active seconds are accumulated per session and used in the payout calculation at month-end.

Plugin V1 — Studio TokenDeprecated

V1 tokens still work but will not receive new features. Migrate to V1.2 by generating a User Token on your Profile page.

The Roblox account registered as the studio owner sees a different view in the Studio plugin — the Owner Dashboard. Members with plugin:deploy who are not the owner are routed to the standard developer view.

Owner Dashboard features

Team Chat is a studio-scoped channel visible to all members. It's accessible from the studio nav. Use it for quick team-wide announcements, sprint updates, or coordination.

Chat features

The Team Status panel on the studio dashboard shows a real-time presence overview of every member. It requires the session:view permission.

Presence indicators

Session time display

For members with an active Studio session, the panel shows their total active seconds for the current session in hours/minutes (e.g. 2h 15m). This accumulates only while they are actively typing in the script editor.

Flagging members

Members with user:flag can click the flag icon on any member card to flag them for manager review. Flagged members appear highlighted in the admin panel. Click the flag again to remove it.

The Profile page is accessed by clicking your avatar or username in any navigation bar. It has two tabs — Profile and Applications — and requires no studio permissions.

Profile tab

Applications tab

The Applications tab shows every hiring application you have submitted across all studios, with live status updates. Click any application card to open the interview thread for that application.

The Document System lets studio Owners and HR create any number of documents — a real NDA, studio rules, an explainer on how sanctions work, or anything else — and decide how much ceremony each one needs. A real legal agreement can require a full signature; most other documents just need a one-click acknowledgment, or nothing at all if they're purely informational.

Three signature styles

Creating a document (Owners & HR)

1. 1Go to your studio and click Documents in the top navigation bar (visible to all members).
2. 2Click New Document and pick a starting point — a Non-Disclosure Agreement, Studio Rules, How Sanctions Work, How Payouts Work, or a Blank document.
3. 3You're taken to the document's page. Open Document Management to review and edit the generated text, choose its signature style, and decide whether it blocks entry.
4. 4Set the Grace period — how many days existing signers/acknowledgers have to re-confirm after a future update (default: 7 days).
5. 5Toggle Enabled on to make it visible to members.

Templates

Each starter template fills in a full draft and a sensible default signature style — review and adjust before enabling.

Signing or acknowledging (Developers)

When a document blocks entry and you haven't completed it yet, you'll be redirected to it the next time you visit any studio page. A Sign-style document shows the same fields as a legal agreement always has:

An Acknowledge-style document just needs a single "I've Read This" click — no personal fields, no scroll gate.

Version updates & grace periods

If an Owner or HR member updates a document's text, the system stamps a new version date. Existing signers/acknowledgers are considered valid for the duration of the configured grace period (default: 7 days). After the grace period expires, members who acted on the old version are prompted to act again.

New members (or anyone who hasn't completed it at all) must always act on the current version immediately.

Viewing acknowledgments

On a document's page, the Acknowledgments tab is visible to members with thedocument:manage permission. For a Sign-style document it shows each member's Discord username, Roblox username, age status, and the date they signed — legal names are hidden by default, click the eye icon next to a name to reveal it. Acknowledge-style documents show just the member and date.

Each row shows one of three statuses:

Permission required

Plugin errors

Payout issues

Studio and member issues