Managing Seats
Every developer who uses Codity occupies a seat in your subscription. Seats are tracked per organization and per VCS provider.
How seats are assigned
Seats are assigned automatically when a developer interacts with Codity for the first time, for example, when Codity reviews their pull request or when they appear in analytics. You can also manually add or remove developers from the Seats section on the Subscription page.
Viewing your seats
Go to Subscription → Seats in the dashboard to see all developers currently occupying a seat.
Removing a developer
To free up a seat:
- Go to Subscription → Seats.
- Find the developer you want to remove.
- Click Remove.
Removed developers will no longer have Codity services active on their pull requests. If they open a new pull request after being removed, Codity will attempt to auto-assign a seat. In case no seats are available, they will be blocked.
Seat limits
If your organization exceeds its purchased seat count and seat enforcement is active, additional developers will be blocked from using Codity services until you either add more seats or remove inactive developers.
Permissions
From the Seats section you can also grant or revoke access for Analytics service for individual developers without removing their seat entirely.
Manage seats through the API
Use the Subscription API to assign or remove seats and grant or revoke analytics access from your own tools. The reference covers API key setup, provider identities, request examples, and blocked responses.
Analytics access level 2 also grants applicable account administration privileges; grant it only to someone who should manage that account. Removing an active seat frees assigned capacity but does not reduce purchased seats or billing.

