Addtional Options Beyond "Restrict Users" (domain based)
eswihart
Posts: 2
I'd like the ability to allow access to projects to everyone within our organization without specifically inviting them to every project. Essentially, the equivalent of the "Anyone in the organization" option within most Microsoft products. The other options would be to allow wildcards (*@domain.com) within the user permissions.
Our use case is that we would like to create links to particular Bluebeam projects within our CRM, which works great, except the person must be invited to the project to gain access.
We've started inviting most everyone to every project, but everything becomes a cluttered mess within studio and the invite emails are a crazy.
1
Categories
- All Categories
- Certifications Overview ↗
- Bluebeam Certified Professional (BCP) ↗
- BCP User Group
- BCI User Group
- Welcome Guide
- Join the Discussion
- 607 Discussion Topics
- 161 Peer Support
- 387 Product Ideas & Feedback
- 51 Community Hub
- 8 What's New?
- Release Notes Website ↗
- Built Blog ↗
- Product Support
- 11 Bluebeam User Groups
- User Groups by Location
- United States
- Canada
- Europe
- Asia Pacific
- User Groups by Interest
- Architecture & Design
- Construction
- Engineering
- Subcontractors & Trades
- User Groups by Specialty Role
- Academic Educators
- Bluebeam Certified Instructors (BCIs)
- Bluebeam Certified Professionals (BCPs)
- Construction Owners & Owner Representatives
- Fresno State Student BUG (Fresno BUG)
- Global Bluebeam User Group Champions
- Government
- Product Ideas & Feedback