[Feature Request] Per-user overage toggle for IAM Identity Center organizations

[nczz]

Feature Description

Currently, the Overages setting in the Kiro console for IAM Identity Center (IDC) organizations is an all-or-nothing toggle — when an admin enables overages, it applies to every user in the organization. There is no way to enable or disable overages on a per-user or per-group basis.

This creates a significant cost management problem for organizations:

• If enabled: Every user in the organization can incur overage charges with no individual limit, making it impossible to control spending at the user level.
• If disabled: No one in the organization can use overages, even power users or team leads who genuinely need the extra capacity.

Proposed Solution

Allow IDC administrators to control overages at a more granular level:

1. Per-user or per-group overage toggle — Enable/disable overages for individual users or groups, not just the entire organization.
2. Per-user overage spending cap (nice to have) — Set a maximum overage budget per user/group per billing cycle.

Use Case

As an IDC organization admin, I want to:

• Enable overages only for senior developers or specific teams who need uninterrupted access
• Keep overages disabled for most users to prevent unexpected costs
• Have visibility and control over who can incur additional charges

Current Behavior

Settings → Kiro settings → Overages toggle → applies to all users in the organization.

Expected Behavior

Settings → Kiro settings → Overages → configurable per user or per group (e.g., via IDC group assignment or a user-level override in the Kiro console).

Additional Context

The current organization-wide toggle is too coarse for any team with more than a handful of users. Fine-grained cost control is a basic expectation for enterprise billing management.

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #6886: Feature Request: Granular control over content collection by feature module (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both request granular control over settings that are currently all-or-nothing toggles - new issue wants per-user overage control, existing issue wants per-feature content collection control. Same core problem of needing more granular administrative controls.

[nczz]

This is not a duplicate of #6886.

• Feature Request: Granular control over content collection by feature module #6886 requests granular control over content collection (data privacy / telemetry settings per feature module).
• This issue ([Feature Request] Per-user overage toggle for IAM Identity Center organizations #7599) requests granular control over overage billing (per-user or per-group overage toggle for IAM Identity Center organizations).

These are completely different domains — one is about data collection preferences, the other is about cost management and billing control. The only similarity is that both happen to request "granular control," but the subject matter, affected settings, and use cases are entirely unrelated.

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[nczz]

Hi team, just following up on this.

I noticed the Enterprise Subscription Management docs (updated 2026-03-19) now states:

Setting custom caps for overages is not yet supported (coming soon).

This confirms the need is recognized. Could you share an estimated timeline for this feature? For organizations using IAM Identity Center, the current all-or-nothing overage toggle at the profile level makes cost governance very difficult — we either block everyone when credits run out, or accept unbounded overage charges across all users.

Even a simple per-user or per-group overage cap (e.g. max 200 overage credits/month) would be a huge improvement for enterprise cost management. Thanks!