2.3 looks to have the granularity needed. However, any clarification of the levels of access offered, and what each of them permits/restricts, would be helpful.
For instance. If trying to restrict access for a user to only his/her sessions, do they get everything but administer rights, plus restriction to "My session" in both attended and unattended And, if that's correct, can they be invited to join someone else's session?
Can these subsets of permissions to applied to a Group, if using AD?
And, if you've got a team of IT support staff, how do you go about providing that one group full access to all scheduled sessions, with all staff. BUT, keep "unattended" sessions restricted to user who creates it, only?
Can you create unattended sessions so they will only be accessible by one individual, by virtue of the initial setup and configuration of the client?
How does one create an unattended session that is restricted to a person, but then open it up to others if needed? (from looking at this, it seems everything is going to be role-based, so no password restricting of an unattended session, right?)
There are a slew of security scenerio's, I'm sure. But, maybe a video walking through the options as you envision them, or a webinar going over the options, would be helpful?
Looks very promising. Just trying to get my head around the variables and how best to apply them.
Thanks Jake! Great work...
Patrick