You are viewing limited content. For full access, please sign in.

Question

Question

RIO Licensing - How Named User Licenses Work

Laserfiche Version 10 Licensing
Updated June 7, 2019
asked on June 7, 2019

Let's say we have a pool of 100 named user licenses. Half are assigned to repository accounts having "Full" selected in the Repository Named User drop-down in the account properties. 250 are defined with "False" selected. Is the following true?

All 50 Named users can log in at any time and if they did all at once, up to 50 of any of the 250 other (False) type users could log in as well?

If only 10 Named users are logged in then still only 50 of the 250 other users could log in. So isn't it always better to minimize accounts defined as Named users if possible?

0 0

Answer

SELECTED ANSWER
replied on June 7, 2019

There are two ways to license user accounts in Rio. You can license them at the LF Directory Service level or at the repository level. I highly recommend licensing everyone at the directory service level if everyone has active directory accounts and they are already mapped with windows authentication. This way users can access multiple repositories on the single license and you can take advantage of AD group syncing.

 

As for your licensing questions, named user is an industry wide term where you license specific user or user account as opposed to concurrent users which limits amounts of concurrent logins. Rio is not sold as concurrent users except in the case of the Weblink or Public Portal product which is limited to read only users.

As for why you have some users able to get in unlicensed at both the directory service level or repository level, that is very hard to say without taking a close look. Manage trustees does bypass the license check, but it would not allow that many concurrent users.

2 0

Replies

replied on June 7, 2019

Only those with the "full" designation can log into the repository.    Accounts such as workflow do not need to be a full user to operate bit they have to be enabled to function.

0 0
replied on June 7, 2019

That's not how it works for us. We have users accessing the repositories via client with accounts set to false. As long as they have privileges for a directory and documents they are authenticated and allowed access and can do what they need to.

I'm just trying to verify that licenses not assigned as Named can be used as "concurrent".

0 0
replied on June 7, 2019 • Show version history

The above should not work with named users(all named users are assigned to a specific account or computer). Laserfiche does not utilize concurrent user licenses anymore except for the read only Weblink/Public portal product.

0 0
replied on June 7, 2019

We are running RIO 10.4. If we have paid for 100 licenses shouldn't 100 users be able to connect even if some of them aren't defined as Full Named Users? We have over 300 accounts defined. If a user couldn't log in when their account is set to false I'd be spending my entire day switching account settings between Full and False.

0 0
replied on June 7, 2019

If a user should not be able to log in unless the dropdown is set to Full then what is allowing them to log in when it's set to False? Is there another admin tool or setting that could be overriding the repository account settings?

0 0
SELECTED ANSWER
replied on June 7, 2019

There are two ways to license user accounts in Rio. You can license them at the LF Directory Service level or at the repository level. I highly recommend licensing everyone at the directory service level if everyone has active directory accounts and they are already mapped with windows authentication. This way users can access multiple repositories on the single license and you can take advantage of AD group syncing.

 

As for your licensing questions, named user is an industry wide term where you license specific user or user account as opposed to concurrent users which limits amounts of concurrent logins. Rio is not sold as concurrent users except in the case of the Weblink or Public Portal product which is limited to read only users.

As for why you have some users able to get in unlicensed at both the directory service level or repository level, that is very hard to say without taking a close look. Manage trustees does bypass the license check, but it would not allow that many concurrent users.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...