Syspro user and licence types are described in operational terms in the SYSPRO help system. The help pages explain how an operator code consumes a licence, and which options in the product change that consumption. They are not a substitute for the order form or the EULA, which were not public, and the pages cover different releases. They are nevertheless the most detailed public source on how Syspro counts users, and they matter because the product enforces several limits through its set-up screens.
Operators and the licence file
A SYSPRO user is an operator code. Operator Maintenance records the operator type: a Normal operator can access the desktop, the Web UI and Espresso; a Template operator is a blueprint used to create other operators and cannot be used to log in; Portal operators are named users for the Supply Chain Portal; and AD Managed operators are managed through Microsoft Active Directory.[1] The numbers of users, modules and functional areas are specified in the LICENSE.XML file that accompanies the initial purchase and any upgrade, and a new file is issued when the number of users, modules or functional areas changes or the annual licence is renewed.[2] The file is applied with the License Manager, run from Company Setup before logging in, and the selected licence can be applied to all companies or selected companies.[5]
The reference to an “annual licence” reflects the Annual License Fee model that Syspro’s July 2026 notice says is being discontinued; see Syspro subscription transition and General Terms.[6] How the licence file works under the subscription model is not described in the sources retrieved.
Cloud ERP licence types
For Syspro Cloud ERP the help describes three licence types.[1]
| Licence type | Purpose | Set-up |
|---|---|---|
| Named User | Customer end users | Enable Named user on the operator |
| Service Account | Approved partners, such as ISV partners, that configure and implement the system | Enable Service account; the operator needs a valid Active Directory account with Syspro and a valid email address |
| e.net | Using e.net programs in the e.net Solutions module | Leave both Named user and Service account disabled |
An operator cannot be both a Named user and a Service account.[1] ADMIN operators are automatically named users, and for e.net operators the Named user and Service account options must be disabled so that no licence is consumed.[1] The help describes the named user and service account settings as applicable only to Syspro Cloud ERP licensing.[1] A practical consequence is that a partner consultant who logs in with an ordinary operator code would take a customer’s named licence, and the help directs official ISV partner users to Service accounts.
Core concurrent users
The help on Espresso shows that core SYSPRO licences can be concurrent: it gives the example of a site licensed for 80 concurrent users, described as 80 SYSPRO concurrent user licences.[3] The operator setting “Allow concurrent use of this operator” lets more than one person use the same operator code at the same time, for example several administrators sharing an account or several operators using an account as a guest.[1] Disabling it prevents an operator consuming additional licences when logging in to SYSPRO more than once.[1] The option does not apply to e.net Solutions licensing, which is per operator code, so only one session per operator code can be allocated, and it cannot be enabled with some other options: it cannot be combined with the Report designer or Analytics viewer options, nor enabled for Portal users, nor with multi-factor authentication.[1] It also does not apply to Cloud ERP.[1]
Report designer access is tied to seats: the number of report designers and designer seats determines how many users can use the Report Designer function of Syspro Reporting Services concurrently, so a customer licensed for two designer seats can select the option for only two operators.[1]
e.net Solutions
e.net Solutions exposes business objects, subdivided into functional areas, and the functional areas are what is licensed.[2] Key points:
- Named user. A named e.net user is a SYSPRO operator code. Functional areas are licensed for the number of named users that will use them, and unlike the core product, different functional areas can be licensed for different numbers of users; the help gives 150 users of the Requisition System functional area and 10 of Purchase Order Primary Posting as an example. A named user has one concurrent logon.[2] Each named user consumes one licence, whether or not logged in.[1]
- Guest or anonymous user. The operator code can be used by a concurrent number of users. If the licence allows 10 concurrent users, only 10 can be logged in within a 30 minute period. A user who logs off and on within 30 minutes consumes two licences, so this method can consume more licences than named users, and a guest with a count of three consumes three licences for each functional area it can access.[1][2] Syspro recommends the guest method only where appropriate, and its example is an application offered to 300 customers who order at different frequencies.[2]
- Classes. Classes group users licensed to use Web-based Applications and suit sites where concurrent users are significantly fewer than total users. The entry must adhere to the licence agreement, and increasing the concurrent users may invalidate the e.net licence.[4]
- Prerequisite. A functional area can be licensed only if the matching SYSPRO module is installed.[2]
- Apportionment. The e.net License Apportionment program assigns functional-area licences to operators who need access to the business objects; service operators created by Syspro for its own services are intentionally not included.[7]
Espresso
Espresso licences are allocated to operators as one of three types.[3]
| Type | Meaning |
|---|---|
| Full | An Espresso licence per seat on a named-user basis; 100 users need 100 seats |
| Linked | A SYSPRO concurrent user who also has Espresso; a site with 80 concurrent licences can link up to 80 operators; additional operators need full licences |
| External | A customer with limited access to queries and transaction posting; tied to one customer code |
Linked operators must be active on both Espresso and the desktop at least once within 21 days, with a three-day grace period after the warning.[3] The number of Espresso users is defined in the license.xml file.[3] The help describes linked licensing as significantly cheaper than full seats for every operator.[3]
Portal and Run Time Product licences
Portal users are named users used only for the Syspro Supply Chain Portal, created through Portal User Management and created from a template operator.[1]
Run Time Product licences are issued for independent software vendors (ISVs) whose products call e.net business objects. They let the third-party product connect to e.net Solutions without further e.net licensing implications, but the site must have licensed the underlying module the product reads.[5] From SYSPRO 8 2021 R1 only Managed Run Time licences apply, meaning the product can reach only the functional areas listed in its definition file.[5]
Counting and compliance
Compliance checks follow from these rules.
- List operators by type, and confirm Named user, Service account and e.net settings against the licence file for Cloud ERP.
- Review operators with Allow concurrent use enabled; each additional login can consume a licence.
- For e.net, reconcile named users per functional area and guest logon counts, including repeated logons within 30 minutes.
- For Espresso, match full, linked and external operators to the file, and check linked operators’ 21-day activity.
- Check Run Time Product licences against ISV integrations.
Because the help pages are release-specific and describe product behaviour, they should be read alongside the contract. See Named user licensing, Concurrent and device licensing and Effective licence position.
Out of scope
- Prices and quantities, which sit in the customer’s order form.
- Metrics for products other than those named here; for example the metrics of Syspro’s partners’ App Store applications.
- Other seat types and options referred to in help pages not retrieved for this article.
- The Syspro EULA text, which was not public.