nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bluebeam Community

Build connections with Bluebeamers around the world, discover what’s new, and make your voice heard.

Studio Session Security

Josh Anhalt

I'm looking for some input on how everyone else is setting up their Studio Sessions. We have predominately unchecked the Private Session checkbox to allow people in our company to join as they were added to the project. We've realized that this opens us up to anyone being able to join if they just guess the correct 9 digit session ID. We're now looking at checking the Private Session checkbox back on, but our main frustration point is we either need to invite every person in our company to allow anyone to get in if they get added to the project, or they have to request the invite then are dependent on a team member being available to get them added. It looks like the person that creates the session does not get any external notification of a join request until they themselves get into the session, which seems like a problem.

New wishlist: The ability to add a password to a session so we can store the password on our server and allow our team to join sessions when they need.

Find more posts tagged with

Studio Sessions

Comments

Dhanush Kodi Raj

Hi Josh Anhalt

I've run into this exact wall. Unchecking Private Session to make life easier for the team really is just leaving the door open, anyone who lands on the right 9-digit ID gets in, nothing else is protecting it. With Private Session back on, the only way in is being added as an Allowed Attendee, individually or through a Studio Group, there's no password option, and no alert that reaches you outside of Revu when someone's waiting to join. So, what you're seeing isn't a setting you've missed, it's just how it's built right now.

One thing that's helped me, build a Studio Group with your whole company in it, then add that Group, not individual names, to Allowed Attendees when you host a Private Session. Still a manual step per session, but it turns "invite 40 people" into one click, and anyone in the group can get in without you touching access each time. The password idea would solve this properly, centrally stored, no ID guessing, no bottleneck on a specific person being online. Worth posting it to the Product Ideas & Feedback category on this Community so it can pick up votes from others hitting the same thing.

Good luck getting Private back on without it slowing the team down.

Thank You for sharing this

Darbie Roach

@Josh Anhalt and @Dhanush Kodi Raj

It would also be incredibly helpful set the sessions to private but allow everyone with the same email domain in with the session ID. We are also having to move to private sessions for all projects, but with 150+ projects running at once, our QC team have had their workflow slowed down a lot by needed to get invited to 5-15 sessions a day.

Welcome!

It looks like you're new here. Sign in or register to get started.