[AI translation based on previous email conversation] This situation has come back today again for another project than the previous one. I feel it is going to come back many more times …
Current Issue
Users with “Viewer” access rights cannot export or download models, even when this is operationally necessary.
Use Case
A structural steel subcontractor needs to download the design model (or other production models) to use as a reference in Tekla. Currently, the project administrator faces two unsatisfactory workarounds:
- Grant “Model Edit” rights to users who should only have view access — not ideal, as they are not owners of those models
- Manually export files and distribute them via email or file transfer services
Note: Granting (only) “Data Edit” rights does display an “Export” button, but the action still fails with a permissions error message.
Proposed Solutions
Two alternative approaches:
Option A: Expand existing “Viewer” role
- All users with “Viewer” rights automatically receive download permissions
- For view-only access without download, share via public link instead
Advantages:
- No change to the user interface
- No added complexity
Disadvantages:
- Not intuitive for new or less experienced users
- Users may not realize that “Viewer” automatically includes download rights, or that they need to use a public link to restrict downloads
Option B: Separate permission level (similar to ACC/Forma)
- Introduce distinct roles: “Viewer” and “Viewer + Download”
- Clear, explicit permission settings
Advantages:
- Transparent and unambiguous for all users
- Explicit control at the point of granting access
Disadvantages:
- Additional permission options increase complexity
- Harder to maintain overview of permissions across multiple models/entire project
User Preference
Option B is considered more robust due to its clarity, though both approaches address the core limitation.
