Siebel counts authorized access, not logins, and the metric written into your ordering document decides your exposure. This guide separates Application User, Registered User, Named User Plus, and the enterprise Employee metric so you can defend the right number in an audit.
Siebel counts authorized access, not logins, and the metric written into your ordering document decides your exposure. This guide separates Application User, Registered User, Named User Plus, and the enterprise Employee metric so you can defend the right number in an audit.
Every Siebel dispute we have defended in 25 years turns on one question: which metric does your ordering document actually name? Oracle sales, audit (LMS/GLAS), and support all read the same contract differently, and the gap between what you deployed and what you licensed is measured in millions. The four metrics in play (Application User, Registered User, Named User Plus, and the enterprise Employee metric) count fundamentally different populations, and mixing them up is the single most common source of Siebel compliance findings we see.
This page is the metric-selection companion to our Oracle Siebel CRM licensing buyer guide. Read it before you accept a renewal quote, respond to an audit data request, or size a Fusion migration, because the metric you are bound to changes every downstream number.
Application User is the primary Siebel CRM metric, and its definition is the trap. Per current Oracle guidance (Oracle Licensing Experts, June 28, 2025), an Application User is any individual authorized to access the Siebel application, irrespective of frequency or duration of use. The trigger is authorized access, not login history. If 500 people have accounts but only 150 log in regularly, you owe licenses for the population that can access the system, not the population that does.
Two consequences follow, and both cost money. First, the metric is per module. Each person authorized to use a Siebel module counts as one Application User license for that module (Oracle Licensing Experts, July 21, 2025). A user with access to three modules generates three counts, not one. Second, inactive and orphaned accounts still count. Leftover accounts for departed employees are a documented audit gap (Reveal Compliance, May 28, 2025), and Siebel does not enforce license limits by default, so nothing in the software stops the number from drifting upward between renewals.
Siebel bills the account you forgot to disable exactly the same as the account your top salesperson uses forty hours a week.
The list price context matters when you quantify exposure. Oracle's price list shows Siebel CRM Base at approximately $3,750 per Application User (Oracle Licensing Experts, July 21, 2025; corroborated by Software Finder, June 18, 2026), with industry add-ons at roughly $400 per user. Annual Software Update License and Support runs the standard 22% of net license (Oracle Licensing Experts, June 28, 2025). At $3,750 base plus 22% support, 100 stale accounts represent roughly $375,000 in list license plus $82,500 a year in support, before any module stacking. That is why account hygiene is a licensing control, not an IT chore.
Registered User is the named-user metric for external users: partners and customers accessing Siebel through a partner portal or self-service site (Oracle Licensing Experts, July 16, 2025). Only non-employees qualify, and it is typically priced below internal-user metrics because it covers parties who touch a narrow slice of functionality. Counting your external population correctly is its own discipline, covered in counting contractors and external users in a Siebel deployment.
The rule buyers most often break: you cannot repurpose internal licenses for external users. Oracle contracts prohibit using cheaper or spare internal Application User licenses to cover partners or customers (Redress Compliance, July 23, 2025). It works in the reverse direction too. A common violation is letting partners and contractors ride on spare Application User licenses because you have them, rather than licensing them properly as Registered Users (Oracle Licensing Experts, July 21, 2025). The math is unforgiving: if audit finds 200 customer-portal users but you licensed 50 Registered Users, that is a 150-user gap (Redress Compliance, July 23, 2025), and Oracle will price the shortfall at the metric it decides applies, not the one you assumed.
Named User Plus (NUP) is a named-user variant that also counts non-human operated accounts: service accounts, scripts, integration users, and any account that accesses the software (Oracle Licensing Experts, July 16, 2025). If your Siebel contract uses NUP, every integration account and batch identity that touches the database or application server counts. Middleware that multiplexes many end users through one service account does not shrink the count; the population behind the multiplexing point is what Oracle measures.
NUP most often appears where Siebel sits on an Oracle Database licensed under restricted-use terms. If that describes your estate, read the Oracle Database under Siebel: restricted-use license limits before you assume the database is covered.
The Employee metric is the one that produces the largest surprises, because it decouples cost from usage entirely. Per Oracle's License Definitions and Rules booklet (v121525, December 15, 2025), Employee means (i) all your full-time, part-time, and temporary employees, and (ii) all your agents, contractors, and consultants who have access to, use, or are tracked by the programs. The booklet is explicit: the quantity of licenses is determined by the number of Employees, not the actual number of users.
This is the same headcount-versus-usage gap that makes Oracle Java so expensive, quantified in our analysis of why 50 Java developers can mean licensing 10,000 employees. If a Siebel module is sold on the Employee metric, a 4,000-employee company pays for 4,000 regardless of whether 150 or 3,000 people ever open the application. At a hypothetical $250 per employee per year, that is $1,000,000 annually for unlimited usage across the population (Redress Compliance, June 23, 2025).
Under the Employee metric, outsourcing a function does not reduce your count. It adds the outsourcer's people to it.
The outsourcing clause is where the Employee definition bites hardest. If you outsource a business function, you must count all of that provider's full-time, part-time, and temporary employees, agents, contractors, and consultants who (i) provide the outsourcing services and (ii) have access to, use, or are tracked by the programs (Oracle License Definitions and Rules v121525). Buyers routinely assume outsourcing shrinks their license footprint. Under this definition it can expand it, because the outsourcer's staff who touch the tracked programs get pulled into your count.
The metric that governs your obligation is the one named in your ordering document (OD) and incorporated definitions, full stop. The price list tells you what Oracle sells; your OD tells you what you bought. Knowing exactly which metric applies to each Siebel line, as specified in your contract, is the core ITAM control (Oracle Licensing Experts, July 21, 2025). Three structural rules shape how the metrics stack:
Web Channel adds a floor to watch: Siebel CRM Web Channel requires at minimum one Siebel Tools user and 100 users of Siebel CRM Base or equivalent (Oracle Global Price List). Below that floor you are non-compliant regardless of actual usage.
The table below is a decision aid, not a substitute for reading your OD. List prices are Oracle price-list references cited in the research; your negotiated net will differ, and support at 22% compounds every one of these numbers annually.
| Metric | Counts | Population | List reference | Primary risk |
|---|---|---|---|---|
| Application User | Authorized access, per module | Internal employees and contractors with accounts | ~$3,750 per user (Base) | Stale accounts and per-module stacking inflate the count |
| Registered User | Named external users | Partners and customers only | Priced below internal, contract-specific | Portal user growth outrunning licensed count |
| Named User Plus | Human and non-human accounts | Users plus service accounts, scripts, integrations | Contract-specific | Uncounted integration and batch accounts |
| Employee | Total workforce plus outsourcers | Everyone, regardless of Siebel use | ~$250 per employee (illustrative) | Headcount growth and outsourcing expand the count with zero usage link |
Because Siebel does not enforce limits by default, the deployment drifts and the audit reconciles it against your entitlement. The recurring findings we defend are predictable, which means they are preventable:
Take these steps in order. Each one shrinks exposure or strengthens your position:
The leverage in Siebel licensing sits with whoever knows the metric definitions cold. Oracle's negotiators and auditors do. When you match that precision, the ambiguous count that Oracle would have priced at list becomes a defensible number you can hold at renewal.
Yes. The Application User metric is triggered by authorized access, not by frequency or duration of use (Oracle Licensing Experts, June 28, 2025). A person who logs in once a quarter and a person who lives in the system both require a full license. The only way to reduce the count is to remove authorized access, not to reduce usage.
No. Oracle contracts prohibit using internal-user licenses to cover external parties, and external users must be licensed under the Registered User metric (Redress Compliance, July 23, 2025). Doing so is a documented compliance violation. If audit finds external users on internal licenses, Oracle prices the shortfall at the metric it deems correct.
Yes. Inactive accounts count in full because the metric is authorized access, and leftover ex-employee accounts are a top audit finding (Oracle Licensing Experts, July 21, 2025; Reveal Compliance, May 28, 2025). Disable or delete accounts the moment access is no longer needed, and do so before generating any audit snapshot.
It expands your count. Per Oracle's License Definitions and Rules booklet (v121525, December 15, 2025), if you outsource a business function you must count the provider's full-time, part-time, and temporary staff, agents, contractors, and consultants who provide the service and have access to or are tracked by the programs. Outsourcing does not shrink an Employee-metric count; it can grow it.
Named User Plus also counts non-human accounts such as service accounts, scripts, and integration identities (Oracle Licensing Experts, July 16, 2025), whereas Application User counts individuals authorized to access a module. NUP most commonly appears where Siebel runs on a restricted-use Oracle Database. Check which metric your ordering document names, because it changes what you must count.
Your ordering document governs, not the price list. The price list describes what Oracle sells; your ordering document and its incorporated definitions state what you bought and how it is counted (Oracle Licensing Experts, July 21, 2025). Extract the exact metric per line item from your ordering document before responding to any Oracle count.
Oracle licenses cores times a core factor, not raw cores. The 0.5 x86 factor, the worked counting, the virtualization trap, and where the factor does not apply.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
