v9 release and the Non-Compliance Fee

[BkraM]

Re: v9 release and the Non-Compliance Fee

Thanks. Do you have a rough idea of when/if a change will be made so that an API seat or user can be set to not get booted if someone logs in and there aren't any remaining seats? I don't want to upgrade until I am sure Stoneedge will never get booted.

[Rick Wilson]

Re: v9 release and the Non-Compliance Fee

Not until 9.0003 but you'll still need to buy it a seat.

[BkraM]

Re: v9 release and the Non-Compliance Fee

Thanks do you have any idea when 9.0003 will be released? Will it be a seat that you assign for a specific user then have that user be the one used for the API connection?

[Rick Wilson]

Re: v9 release and the Non-Compliance Fee

Goal is around MivaCon in late March.

It'll allow you to purchase a license (for the same price as a seat) that allows a user (in this case StoneEdge) to not count as a seat (in other words always have a seat). This user will only be able to be logged into any 1 session at 1 time, so it can't be shared.

[BkraM]

Re: v9 release and the Non-Compliance Fee

Thanks.

Will there be any kind of hierarchy built into users. For example if we had 1 seat and 3 users. User1 = 1, User2 = 2 and User3 = 3 so user1 can not be booted by 2 or 3 but can boot 2 and 3 and user2 could boot user3.

Or User1 = 1, User2=2 and user3=2 so User1 can boot either and the other 2 cant boot anyone.

[Rick Wilson]

Re: v9 release and the Non-Compliance Fee

Sort of, the way it works is if you're a Non-Admin and you login and have a seat, if you login from another browser or computer, it'll just take over your seat (i.e. kick you out of the other session and open a new session on your new machine).

Or as an Admin, you can kick any session out that choose.

Non admin's can't kick out admins (or other non-admins), only their own sessions.

If you have an API license as mentioned above it'll be outside of this process.