Track experience and quotas

Experience records long-term community progression. Quota points measure progress toward a configured requirement or period. Communities can use either or both without treating them as the same score.

Update experienceCopy link to Update experience

Authorised staff can change a member’s experience from their profile or with the community’s configurable experience command, commonly /xp. Depending on settings, the workflow can add, remove, or set a value and can support a reason.

1. Confirm the target account and current balance.
2. Choose the intended operation and amount.
3. Enter a useful reason when requested.
4. Confirm the result in the profile and audit log.

The default requirement for changing experience is Officer; setting an absolute experience value defaults to Owner. Community owners can change those requirements.

Update quota pointsCopy link to Update quota points

Use the member profile or /quotapoint for permitted quota changes. The default requirement for ordinary quota changes is Officer, while setting an absolute total defaults to Owner.

Quota settings define what is measured and when it applies. Staff should not manually reset or compensate scores until they understand the configured period and any event awards.

View progressCopy link to View progress

Use /leaderboard or the corresponding Clan Labs view to compare eligible member totals. A member profile shows the person’s own progression context. Results can differ from a raw Roblox rank because Clan Labs progression is community data.

Automated progressionCopy link to Automated progression

When enabled and included by the plan, automated progression evaluates configured experience and qualification requirements before moving a member through eligible ranks. It still respects active suspensions, blacklist rules, configured rank boundaries, Open Cloud access, and Roblox’s current group state.

An automated check that cannot safely determine suspension or rank state stops without guessing. Resolve the underlying service or configuration problem before repeating a manual rank change.

Event awardsCopy link to Event awards

Event types can define host, co-host, and attendee experience or quota awards. An event snapshots its type configuration when created, so changing a reusable type later does not rewrite that existing event’s awards.

Good operating practiceCopy link to Good operating practice

• Publish a clear community policy for how points are earned.
• Use reasons and audit records for manual adjustments.
• Restrict absolute set actions more tightly than incremental changes.
• Test progression boundaries with a non-privileged member.
• Do not repeatedly submit a failed award; verify the existing balance first.

Configure the features with Experience setup and Quota setup. If Discord does not reflect the result, see Profile does not sync.