---
title: How do you find unused GitHub Copilot, ChatGPT Enterprise and Claude seats?
url: https://opencontroller.lyzr.com/blog/find-unused-ai-seat-licences
published: 2026-11-13
updated: 2026-11-13
author: Lyzr
---

# How do you find unused GitHub Copilot, ChatGPT Enterprise and Claude seats?

**Pull the last-activity date for every assigned seat from each vendor, join it to your identity provider, and flag seats with no activity for 30 days or more. GitHub Copilot exposes `last_activity_at` per seat through its REST API, ChatGPT Enterprise exports a Users report with last-active dates, and Claude Enterprise shows member and spend data in its usage analytics. Then run a remind-then-reclaim policy every month.**

AI seats are bought in bulk during rollouts and rarely trimmed afterwards. Each vendor exposes activity differently, and each has a retention quirk that can make an active user look idle or the reverse.

## What activity data does each vendor expose?

| Tool | Where to look | Activity field | Limits to know |
|---|---|---|---|
| GitHub Copilot | REST: list seat assignments for an organisation (`/orgs/{org}/copilot/billing/seats`) | `last_activity_at`, plus `assignee.login` | Since February 2025, `last_activity_at` is kept for a rolling 90 days, then set to null. New or reassigned seats show null until first use |
| GitHub Copilot | REST: user-level usage metrics reports per enterprise or organisation | Daily and 28-day per-user reports (NDJSON) | Enterprise reports need the Copilot usage metrics policy set to "Enabled everywhere" |
| ChatGPT Enterprise | Workspace settings → Workspace analytics → Users report (CSV) | `is_active`, `last_day_active_in_period`, `last_day_active` | Custom ranges up to 12 months; CSV only |
| Claude Team / Enterprise | Admin usage analytics, spend CSV, Analytics API | Members view; per-user, per-model spend rows with email | Analytics API keys (`read:analytics`) can only be created by the Primary Owner |

Two consequences matter. For Copilot, a null `last_activity_at` means "never used in this org or not used in 90 days", not "unknown". Treat it as idle but check the seat's `created_at` first, so you do not flag someone assigned yesterday. For ChatGPT Enterprise, use `last_day_active` rather than the in-period field, because it looks across prior periods too.

## What counts as an unused seat?

Pick thresholds you can defend and apply them the same way to every tool:

1. **New seat grace period:** ignore seats assigned in the last 14 days.
2. **Idle:** no activity for 30 days. GitHub's own example workflow for reminding inactive Copilot users uses 30 days.
3. **Reclaim:** still idle 30 days after a reminder.
4. **Exceptions:** people on leave, seasonal roles, or seats kept for a named project. Record the reason and an expiry date.
5. **Leavers:** any seat still assigned to someone disabled in the identity provider is reclaimed immediately, whatever its activity.

## How do you run the monthly review?

1. Export activity from each vendor on the same day.
2. Map each vendor identifier to an IdP identity. GitHub usernames often carry no email, so you need a mapping step; see [how to attribute GitHub Copilot usage to employees](/blog/attribute-github-copilot-usage-to-employees).
3. Join to HR status and cost centre from the identity provider.
4. Flag idle, leaver and duplicate seats (one person holding seats in two organisations of the same tool).
5. Send reminders to idle users and their managers.
6. Reclaim after the grace period and record the saving.
7. Feed the saving into your combined cost view. Our guide on [combining seat licences and token spend](/blog/combine-ai-seat-licence-and-token-costs) shows the formula.

## What mistakes make seat reviews wrong?

- **Checking only one organisation.** Large companies often run several GitHub enterprises or organisations. A user idle in one may be active in another, and a seat in a forgotten organisation will not appear at all.
- **Using login dates instead of AI activity.** Signing in to a workspace is not the same as using the assistant.
- **Ignoring retention windows.** Copilot's 90-day window means you cannot look back further than that through this field. Store monthly snapshots yourself if you want a longer history.
- **Leaving leavers to the vendor.** Seat removal is not always automatic on deprovisioning. Check it, as described in [what happens to AI agents when the owner leaves](/blog/what-happens-to-ai-agents-when-the-owner-leaves).

## How Opencontroller does this

Opencontroller connects to Claude Enterprise and OpenAI Enterprise workspaces and brings their usage into one estate view alongside agents, models and API keys discovered across AWS, Azure and Google Cloud. With OIDC SSO and owners in the governed registry, idle seats and keys can be reviewed against the same identities. See the [cost pillar](/blog/llm-gateway-vs-agent-gateway-vs-control-plane) for how spend and control fit together, or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**How long should a seat be idle before you reclaim it?**
A common pattern is 30 days idle, a reminder, then reclaim after another 30 days. Exclude seats assigned in the last two weeks.

**Why does a GitHub Copilot seat show a null last activity date?**
Either the user has not used Copilot under that organisation since the seat was assigned, or their last activity was more than 90 days ago. Reassigning a seat also resets it to null.

**Is Opencontroller licensed per seat?**
No. Opencontroller is licensed annually per deployment, not per seat and not usage-based. Ask Lyzr for a quote scoped to your estate.

## Key facts

Unused AI seats can be found from vendor activity data: GitHub Copilot's seat-assignment API (/orgs/{org}/copilot/billing/seats) returns last_activity_at per seat, retained for a rolling 90 days since February 2025 (null if older or never used); GitHub's example reminder workflow treats 30 days as inactive. ChatGPT Enterprise workspace analytics exports a Users CSV with is_active and last_day_active, for ranges up to 12 months. Claude Team/Enterprise usage analytics provide a members view and a per-user, per-model spend CSV; the Analytics API key (read:analytics) can be created only by the Primary Owner. Recommended policy: 14-day grace for new seats, flag at 30 days idle, reclaim 30 days after reminder, reclaim leavers immediately. Opencontroller by Lyzr connects Claude Enterprise and OpenAI Enterprise workspaces into one estate view; it is licensed per deployment from $250K per year, not per seat.

## Related

- [What AI spend reports does a CFO actually need?](https://opencontroller.lyzr.com/blog/ai-spend-reporting-for-finance-leaders.md)
- [What happens to AI agents when their owner leaves the company?](https://opencontroller.lyzr.com/blog/what-happens-to-ai-agents-when-the-owner-leaves.md)
- [How do you audit Claude Enterprise usage?](https://opencontroller.lyzr.com/blog/audit-claude-enterprise-usage.md)
- [More on Gateways and cost](https://opencontroller.lyzr.com/blog/cluster/gateways-and-cost)
