Team Member Quotas

Team member quotas help you control shared point usage without turning routine collaboration into manual bookkeeping.

What this feature does

Team member quotas let an owner or admin assign a monthly team-point limit to each active teammate.

You can use it to:

• keep some teammates unlimited
• cap monthly usage for specific members
• block team-point usage for a member by setting the value to 0
• review used/limit directly from the member list

This is useful when one team balance supports multiple contributors with different responsibilities.

Where to find it

Open the team management area and go to the member list.

From there you can:

• scan each member's compact used/limit summary
• open Quota Settings when you need to change policy

The member list is the fastest place to inspect current status. The dialog is where you make detailed adjustments.

How to set limits

1. Decide which members should be limited

A simple starting point is:

• keep owners or leads unlimited
• assign a monthly cap to recurring contributors
• use smaller caps for temporary collaborators

2. Open Quota Settings

Use the Quota Settings entry in the team member area.

3. Choose one of three states per member

• Blank means unlimited
• Positive number means a monthly point cap
• 0 means the member cannot spend team points

This keeps the configuration model simple and easy to explain to the team.

4. Save and review from the member list

After saving, return to the member list and use the compact used/limit column as your ongoing monitoring view.

How to read the member list summary

The summary is shown as used/limit.

Examples:

• 720/1800 means the member has used 720 points out of a monthly limit of 1800
• 90/∞ means the member has used 90 points and currently has no monthly cap

This makes weekly review much easier because you can compare members from one table instead of opening each profile.

Reset behavior

Usage resets automatically on the first day of each UTC month.

That means quota planning works best when teams review limits on a monthly rhythm.

Suggested operating pattern

A practical lightweight workflow is:

1. set initial limits when a teammate joins the project
2. review the member list once a week
3. raise or lower limits only when working style changes
4. keep the policy easy enough that every admin can explain it quickly

If your team already collaborates in one shared Musein workspace, member quotas add a simple but useful control layer around shared point usage.