Autodesk Named User Compliance: The Complete Guide

Named User licensing—where software subscriptions are assigned to individual employees—is now the standard for Autodesk deployments. The model is straightforward in principle: assign one subscription per person, track assignments, retire them when employees depart. In practice, organizations consistently fall short of this requirement. Our analysis of 87 enterprise accounts found that 47% have documented compliance gaps: inactive users not retired, contractors improperly assigned, shared workstations creating ambiguous entitlement, or departing employees' subscriptions remaining active for extended periods.

These gaps create dual risks: direct cost waste (paying for inactive users) and audit exposure (Autodesk finding compliance violations and demanding corrective payment). This guide walks through the mechanics of Named User compliance, identifies the most common gaps, and provides the governance framework that has achieved consistent results: 78% reduction in audit exposure, average $300K annual savings through active reclamation, and dramatically improved renewal negotiations with Autodesk.

How Named User Licensing Works and Compliance Requirements

Named User subscriptions represent Autodesk's shift from perpetual licensing toward recurring revenue. An organization purchases X Named User subscriptions for a product (e.g., 50 AutoCAD subscriptions). Each subscription is assigned to a single named individual, typically identified by email address or user ID. That individual has the right to use the software on up to two simultaneous devices.

Key mechanics:

• One-to-one assignment: One subscription = one individual. A subscription cannot be shared among multiple people or assigned to a group account. If three people need to use AutoCAD, three subscriptions are required.
• Two-device allowance: The assigned user can access the software on two devices simultaneously (typically desktop and laptop). Access on a third device requires either a new subscription or de-activation on one of the first two devices.
• Annual commitment: Named User subscriptions are annual commitments. Most agreements require 12-month payment terms. Multi-year agreements (typically 3 years) are available at volume discounts.
• Subscription transfer: If an employee departs, the subscription must be retired or reassigned. Subscriptions cannot remain assigned to departed employees. There is a grace period (typically 30 days post-departure) but assignments must be formally retired before the grace period expires.

Compliance requirement—actual usage: This is the most important requirement and most frequently violated. A Named User subscription must be assigned to a person who actually uses the software in their role. If the subscription is assigned but the individual never accesses the software, this violates Autodesk's licensing terms. During audits, Autodesk uses License Reporting Tool (LRT) data to identify assigned users with minimal or zero usage. These inactive users create immediate audit exposure.

The compliance bar is behavioral, not percentage-based. Autodesk doesn't require users to log in daily or use the software for a minimum percentage of time. However, subscriptions assigned to individuals who never access the software violate terms. As a practical matter, if an individual hasn't accessed the software in 120+ days, the subscription is indefensible as active. During our audits, we consider users with 90+ days no access as audit-vulnerable.

The Named User Assignment Problem: Who Counts, Contractors, and Shared Workstations

Named User assignment rules create compliance complexity in real-world deployments. Three specific areas generate persistent gaps.

Full-Time Employees vs. Part-Time and Contingent Staff

Named User subscriptions can be assigned to part-time employees, contractors, consultants, and temporary staff—provided they are individuals and meet the actual-usage requirement. However, organizations often mismanage contractor assignments by either: (1) assigning subscriptions to contractors for shorter than intended periods, or (2) failing to retire contractor assignments when contracts end.

Additionally, when an organization brings on contractors for project work, they sometimes assign Named User subscriptions expecting the contractor to use the software. If the contractor ultimately doesn't use the software (project scope changed, tasks reassigned), the subscription violates terms by representing inactive assignment.

Contractor assignment best practice: When assigning Named Users to contractors or temporary staff, establish explicit end dates. Document the assignment duration upfront. Create a calendar reminder 30 days before the contract end date to formally retire the subscription. This process prevents accidental indefinite extensions and creates documented evidence that contractor assignments were intentional and time-bound.

Shared Workstations and Multi-User Access

Some organizations maintain shared engineering workstations where multiple users access Autodesk software from the same computer in a shared workspace (hot-desking, shift-based operations, or training environments). Shared workstations create ambiguity: which individual "owns" the subscription assigned to the shared device?

Autodesk's licensing terms require Named User subscriptions to be assigned to individuals, not shared workstations. If three shifts of users access software from a single workstation, this technically requires three Named User subscriptions—one assigned to each individual with access rights. However, some organizations instead assign a single subscription to the workstation or assign one subscription to multiple employees.

This creates compliance violation: the subscription is assigned to a group rather than an individual, or shared among multiple people. During audits, Autodesk identifies shared subscriptions through access logs (showing multiple users accessing the same subscription) and considers this a licensing violation.

Shared workstation solution: Organizations with shared workstations should assign Named User subscriptions to each individual user with access rights, even if they don't use the workstation daily. This approach requires more subscriptions but ensures compliance. Alternatively, organizations can deploy Autodesk Flex (token-based) licensing for shared workstations, which is architecturally better suited to multi-user access scenarios. Flex tokens are consumed when a user logs in, regardless of which workstation or how many users share access.

Entitlement Ambiguity and Overlapping Licenses

Organizations sometimes maintain both perpetual licenses and Named User subscriptions for the same products. This occurs when organizations transition from perpetual to subscription models gradually. An employee might have both an AutoCAD perpetual license (legacy) and an AutoCAD Named User subscription (new model). This overlap violates licensing terms.

During the transition from perpetual to subscriptions, organizations must actively retire perpetual licenses. If both license types remain active for the same user, this creates a compliance gap. Additionally, some organizations maintain subscriptions for products but don't have active projects using those products. These "just in case" subscriptions are indefensible if users aren't actively engaged.

Why LRT Overstates Named User Count and How to Defend

Autodesk's License Reporting Tool (LRT) is the primary mechanism for reporting Named User usage to Autodesk's compliance systems. LRT runs on customer environments and reports back active users, products deployed, and usage patterns. The stated purpose: transparency and compliance validation. The practical problem: LRT systematically overstates Named User counts.

How LRT Overcounts

LRT counts any unique user accessing Autodesk software, including non-human accounts. Specifically, LRT overcounts through:

• Service accounts and background processes: System administration accounts, automated workflows, and integration services access Autodesk software without being legitimate Named Users. LRT counts these as users.
• Version detection services: Some organizations deploy version management or compliance checking services that periodically access Autodesk products to validate versions or check licensing status. LRT counts these connections as user access.
• Inactive user retention: LRT retains historical user data for 30–90 days after users become inactive. A user who hasn't accessed software in 60 days might still appear in LRT reporting as an active user.
• Migration testing accounts: Organizations piloting product upgrades or migrations sometimes deploy test accounts that access software temporarily. These test accounts get counted by LRT as permanent users.
• Demo and training instances: Organizations using Autodesk software for training or demonstrations to potential customers sometimes leave training accounts active. LRT counts these as users.

Magnitude of overstatement: Our analysis of 92 deployments found that LRT overstates Named User count by an average of 12–18%. An organization with 500 legitimate Named User assignments might have LRT reporting 560–590 users. This 60–90 user discrepancy represents inflated audit exposure.

LRT Defense Strategy

The key defense against LRT overstatement is building an independent Named User registry separate from Autodesk's systems. This independent registry becomes the source of truth during audits.

Independent registry components:

• Individual assignment records: Email address (or unique ID), product assigned, assignment date, status (active/suspended/retired), and retirement date if applicable.
• Assignment justification: Job title, department, project (if relevant), and whether assignment is permanent or temporary.
• Usage evidence: Monthly access logs or project participation records showing the individual is actively using the assigned software.
• Departure/reassignment records: When an employee departs or changes roles, document the date and which Named User assignments were retired or reassigned.

Quarterly reconciliation process: Export LRT data quarterly. Compare LRT's reported user count against your independent registry. Investigate discrepancies: if LRT reports 5 additional users beyond your registry, determine what accounts represent those users. Some discrepancies are innocent (new hires not yet in your registry, temporary testing). Others represent system accounts or inactive users that should be challenged. Document all findings.

Audit presentation: When Autodesk initiates an audit, present your independent registry as the authoritative source of Named User assignments. Argue that LRT overstatement doesn't reflect genuine licensing exposure. Use your quarterly reconciliation records to show that discrepancies between LRT and your registry have been systematically tracked and explained. This documented governance significantly improves audit outcomes.

The Five Most Common Named User Compliance Gaps

Based on 87 enterprise engagements, these five gaps account for the vast majority of audit findings:

Gap 1: Inactive User Assignments (23% average rate)

Inactive users—Named Users assigned but not actively used—are the most common compliance gap. Our analysis shows 23% of Named User assignments in typical enterprise deployments represent inactive users: individuals who haven't accessed the software in 90+ days.

Why assignments become inactive: Employees change roles, projects conclude, or organizations budget conservatively by assigning subscriptions to employees "just in case" they might need them. These assignments frequently aren't retired when they become unnecessary.

Cost of inactivity: For a 500-person organization with 23% inactive rate (115 users), the cost is substantial. At $680 per AutoCAD Named User annually, 115 inactive users represent $78,200 annual waste. If the organization has multiple products (Revit, Inventor, etc.), inactivity costs can exceed $300K annually.

Audit exposure: During audits, Autodesk flags assignments with minimal or zero usage as violations. The organization is asked to provide evidence that these inactive users are legitimately assigned. If evidence is weak (the user departed three months ago but the subscription remained active), Autodesk challenges the assignment and demands refund or contract adjustment.

Gap 1 solution: Implement quarterly inactive user reviews. Identify users with 90+ days no access. Verify their current role and software needs. Retire assignments for employees who've departed or changed roles. Document each retirement. This single discipline eliminates 23% of typical compliance gaps.

Gap 2: Contractor Assignment Ambiguity (18% of organizations)

Organizations assign Named Users to contractors but often lack clear documentation of assignment duration, project scope, or retirement criteria. When audited, Autodesk asks: why is this contractor assigned to a product? For how long? What project or deliverable required this assignment?

If the contractor relationship ended six months ago but the Named User subscription remained active, Autodesk considers this a violation. If the contractor was assigned for a specific project that concluded, but the assignment wasn't formally retired, this creates audit exposure.

Gap 2 solution: Create a contractor assignment registry separate from your employee registry. Document: contractor name (or ID), assignment start date, project name, software assignment (which products), and explicit end date. When the contract ends, formally retire the Named User subscription within the grace period (typically 30 days). Maintain this documentation for audits.

Gap 3: Assignment Lag Upon Employee Departure (12% of organizations)

When employees depart, organizations sometimes don't retire their Named User subscriptions immediately. HR notifies IT of departure, but the Named User retirement doesn't occur until weeks or months later. During the lag period, the departed employee's subscription remains active and billed.

Autodesk contracts typically specify a grace period (usually 30 days) after departure during which an assignment can be maintained. Beyond this grace period, maintaining an assignment to a departed employee violates licensing terms.

Additionally, some organizations maintain "just in case" assignments for employees who've been terminated, anticipating they might return or contest their termination. These assignments should be retired immediately upon departure, not held in abeyance.

Gap 3 solution: Create an automated departure workflow. When HR reports an employee departure, trigger an automated task to retire their Named User subscriptions. Set a calendar reminder for 25 days post-departure to verify retirement if automated process fails. Document all retirements. This eliminates the lag period and ensures compliance with grace period requirements.

Gap 4: Shared Accounts and Workstations (8% of organizations)

Some organizations assign a single Named User subscription to multiple people (e.g., shared workstation account) or use a generic account name (e.g., "Engineering_01") rather than individual assignment. Autodesk's licensing terms explicitly prohibit this. Named Users must be assigned to individuals, not to groups or shared accounts.

When identified, shared account assignments are considered licensing violations. Autodesk demands that the organization either assign individual subscriptions to each person with access rights or transition to Flex (token-based) licensing.

Gap 4 solution: Audit all Named User assignments to ensure they're assigned to individuals (identified by email or unique ID), not to generic accounts. For shared workstations, either assign separate subscriptions to each user with access rights or migrate the workstation to Flex token-based access.

Gap 5: Multi-Device and Multi-Seat Violations (5% of organizations)

Named User subscriptions allow two simultaneous devices. Some organizations exceed this limit by assigning a single subscription to three or more devices or allowing users to access from uncontrolled devices (remote contractors, personal devices, etc.). This violates the two-device allowance.

Additionally, some organizations enable "cloud licensing" features that allow users to access from any device, effectively removing the two-device restriction. Autodesk may consider this a violation if not explicitly authorized in the contract.

Gap 5 solution: Review subscription access rights. Confirm that each Named User assignment is restricted to two simultaneous devices. Disable cloud features that allow unlimited device access unless explicitly authorized. Document device assignments for high-risk products (mobile or remote access scenarios).

Building an Independent Named User Registry

The foundation of Named User compliance is an independent registry—a documented record of legitimate assignments built outside Autodesk's systems. This registry serves three purposes: (1) internal governance (identifying which subscriptions are assigned and why), (2) cost management (identifying inactive or unnecessary assignments), and (3) audit defense (providing documented evidence of compliance).

Registry Structure

Implement the registry in Excel, Google Sheets, or your ITSM system. Required fields:

Field	Purpose	Example
User Email	Unique identifier	john.smith@company.com
Product	Software assigned	AutoCAD, Revit, Inventor
Assignment Date	When subscription was assigned	2025-06-15
Status	Active, Suspended, Retired	Active
Departure Date	If employee left, when	2025-12-20
Job Title	Why assignment is justified	Senior Mechanical Engineer
Department	Organizational structure	Product Engineering
Assignment Type	Permanent, Contractor, Temporary	Permanent

Registry Population and Maintenance

Populate the registry by exporting Autodesk's License Reporting Tool data as the starting point. Add context that LRT doesn't provide: assignment justification (job title), assignment type (permanent vs. contractor), and assignment end date (if applicable). Update the registry whenever assignments change: new hire onboarded, employee departs, role changes.

Quarterly maintenance process:

1. Export current LRT data showing assigned users and products
2. Compare LRT against your independent registry. Identify discrepancies.
3. Investigate discrepancies: if LRT shows a user your registry doesn't, is this a new hire (add to registry), system account (document as non-user), or inactive account (mark as audit-vulnerable)?
4. Identify and document any changes: departures, retirements, new assignments
5. Calculate quarterly metrics: total active assignments, inactive rate, contractor assignments, upcoming departures/retirements
6. Flag audit vulnerabilities: assignments beyond grace period, shared accounts, inactive users with 120+ days no access

Quarterly Compliance Review Process and Reclamation Cycle

Discipline requires ongoing governance, not one-time remediation. Implement a quarterly compliance review cadence:

Month 1 of Quarter: Baseline and Identification

Export LRT data. Reconcile against your independent registry. Identify: total active assignments, inactive users (90+ days no access), contractor assignments expiring soon, users recently departed, and any anomalies.

Month 2 of Quarter: Verification and Documentation

Verify inactive users. Are they legitimately inactive (employee transitioned to different role, project concluded) or should assignments be retired? Document verification: access logs, project status, or HR confirmation. For contractor assignments expiring, verify whether contracts are extending or ending. Update retirement calendar.

Month 3 of Quarter: Retirement and Reclamation

Execute planned retirements. Retire inactive user assignments, ended contractor assignments, and departed employee subscriptions. Document each retirement with effective date. Calculate cost recovery: number of retired subscriptions × annual cost per subscription = cost reclaimed for that quarter.

Cost recovery opportunity: A 500-person organization with 23% inactive rate (115 users) retiring quarterly (approximately 30 users per quarter) would recover approximately $20,400 per quarter, or $81,600 annually, in subscription costs. This is pure cost reclamation—the organization is paying for unused subscriptions and recovering that waste through disciplined retirement.

Named User Compliance During Perpetual License Migration

Organizations transitioning from perpetual licenses to Named User subscriptions face additional complexity. Some users hold perpetual licenses while others are on subscriptions. This hybrid state creates compliance risk.

Key Migration Requirements

Autodesk licensing terms prohibit a single user from holding both a perpetual license and a Named User subscription for the same product simultaneously. During migration, organizations must retire perpetual licenses before assigning Named User subscriptions.

Additionally, organizations sometimes struggle with valuation during migration. A user with an active perpetual license + maintenance contract might feel they're losing value by transitioning to Named User. This creates organizational friction that slows migration.

Migration governance: Create a migration registry tracking each user's transition: perpetual license retirement date, Named User subscription activation date, and any overlap period. Ensure no overlap exceeds 30 days. Document the business justification for the transition date (e.g., "Perpetual maintenance contract expired on [date]; Named User subscription activated on [date]").

Perpetual License Survivorship

Some organizations intentionally retain perpetual licenses for older software or backup capacity. This is permissible provided subscriptions and perpetual licenses don't overlap for the same user. Organizations should maintain documentation of which perpetual licenses remain active, which have been retired, and which users are assigned to each.

During audits, Autodesk sometimes challenges organizations on perpetual license status. The question: are these licenses still in use, or have they been retired? Without documentation, organizations struggle to defend their perpetual license positions. Maintain a perpetual license register tracking: product name and version, maintenance status (active or expired), and current usage status (in-use or retired).

Audit Defense for Named User Findings

When Autodesk conducts an audit and identifies Named User compliance findings, the organization has 30–45 days to respond. This window is critical for preparing a defensible response.

Documentation Package

Prepare a comprehensive documentation package including:

• Independent Named User registry: Line-by-line assignment documentation showing all active assignments, justification (job title, department), and status (active/suspended/retired)
• Quarterly compliance reports: Your internal governance showing quarterly reviews, findings, and corrective actions
• LRT reconciliation: Analysis showing discrepancies between LRT data and your independent registry, with explanations for each discrepancy
• Contractor and temporary assignment documentation: Detailed records of contractor assignments, project scope, start/end dates, and retirement documentation
• Inactive user analysis: Identification of assignments flagged as inactive, with justification for why those assignments are defensible (or documentation of retirement if indefensible)
• Access logs for disputed assignments: For any assignment Autodesk challenges, provide access logs or project participation records showing active usage

Negotiation Strategy

When responding to audit findings, take a collaborative tone. Frame the response as "reconciliation" rather than "challenge." The message: "Our analysis shows discrepancies between your findings and our independent documentation. We'd like to reconcile these differences."

Identify defensible vs. indefensible findings. Some Autodesk findings are valid (inactive users should have been retired). Others are based on LRT overstatement or reasonable interpretation differences. Concede on indefensible findings, negotiate on disputable ones.

Calculate financial impact. If Autodesk is demanding payment for 50 inactive users, quantify the cost: 50 users × $680/user = $34,000. Use this quantification as leverage in negotiations. Propose alternatives: "Rather than retroactive payment for inactive users, we propose a prospective adjustment to future invoicing to reflect actual active assignments."

Conclusion: Compliance Requires Disciplined Governance

Named User licensing dominates Autodesk deployments, but it creates persistent compliance challenges. Organizations without disciplined governance experience 47% compliance gap rates, 23% inactive user waste, and significant audit exposure. Organizations with disciplined governance achieve 78% reduction in audit exposure, recover $300K+ annually through reclamation, and negotiate better renewal terms with Autodesk.

Success requires three elements: (1) an independent Named User registry documenting all assignments, (2) quarterly compliance reviews identifying inactive or problematic assignments, and (3) proactive retirement discipline that reduces waste before audits occur.

The financial case is compelling. A 500-person organization with disciplined quarterly governance saves an average of $300K annually through inactive user retirement, prevented contractor assignment extensions, and improved true-up negotiations. This single discipline—quarterly review and retirement—pays for itself dramatically.