Restricted Access - Modelling standards

LFBIMMAN — Sat, 25 Oct 2025 15:50:30 GMT

Hi All,

It's Friday, and I find myself yet again fixing models for careless Archicad users. I like to try and correct mistakes with the user & choose education over restriction. However, some people cannot be taught & will choose the quick way 9 out of 10 times. These people then usually complain that their models are running slowly.... it's an annoying cycle.

My question is... Is there any way to restrict access to the embedded library? The only way I can think of is to reserve the embedded library, but I don't want to have to do this individually for each project; I would rather manage it through BIMcloud if possible.

If anyone has any neat ways of ensuring that models stay clean & accessible by removing access or controls to particular sections of Archicad, please share them.

For example, I like the fact that you can ensure that project elements have been released on teamwork projects by toggling an option in the data integrity settings in work environments.

Again, not trying to be malicious or make it difficult for people; I just want to ensure fundamentals are being adhered to.

Operating system used: Windows

Re: Restricted Access - Modelling standards

martin-b — Sat, 25 Oct 2025 11:09:25 GMT

In the BimCloud, you can change the permissions for each role. Or create new roles for users. There are 3 permissions that handle Libraries:

Libraries - Add/Remove: Enables user to add BIMcloud Libraries to the project using the Library Manager. (Does not enable user to manage server libraries - that requires permissions on the BIMcloud Manager.)

Library Part - Create

Library Part - Delete/Modify

https://help.graphisoft.com/bc/INT/Topics/BCManager_Roles_Topics/c_RolesPage.html

And just a little heads up, the "release all" option does not really do what it says. See here: https://community.graphisoft.com/t5/Teamwork-BIMcloud/Release-all-when-closing-Teamwork-File/td-p/605064

There is also a problem with reserved Elements that are not granted before one user leaves. Say that the first user sends a request. He didn't get it granted, but needs to go home for the day. He sends his changes, releases all and closes everyting. Then, a second user finally sees the request from the first user, grants it without thinking and now the first user who is already offline has a bunch of stuff reserved and no one can use it until they kick the first user from the project or until he goes back online...

topic Restricted Access - Modelling standards in Modeling

Restricted Access - Modelling standards

Re: Restricted Access - Modelling standards