Differences Between OEM, Single User, and Multi-User Licenses

What are the differences between OEM, single-user, and multi-user licenses? This comprehensive guide explains software license types, usage restrictions, transfer prohibitions, triple fees, compensation, and penalty risks under Turkish Copyright Law (FSEK).

Software licensing is a far more technical and legal field than many companies realize. The fact that software has been “purchased” does not mean it can be freely used on any device, by any user, anywhere, and for any length of time. A lack of awareness, particularly regarding the differences between OEM licenses, single-user licenses, and multi-user licenses, leads to serious license violations in companies, accounting departments, architecture and engineering offices, design teams, and even individual professionals. In Turkish law, computer programs are protected works under the Law No. 5846 on Intellectual and Artistic Works, and according to WIPO Lex records, the current consolidated text of the Law includes amendments No. 7346 dated December 21, 2021.

Therefore, the differences between OEM, single-user, and multi-user licenses are not merely a practical matter concerning the IT department. This distinction represents a risk area that can lead to copyright infringement, breach of contract, presumption of unfair use, triple damages, compensation, injunctions, and in some cases, criminal investigations. The General Directorate of Copyrights of the Ministry of Culture and Tourism also explicitly states that both civil and criminal proceedings can be initiated in cases of copyright infringement.

Compliance is impossible without understanding software licensing types

Software licenses essentially define the limits of usage rights. One type of license is device-based, another is user-based, and yet another is structured for multiple users or centralized management. Therefore, the same software can be offered with different licensing models, and each model may have different legal consequences. For example, Adobe's corporate licensing documents clearly state that the "named user licensing" model is tied to individual users and that licenses are managed centrally. Autodesk also states that in subscriptions requiring login, each seat will be assigned to a single authorized user and cannot be shared.

These limits are also of particular importance under Turkish law. According to Article 52 of the Copyright Law, contracts and transactions relating to financial rights must be in writing, and the rights in question must be clearly indicated. In other words, the statement "I purchased the program" alone is not sufficient; it is crucial to specify which right is granted, for whom, within what scope, and for how long. If the company or user exceeds the technical and contractual limits of the license, this exceeding can lead to consequences ranging from breach of contract to copyright infringement.

What is an OEM license?

In its simplest terms, an OEM license is a license model that comes bundled with a specific device and is legally bound to that device. Microsoft's official OEM Windows terms of use state that the software is licensed to run on a "licensed device," and that under this license, one instance of the software can be installed and run on the licensed device, and that it can be used by only one person at a time. In the same Microsoft documents, the concept of "device" is defined as a hardware system, indicating that the OEM product is tied to the device on which it was first installed. Microsoft's official OEM licensing rules also clearly state in their summary that the OEM product is "married" to the original computer on which it was installed, and that existing OEM licenses cannot be transferred from one machine to another.

This type of license is most commonly encountered in operating systems and some pre-installed office products. Users often consider OEM licenses as "cheap and standard licenses." However, the legal principle of the OEM model is that the software is licensed in conjunction with specific hardware. Therefore, transferring OEM-licensed software to another computer, uninstalling it from an old device and installing it on a new one, or viewing a device change as a normal license transfer is often contrary to the license terms. The fact that activation may be temporarily possible does not create legal authorization; Microsoft's official statements specifically emphasize that license rights arise from the license terms, not from the activation itself.

The significance of this in Turkish law is as follows: an OEM license is a device-based license. If the user exceeds this limit and transfers the OEM software to another device, the legal basis for the licensing relationship becomes questionable. While this alone does not automatically result in penalties in every case, if it creates a usage area without the rights holder's permission, it can raise contractual liability and copyright claims.

What is a single-user license?

A single-user license is a licensing model where software is allocated to a specific individual user. The most common example of this in the modern subscription ecosystem is "named user licensing." Adobe's current enterprise licensing page clearly states that named user licenses tie Adobe application and service usage to an individual user, that this model is designed for networked scenarios, and that compliance tracking can be managed more centrally through users rather than machines. Autodesk's official support also states that in subscriptions requiring sign-in, each seat will be assigned to a single Authorized User and seats cannot be shared. Furthermore, Autodesk's AutoCAD subscription FAQ page explicitly states that a single-user subscription is a structure that only one user can access, activate, and use, and that users cannot share the same seat.

Here, “single user” and “single device” are not the same thing. A single-user license from some providers may allow the same person to log in on multiple devices, but this does not mean the license can be shared within a team. The legal center is the person, not the device. Therefore, sharing a single-user license within the office using a “shared account” logic, giving a user’s login information to teammates, or allowing a departing employee’s account to continue being used in the office, is often against the license terms. The fact that the Microsoft Service Agreement states that account information cannot be transferred to another user or entity supports this same logic.

In Turkish law, the critical point regarding single-user licenses is that the right to use is restricted to a personal level. If a company uses a single-user license as if it were a team license, the defense of "we purchased the program" becomes weaker. This is because the issue is not the existence of the software, but who uses it and to what extent. Copyright protection under the Turkish Intellectual Property Rights Law (FSEK) can directly come into play here; especially if economic rights are used more extensively than permitted, the rights holder can assert a claim of unlicensed use, along with contractual and copyright aspects.

What is a multi-user license?

A multi-user license is a model designed for multiple users or multiple license seats. However, the biggest misconception here is that "multiple users = unlimited use." In reality, multi-user licenses are also subject to numerical and organizational limitations. Adobe's Acrobat for Teams pricing page clearly shows that licenses are offered on a "per license" basis, the number of licenses is selected in team plans, and licenses can be reassigned via the web-based Admin Console. This demonstrates that the multi-user model means managing multiple licenses, but is still limited by the number of seats. Autodesk's licensing options page also defines the distinction between "single-user, multi-user, and network," showing that multi-user licenses are a separate category.

The multi-user model appears in various forms in different products, such as team licenses, network licenses, shared device licenses, or enterprise plans. However, the common point is that even with multiple users, this authorization is not unlimited. The number of licenses, simultaneous use, device type, organizational structure, remote access conditions, and sometimes physical location limits are all determined by contract. Autodesk's audit page lists "overuse of subscription seats" and "overuse of perpetual seats" as separate types of non-compliance, indicating that even with multi-user licenses, excess usage is considered a clear violation.

This type of license is particularly beneficial for companies because it provides ease of centralized management, user assignment, access restriction, and reporting. However, it also creates greater corporate risks if misused. This is because multi-user licenses often give companies a false sense of security. If the number of licenses, user scope, and affiliated company limits are ignored with the thought, "We already have a team license," then unauthorized use of extra seats or unauthorized organizational sharing can occur much more easily. In Turkish law, this can result in the software being used economically for a wider period than permitted.

What are the key differences between OEM, single-user, and multi-user licenses?

The first major difference separating these three licensing models is what the license is tied to. OEM licensing is primarily device-bound. Single-user licensing is individual-bound. Multi-user licensing is tied to a specific number of users, seats, or organizational authority. In the OEM model, the central licensing element is the hardware; in the single-user model, it's the user account and identity; and in the multi-user model, it's the license pool or team management. Microsoft's OEM terms tie the software to the licensed device, while Adobe's named user model emphasizes the individual user, and Adobe Teams and Autodesk's multi-user approach emphasizes license seats and centralized assignment.

The second major difference lies in the transferability and sharing regime. OEM licenses, in general, cannot be considered separately from the device and cannot be freely transferred to another machine. Account sharing is generally prohibited in single-user licenses; the license is granted to one person. In multi-user licenses, authorization can be given to as many users as the number of licenses, but this still does not mean "unlimited internal free use." Choosing the wrong license type or misusing the correct license type is the stage that most often creates problems in practice.

The third difference is how compliance is monitored. In OEM licensing, auditing is often done via the device and product key. In single-user licensing, user ID, session, and assignment become important. In multi-user licensing, the license pool, number of seats, central admin panel, and access distribution are decisive. Therefore, the forms of violation also change: in OEM, migration and incorrect device usage are more common; in single-user, account sharing; and in multi-user, exceeding seats and spreading outside the organization are more frequent.

What are the legal consequences of using the wrong type of license?

In Turkish law, computer programs are protected as works of art, so exceeding the limits permitted by the license is not merely a commercial mismatch. According to Article 68 of the Law on Intellectual and Artistic Works (FSEK), in case of processing, reproduction, distribution, performance, or public transmission without written permission in accordance with the law, the rights holder may demand up to three times the price they would have requested if a contract had been made, or the current market price. Therefore, transferring an OEM license to another device, using a single-user license as a team, or operating a multi-user license beyond the number of seats purchased may result in significant financial claims depending on the specific circumstances.

Under Articles 66 and 69 of the Copyright Law, lawsuits for the cessation and prevention of infringement may also arise. In other words, the rights holder may not only seek monetary compensation; they may also demand the cessation of use, the removal of installations, and a prevention of the infringement from recurring. This creates significant operational pressure, especially in companies where workflows are software-dependent. For example, if accounting software is used with the wrong license, if an ERP solution exceeds its license limit, or if a CAD program is shared within the office with a single-user license, the legal process could lead to the software being effectively disabled.

Monetary compensation and profit sharing are also open to discussion. The Ministry's statement indicates that in cases of copyright infringement, both material and moral damages, as well as the profits obtained from the infringement, can be claimed. The claim that "you used the software without paying and obtained economic benefit from this use" is particularly strong if the projects are commercially run without a license or with an incorrect license, services provided to clients, or critical processes within the company.

Is there a risk of punishment?

Yes, it's possible. According to the official statement of the General Directorate of Copyright, processing, reproduction, distribution, public dissemination, publication, and possession or storage of illegally reproduced works for commercial purposes without written permission are among the situations in which criminal proceedings can be initiated. Unauthorized transfer of OEM to another machine may not seem equally serious in every case; however, cracking, counterfeit activation, license breaching, systematic commercial use with shared accounts, or the use of invalid software can significantly increase the severity of the penalties. Autodesk's definition of "nonvalid software" as software that has been modified or cracked by an unauthorized party also confirms this distinction in practice.

Therefore, misuse of single-user and multi-user licenses, even if it seems technically simple, can in some cases lead to criminal charges. Especially if tools that bypass license verification are used, the issue goes beyond simple license non-compliance. For companies, this risk makes the "we'll fix it later" approach extremely dangerous.

What is the biggest practical risk for companies?

The greatest practical risk is not only choosing the wrong license type, but also misusing the correct license. Many companies assume OEM licenses are portable like regular retail licenses. They see single-user licenses as "sharable within the office" and multi-user licenses as unlimited organizational licenses. However, current official manufacturer documents clearly show that each model has its own limitations. In Turkish law, exceeding the license limits also creates serious problems under the burden of documentation and proof. Under Article 76 of the Law on Intellectual and Artistic Works, the court may request the necessary permissions and authorization documents or a list of the works used from the user; failure to provide these constitutes a presumption of unlawful use.

Therefore, companies should view software compliance not just as a purchase, but as a continuously monitored legal process. Device-based inventory, user assignments, license agreements, reseller registrations, subscription renewals, and employee exit processes must be managed together. Otherwise, the most costly mistake is often not failing to purchase the software, but using the wrong license type for years without realizing it.

Conclusion

The differences between OEM, single-user, and multi-user licenses are extremely important from a legal perspective. OEM licenses are device-based and generally tied to the hardware on which they were initially installed. Single-user licenses are tied to an individual user, and sharing is often prohibited. Multi-user licenses allow for multiple users or seats, but this does not mean unlimited and unrestricted use. Each model has different limits, and exceeding these limits can lead to consequences under Turkish law ranging from breach of contract and copyright infringement to triple damages and, in some cases, criminal penalties.

In short, the correct question is not "which license is cheaper?" but "which license suits our actual usage pattern?" If a company does not choose the license that suits its real needs, or uses the chosen license in violation of its terms, the short-term savings idea can turn into much more expensive legal consequences in the long run. Software license compliance is no longer a matter of technical convenience; it is a direct issue of business security and legal risk management.

Frequently Asked Questions

Can I transfer an OEM license to another computer?
As a general rule, an OEM license is tied to the device it was originally installed on and cannot be freely transferred to another machine. Microsoft's official OEM policies also state that the OEM product is tied to the original PC.

Can two people in the same office use a single-user license?
For many manufacturers, the answer is no. Adobe's named user model links the license to an individual user; Autodesk also explicitly states that it does not allow seat sharing in single-user subscriptions requiring sign-in.

Does a multi-user license provide unlimited use?
No. Multi-user licenses are also limited by the number of seats or users. Adobe Teams plans offer licenses on a "per license" basis; Autodesk also defines overuse of subscription seats as a separate category of incompatibility.

If the wrong license type is used, will only the missing license fee be paid?
No. Depending on the specific case, there may be a risk of triple the fee, compensation, suspension of use, and in some cases, penalties.

Does the lack of copyright protection provide a defense?
Generally, no. According to ministry statements, copyright arises the moment the work is created; registration is not a mandatory rights-establishing condition.