Streamline your workflows and master BIM coordination! Program starts April 28!

Teamwork & BIMcloud
About Teamwork, BIMcloud, BIMcloud Basic, BIMcloud Software as a Service, network settings, etc.

Cannot copy-paste Hotlink Modules in Teamwork files "because your Role does not allow it"

tkrepler_fjc
Booster

Sometimes, some of my colleagues receive this message when copy-pasting entire Hotlinks (within the same Teamwork project).

Screenshot 2025-04-02 at 2.06.15 PM.png

They might have all access rights in the world assigned to them, yet it still comes up.

Obviously, there are workarounds, and we have applied these, but it is still annoying.

We have been battling this problem for a long time (I think ever since we started using BIMcloud (Pro) on premises 8 years ago or more), and reported it to Graphisoft, but they could not find the cause of the problem, as it is extremely random.

I am wondering if any of you have experienced this issue or still do.

Thanks.

Tony Krepler
Design Technology Lead - BIM, fjcstudio
Sydney, Australia
Archicad since 3.4, macOS 14
5 REPLIES 5
Matteods
Enthusiast

Hi,

 

are hotlinks mod files or pln?

Hi Matteods, they are MOD files — usually published from the same Teamwork file.

Cheers,

Tony Krepler
Design Technology Lead - BIM, fjcstudio
Sydney, Australia
Archicad since 3.4, macOS 14

Hi,

So it's already the lightest file. Do you have all the same role in teamwork? Better to check if the right to use and modify hotlink is checked in teamwork role. Here an example 

https://help.graphisoft.com/BC/22/INT/_BIMcloud_/30_BIMcloudManager/30_BIMcloudManager-58.htm#XREF_1...

 

tkrepler_fjc
Booster

Yeah, I know this, it doesn't work even if everything is checked.

Tony Krepler
Design Technology Lead - BIM, fjcstudio
Sydney, Australia
Archicad since 3.4, macOS 14

Oh I understand. In this case maybe is better to try to lunch a new empty file in teamwork and then try to work with hotlinks and check if the problem persist or not. So you can check if the problem is due to the file. If it's working well on a new, one option it can be that the person who has this problem has to leave the project and then rejoin it. But this will cause the lost of data and cache for that person so it's not the best 🙂