What it models
The schema models the following tables:The SaaS Subscription is visible to the help desk agent without a requester link, so that questions like “do we have Figma?” can be answered. All other tables are scoped to the requester.
Use cases
- License compliance. Compare what you’re entitled to against what’s consumed. A Reconciliation Result records the variance and its verdict, so over- and under-licensing are queryable.
- SaaS and seat tracking. A subscription’s purchased quantity, assigned seats, and active seats sit side by side. The difference between assigned and active is the number of units available for reclamation.
- Renewals. Renewal dates on subscriptions and contracts drive T-90 / T-60 / T-30 reminder sweeps, so you’re aware of all auto-renews.
Usage tips
Populate and extend
- Populate it from your SaaS-management and IdP sources with ingestion, or import a license schedule by CSV.
- Extend it with your own fields, tables, and relationships, and add validation rules. For example, require a contract on any subscription over a spend threshold.
Reclamation lives in access management
Serval reclaims unused licenses two ways, both outside the database:- Policy-based reclamation. The deterministic, rule-driven path. Define a policy, and Serval flags every seat that crosses it for a reclaim decision. For more information, see Reclamations.
- Proactive reclamation agent. The flexible, AI-driven path. An installable agent that reads your team’s connected apps, gathers context and data for each user and seat, and reasons which licenses are good reclamation candidates. The agent doesn’t deprovision on its own. Instead, it presents its findings for your review, and you make the final decision for each item.