How to manage boosting orders with a team
Roles, game scopes, assignment rules, acceptance windows, progress updates, and booster earnings for organized teams.
Scope access instead of sharing one login
A booster normally needs the assigned order, required execution details, relevant conversation, progress controls, and their earnings. They do not automatically need billing, every buyer message, global pricing, or all inventory.
Permissions should be enforced by the server and database, not only by hiding menu items.
Choose an assignment policy per game
Different services need different policies. A small team may use manual assignment. A larger team may use weighted rotation, skill match, capacity match, first-accept, or scheduled shifts. The owner should be able to override a result with a recorded reason.
When a member must accept an assignment, set a deadline and return expired assignments to the pool automatically.
Make earnings predictable
Earnings can be fixed, percentage-based, game-specific, service-specific, or overridden for one order. The chosen rule should be captured when the order is assigned so later configuration changes do not rewrite history.
Cancellation and refund events should create clear reversals. This prevents disputes between the owner and team members.