An AutoCAD license for shift work is counted by person

One shared Autodesk account on the computer beside a machine tool does not turn one subscription into a license for two operators. Under the current Single User model, the right is assigned to a specific person, so two shifts staffed by two employees usually require two assignments, even if they never open AutoCAD at the same time.

A workstation and a user answer different questions. The workstation tells you where the software is installed. The license determines who may launch it. When procurement mixes up these units, the savings last only until the first review or until the second operator cannot sign in properly.

This article covers a typical production case: a shared computer, several shifts, employees, and commercial use. A specific contract, an old perpetual entitlement, or special terms may change the answer, so check the documents tied to your serial number and Subscription ID before buying. "We used to do it this way" is not a contract.

The named user model counts people, not computers

An AutoCAD license for shift work under the Single User model is counted by the number of specific employees who need access, not by the number of computers or simultaneous launches. The current "Offerings" section of the Autodesk Terms of Use says that every Authorized User needs a unique Autodesk ID and that no one else may use that identifier to access the product.

The conclusion for a shop floor is simple. If Ivan uses a terminal from 8:00 a.m. to 8:00 p.m. and Aigul uses the same terminal from 8:00 p.m. to 8:00 a.m., they are two named users. Their shifts not overlapping does not make them one person. Each needs an individual account, and the administrator must give each person a separate subscription seat or another suitable type of access.

The phrase "one workstation" often misleads the finance team. It really is one system unit in the asset register. Autodesk Account uses another unit of assignment: an individual with a unique email address and Autodesk ID. There is one installation, but two access rights.

A shared account such as [email protected] does not solve the issue. It makes no difference if the shift supervisor controls the password and the employees never sign in at the same time, because the login does not identify one Authorized User. Autodesk's support article "Log in to several devices at once with the same user ID" explicitly says that an ID must belong to an individual, not a group or a generic login.

Do not confuse this rule with permission to install subscription software on several devices. Autodesk says a named user may install the product on the number of devices allowed by the offering terms, while using the desktop version on only one desktop device at a time. This lets one engineer use a fixed workstation and a company laptop at different times, for example. It does not let two engineers take turns signing in under that engineer's name.

There is another detail about concurrent use. In Autodesk's current terms, background activities such as batch processing or a render running without user input do not count toward the concurrent access limit for one Authorized User. That is an uncommon exception on an ordinary shift, and it does not reduce the number of assignments. You cannot leave a background task running for the day operator and then let the night operator use interactive AutoCAD under the same ID: the second person is still using someone else's entitlement.

Count a person as a user if access is part of their normal duties and the software must be ready for them without an administrative reassignment. Do not try to measure the entitlement by minutes of mouse movement. Such data can show utilization, but the Single User terms rely on the assigned Authorized User. That is why two employees working separate twelve-hour shifts require two assignments, while one mobile engineer with several personal work devices remains one user if the concurrent use limit is observed.

A shift schedule does not create a floating license

Separating people by time reduces the concurrent load, but it does not change the entitlement purchased. Single User remains an assignment to a person even if the computer sits idle for half the day. A floating principle applies only when the agreement expressly permits a Multi User or network model, or when Flex is used under its own consumption rules.

I keep finding the same faulty setup. AutoCAD on the first shift's computer is activated with the supervisor's account. At the end of the shift, the supervisor closes the drawing but does not sign out of every Autodesk component. The second shift's operator continues in the same session or learns the password. The access history shows the supervisor's name, local settings and cloud data get mixed together, and the actual user does not match the assignee.

This setup has several immediate consequences. The company cannot reliably show who used the software. When the shared account's owner leaves, the password must be changed urgently. Personal settings, history, and access to cloud services pass between employees. Most important, a license breach does not disappear because the time sheet proves the two people did not work at once.

Some administrators try to reassign one seat in Autodesk Account at 7:55 p.m. and move it back in the morning. The terms allow an administrator to reassign Single User access from one person to another through Autodesk's process. But that mechanism is intended for a genuine change of recipient, such as a departure, transfer, or long replacement, not as a shift scheduler. Daily rotation disguises the continuing need of two employees as one seat and creates a poor record for a review.

If the second operator only reads printed work orders and never starts AutoCAD, that person needs no assignment. If the operator opens a DWG in AutoCAD, makes even one change, prints from the software, or checks geometry with product tools, that person is using the offering. A job title of "operator" rather than "designer" changes nothing. Count actual access.

A remote session does not turn the user into a device either. If an employee connects to the shop computer with a remote access tool and starts AutoCAD, that employee needs the entitlement. Check the virtualization and remote access terms for your edition and plan separately: the right to start the product and the right to host it in a particular infrastructure do not always match.

Network licensing and Single User solve different problems

A true network license limits the number of concurrent sessions, while Single User limits the group of assigned people. These are not two names for the same purchase. Under the former Multi User model, a license server issued an available seat to any permitted user on the company network until the purchased concurrent limit was reached.

That model feels natural for a shop with nonoverlapping shifts: two people could use one floating seat at different times. Autodesk, however, ended new sales and renewals of standard commercial subscriptions with multi-user access. The company's transition page for Named User states that those subscriptions were retired and that existing customers were offered a transition. As a result, "let's buy a network license" now usually describes a desired mechanism, not a standard item available for purchase.

Do not assume an old entitlement is active because a license file or Network License Manager still exists. First locate the agreement, proof of entitlement, maintenance term, renewal history, and terms for that specific version. A perpetual license for an old release, a current special agreement, and an expired subscription lead to different conclusions. A server that still runs does not prove the right to use the product.

For Multi User, the current terms cap concurrent Authorized Users at the purchased capacity and describe access through a protected LAN or VPN. They also define whom the organization may admit. If the company retains such an entitlement, calculate the actual peak of concurrent work, add a justified margin, and check the contract limits. You cannot apply that formula to a Single User subscription by choice.

The difference is easy to see with six designers. Under Single User, all six need personal access even if only three work at once. With a valid network model, the requirement might equal peak concurrent sessions plus a margin if the terms of that specific entitlement permit it. With Flex, all six remain named users with separate IDs, but usage draws tokens from a shared pool for each day an eligible product is used.

Two shifts need an access matrix, not a computer count

A sound calculation starts with a list of people and the nature of their work. Add computers second to plan installation and performance. That order quickly reveals relief workers, supervisors, process engineers, and external specialists who tend to be missing from the budget.

Consider a shop with ten shared workstations. One operator uses each station during the day and another at night. Eight operators on each shift open AutoCAD every day, two night employees only receive PDFs, and one process engineer edits DWG files on any available station during weekends. The Single User basis is not ten computers or twenty rows in the shift roster. It is seventeen actual AutoCAD users: eight day operators, eight night operators, and the process engineer.

Use one row per person in a table so the calculation can be repeated and defended:

The formula for a named subscription is short:

Потребность Single User = число уникальных людей, которым назначен доступ

The number of shifts, terminals, and working hours does not enter the formula. Those data help make sure no one was missed and allow you to compare a standing subscription with Flex for occasional use.

The calculation for a valid Multi User entitlement is different:

Потребность Multi User = максимальное число одновременных сеансов + согласованный резерв

Use that line only after confirming the right to a network model. Flex has no universal seat formula: estimate the number of days each person will actually start the product, the current AutoCAD token rate in your region, and the validity period of the token pack. Rates and availability change, so take them from the commercial quote, not an old presentation.

Count relief workers according to the actual scenario. If four relief operators can replace any employee and start AutoCAD when doing so, each needs a lawful route to access. Regular, recurring replacements usually call for separate Single User seats. Flex may make more sense for rare callouts, but compare annual consumption, not the cost of one day.

Flex helps with occasional access but still uses names

Autodesk Flex suits people who open AutoCAD occasionally and is a poor automatic answer to round-the-clock work on two shifts. According to the official Flex FAQ and Flex overview, a company prepurchases tokens, assigns real users, and permits selected products for them. Starting a product consumes its daily rate from the shared balance.

The important distinction is that a shared token pool is not a shared account. Every employee receives an individual Autodesk ID. Payment is pooled, but identity remains personal. This preserves normal administration and avoids passing a password between shifts.

Include Flex in the calculation for a process engineer, auditor, relief specialist, or manager who needs AutoCAD a few days a month. A standing subscription is often clearer and more predictable for an operator who opens the software every shift. No honest threshold can be given without the current subscription price, regional token rate, and work calendar.

Compare the choices over one period, usually the term of your procurement. For each occasional user, multiply the expected number of paid launch days by the current daily token rate, then add a sensible margin for unscheduled visits. Compare that total with a named subscription and account for token expiration. Do not mix "scheduled days" with "launch days": an employee may report for a shift but work only with a PDF.

Flex is not a network license in the former sense. It does not hand one concurrent seat to the first person who asks. Autodesk explicitly describes both Single User subscriptions and Flex as forms of named user access. They differ in payment and product assignment, not in permission to work anonymously at a shared terminal.

Check the operational side as well. The team needs an adequate balance, users must be assigned, and the required product must be permitted. The night shift should not discover that tokens have run out or that someone forgot to add an employee during an urgent edit. Assign an owner to the process and set an internal balance alert threshold, even if procurement happens once a year.

A shared computer needs separate profiles and sign-ins

Bad configuration can undermine correctly purchased seats on a shared computer. Every operator needs a separate operating system profile and an individual Autodesk ID. At the end of a shift, the user closes files, lets any cloud components in use finish syncing, signs out of Autodesk, and ends the operating system session.

Do not store an Autodesk password in a shared profile's browser or pin it to the instructions beside the monitor. Do not use the shop's mailbox as the user's identity. A corporate email address with an employee's name works if it belongs to that specific person and the company manages its lifecycle.

Separate three layers on the workstation that often end up in one folder:

• shared production DWG files and templates protected by company access rights;
• the personal operating system profile with its cache, interface settings, and credentials;
• license assignment records and employment records maintained by the administrator outside the working directory.

This separation does not replace a license, but it does demonstrate deliberate access management. It also lowers the chance that a night operator sends a file from the day colleague's cloud space or changes that colleague's print profile.

A named subscription periodically needs an internet connection to verify the entitlement. Autodesk's "How to work offline in AutoCAD products" states that the user must connect at least once every 30 days, and the product warns them before the deadline. Plan for that requirement in the network rules for an isolated shop segment. Opening all outbound traffic without review is unwise, but blocking verification completely and hoping for permanent offline use will fail too.

If the workstation supports critical production, test the user change before going live. One operator ends the session, the second signs in under a personal profile, starts AutoCAD, opens a test copy of a DWG, prints it, and closes the software. Confirm that the license resolves to the second ID, template paths work, and the other person's recent files and credentials are not visible.

Reassignment is for staff changes, not every shift

An administrator may reassign Single User access to another person through Autodesk's process, but should do so when the population of users changes. Normal reasons are clear: an employee leaves, transfers to a role that does not use AutoCAD, takes an extended absence with another specialist replacing them, or finishes a project.

The seat transfer should leave a connected record. The supervisor's removal request, the last working date, removal of the assignment in Autodesk Account, and the new assignment to another unique ID should agree in time. If single sign-on is connected to the employee directory, do not rely solely on automatic account deletion: check separately that the product seat became available.

Daily reassignment looks different. The same two names alternately receive one seat hundreds of times according to a fixed schedule, although both remain continuing users. That is not a staffing event. It is an attempt to turn named user access into a concurrent license through administrative actions.

A short business trip or sick leave calls for a practical answer based on the facts. If the substitute will actually start AutoCAD, that person needs personal, permitted access for the work period. You can assign a free seat if the former user truly does not use the product and the reassignment follows the rules, provide another personal seat already purchased, or use Flex. You cannot simply share someone else's password.

Assign an owner to the process. The shop supervisor reports who needs access and when. Human resources confirms hiring, transfers, and departures. The Autodesk administrator assigns the product and retains the export. Procurement tracks the seat count, terms, and commercial records. A generic login almost always appears when all four roles silently assume that someone else completed the task.

A review must connect the contract, the person, and the launch

A licensing review should not stop at a screenshot of the "About" window. It must connect the commercial entitlement, the Autodesk Account assignment, the personnel list, and the actual way people work on devices. Each source on its own can create false reassurance.

Once a quarter and before renewal, assemble one review package:

1. Export the users assigned AutoCAD or Flex with their corporate email addresses.
2. Compare the export with employees and contractors, including night, relief, and weekend shifts.
3. Reconcile active seats, Subscription IDs, dates, and invoices with Autodesk Account and supplier records.
4. Check shared computers for separate operating system profiles, the absence of a generic Autodesk ID, and proper sign-out between shifts.
5. Record exceptions, the person responsible for correction, and the due date, then verify that each issue was closed.

This is the article's second practical tool, and it is enough. Do not create ten logs that no one reads. One user table and one quarterly package establish a clear chain: the organization bought an entitlement, assigned it to a specific person, and configured that person's work environment for the licensing method.

Keep the applicable terms with the proof of purchase. Autodesk has changed its access models, plan names, and sales process. The procurement folder should contain the contract or order, the relevant version of the terms, the offering description, invoices, renewal information, and correspondence about special rights. The old word "network" in an installer name cannot replace those documents.

Check actual exceptions. A contractor who comes once a month, a temporary employee hired for three weeks, and a service engineer may be absent from the staff export but still start the software. Review terms for contractors and territorial use separately. Do not extend an internal access right to outsiders out of habit.

If you find a shared ID, stop its use first and give people proper access. Then change the password, end active sessions, inspect connected cloud data, and document the correction. Do not rewrite logs after the event or try to describe the shared account as a technical user.

Procurement must follow the working pattern

For two permanent operators sharing one station across two shifts, the starting answer is simple: two unique Autodesk IDs and two Single User seats. If one employee never starts AutoCAD, leave that person out. If the second uses the product rarely, compare a separate subscription with Flex. Apply the network formula only to a confirmed, valid Multi User entitlement, not to a wish to pay for the concurrent peak.

Give the supplier an access matrix before requesting a price, not the phrase "AutoCAD for ten computers." State how many unique people work regularly, how many use it occasionally, how shifts are arranged, and whether there are isolated network segments, contractors, or old agreements. The quote can then be tested against the actual work pattern.

GSE.kz sells and integrates Autodesk software, so for this kind of procurement we ask customers to describe users and shifts before selecting the license mix. It is a dull part of the project, but it prevents anyone from confusing an installation on a shared computer with two people's right to run the software.

In the order, state the offering name, access type, number of seats or Flex volume, term, territory, product contents, and administrator details separately. Ask the supplier to confirm in writing how the proposed setup covers the day, night, and relief shifts. A verbal statement that "you can use it on one computer" is too vague: it may refer to installation rather than users.

Do not buy an unexplained surplus, but do not calculate only for a perfect roster. Vacations, sickness, training, commissioning, and emergency callouts change the group of people. Justify the margin with specific situations: a spare named seat for an approved replacement, Flex for rare visits, or a procurement process that can add a seat quickly.

Before production use, assign the users, test every employee's sign-in, and save the initial export. Give the shift supervisor a short rule: everyone uses a personal profile, no one uses another person's password, and replacements are reported before AutoCAD starts. If the night operator cannot sign in, treat it as an access incident, not a reason to borrow the day operator's account.

Shift work itself is not difficult to license. The difficulty begins when a company counts hardware under an agreement that counts people. Name everyone who actually presses "Start," and most disputed cases will be settled before the invoice arrives.