Summary:
Currently, Rovo Dev credits (used for features like automated Pull Request reviews in Bitbucket) are deducted from the individual allocation of the PR author. When a high-volume contributor exhausts their monthly credits, Rovo Dev features stop functioning for their PRs until the next billing cycle, even if other team members have remaining credits.

Requested Behavior:
Provide an option for organization admins to enable a "shared pool" or "org-level wallet" for Rovo Dev credits. This would allow the team's total credit allocation to be managed collectively, ensuring that active contributors can continue using Rovo Dev as long as the organization has credits available.

Why it matters:

• Team-level Functionality: Code review is a team-level quality function. The current model penalizes the most active contributors.
• Reliability: Teams using Rovo Dev as a required merge check face workflow blockers when individual credits run out mid-cycle.
• Administrative Overhead: Managing individual limits is complex for large teams; a shared pool aligns better with how teams actually consume resources.