back to top

SalesLogix Licenses – Named user vs.Concurrent, what’s the difference?

Think of a named user license as “owned” by and used exclusively by the SalesLogix user assigned to it.  Even if that user is not logged in at the time, their assigned named license is not available to be used by others users.  The up-side to this type of license is that the named user will always be able to log into the software regardless of how many other users may be logged in since his license is held in reserve just for him. 

 


A concurrent license or group of concurrent licenses is a “pool” of licenses that can be used by an unlimited number of SalesLogix users who are assigned to use the pool.  When a user assigned to the concurrent license pool tries to log in, SalesLogix checks to see if there is a concurrent license available and if so, they successfully log in.  If all of the concurrent licenses in the pool are in use by other logged in users, the user attempting to log in gets an error message stating that there are no concurrent licenses in the pool available at this time and to try again later. 


The up-side to concurrent licenses is that they are shared and therefore less costly to buy licenses for users who work on shifts or are just casual users who don’t need to stay logged in for long periods of time or their need to log in is not time sensitive or urgent.  The down-side is that a user who needs to log in may not be able to in the case where the number of concurrent licenses in the pool is equal to the number of users currently logged in.

 

Another way to think of a named user license is like having a reserved parking space in the parking lot.  The named user always has his designated space available whether his car is currently on the lot or not.  The rest of the parking spots are like a concurrent user license where first come first served and if a shared spot is open when you arrive, you can park there and if no spaces are open, you get to drive around until someone leaves the lot.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Scott Weber
Scott Weber
Scott Weber is CRM Practice Manager and Senior Consultant for Customer FX Corporation.

1 COMMENT

  1. I have a question, we have a valid license for 2 named users and n concurrent users.
    With this blog, I understand clearly the diference between concurrent and named users, but I don’t know how to use my named users.

    What I want to say is, how to create a named user in the “Administrator”?

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos