Loading image...Kiro

Product

  • About Kiro
  • Agents
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Case studies
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Videos
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Kiro
  • Agents
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effortAWS GovCloud (US) models

Features

How Kiro worksLocal command sandboxACP integrations
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Workflows
Agent Skills
Powers
Cloud sessionsMemoryCompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Experimental
Troubleshooting0.x reference

CLI

Setup & First RunChoose an agent harness
Terminal UI
Chat
Fullscreen modeVoice modeHeadless modeACPAuto complete
Experimental
Troubleshooting
Upgrade from CLI 2.x
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Features
Interfaces
Apps
System & storageConfigurationSecurityTroubleshooting

Web

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeScheduleConfiguration Sync
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettings

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Deployment optionsSubscribe your teamManage subscriptions
Credit pooling
Overview
Manage seats
Manage usage limits
Monitor usage
Add credits
Governance
Monitor and track
SettingsManaged updatesTLS inspection compatibilityBillingIAMSupported regions
AWS GovCloud (US)

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

OverviewRunning Kiro in the cloud
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  2. Enterprise
  3. Credit pooling
  4. Manage seats
View as Markdown

Manage seats

View as Markdown

Every user who draws credits from the pool needs a seat. You give users access by adding them directly or by adding a group they belong to. In the Kiro console, you manage the pool under Access management > Credit sharing.

Before you begin

  • Your role must allow q:GetPaymentModelEligibility, q:CreateAssignment, q:DeleteAssignment, q:AssignSeats, q:DeleteSeats, and user-subscriptions:ListSeatAssignments. The full Kiro administrator policy includes these actions and other Kiro administration permissions.
  • Users and groups must exist in AWS IAM Identity Center or in the external identity provider synced to it.
Prepaid and postpaid pools

Pools are billed either prepaid or postpaid. The billing model is set for your AWS account and is shown in the purchase summary and on the Credits tab. Prepaid pools show the Add seat purchase action and follow the seat assignment steps on this page. Postpaid pools have no fixed seat count to buy, so members are seated automatically.

Buy seats for a prepaid pool

  1. Open Access management > Credit sharing and choose Add seat.
  2. In How many seats do you want?, enter the number of seats.
  3. Review the Buy seats purchase summary, then choose Confirm Purchase.

Each seat is $20 per month and contributes 500 monthly credits to the pool. The credits are added to the pool as soon as the purchase completes; you do not need to assign a user first. Seat price and credits are prorated for the first month, and the full seat price is due at the next billing cycle. Seats you buy later are prorated the same way.

Add users and groups

Add a user

  1. On the Credit sharing page, open the Users tab and choose Add user.
  2. Search for the user in IAM Identity Center or your synced identity provider, and select the user.
  3. Repeat to add more users, then confirm the dialog.

Add a group

  1. On the Credit sharing page, open the Groups tab and choose Add group.
  2. Search for the group and select it.
  3. Repeat to add more groups, then confirm the dialog.

Adding a group does not add seats. In a prepaid pool, members of the group are seated the first time they use Kiro, if a seat is available; postpaid pools seat members automatically. Users who appear in more than one group are counted once and are not charged twice.

Assign seats

In a prepaid pool, a user you add gets a seat in one of two ways:

  • You choose Assign seat for the user on the Users tab.
  • A seat is free when the user opens Kiro, and the seat is assigned automatically.

The user's status on the Users tab shows Seated or Awaiting seat.

When seats run out

If you add more users than you have free seats, the console adds them with Awaiting seat status and opens the Add seat checkout for the shortfall. After the purchase completes, each user remains in Awaiting seat status until they activate their Kiro account from any Kiro client. Kiro assigns the seat when activation completes.

Postpaid pools seat every member automatically, so there is no shortfall and no Add seat action.

Remove users and seats

Remove a user

  1. Open the Users tab and select the users to remove.
  2. Choose Remove user from seat.
  3. In a prepaid pool, removing the user frees their seat assignment. To schedule that seat for removal, select Remove seat at the end of the month. If you select this option and the seat remains unassigned, it is removed at the end of the billing cycle. Postpaid pools have no purchased seats to remove, so this option does not appear.
  4. Confirm the removal.

Removing a user's direct assignment ends their pool access immediately unless they still belong to an added group. Credits they already used are not returned. Removing a user does not remove unused credits from the pool: monthly credits remain available until the end of the billing cycle, and additional credits retain their original expiration dates.

You can only remove users who have been assigned a seat. Users who belong to a group you added cannot be removed here. First remove them from the group in IAM Identity Center or your synced identity provider (see Connecting your identity provider). If they were also added directly, remove them under Users.

Remove a group

  1. Open the Groups tab and select the group.
  2. Choose Remove group and confirm.

Removing a group ends pool access immediately for members who do not also have access through a direct assignment or another added group.

Remove unassigned seats from a prepaid pool

To stop paying for seats nobody uses in a prepaid pool, choose Remove unassigned seat on the Credit sharing page. The seat is scheduled for removal at the end of the billing cycle and shows Pending removal until then. This action does not appear for postpaid pools.

Related resources

  • Credit pooling: Overview of how the shared pool works
  • Manage usage limits: Control each user's usage with user, group, and profile limits
  • Monitor usage: Track pool balance and projected consumption
  • Enterprise billing: Understand subscription tiers and included credit allowances
  • Managing Kiro subscriptions: Change plans, unsubscribe users, and enable overages

Next step

Go to Manage usage limits to control each user's credit use with user, group, and profile limits.

Page updated: November 4, 2026
Credit pooling
Manage usage limits