Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Options
I am looking for information of how best to set up overall file structures
Marc_J
Member Posts: 2 ✭
As an example, if I have several customers and each customer has several assemblys that are not connected. What is the best way to structure the overall interface.
Could someone please direct me to the relevant information.
Regards
Marc J
Could someone please direct me to the relevant information.
Regards
Marc J
0
Best Answer
-
Options
traveler_hauptman
Member, OS Professional, Mentor, Developers Posts: 419 PRO
Permissions are per-document.
I would create an organization for each customer (drop-down menu on the main page under your username). This will allow you to give permissions to documents quickly to the relevant people.
One document for each final assembly (what you ship to the customer).
Common sub-assemblies that are static (ie those whose changes don't need to propogate to other documents) can go in their own document and be re-used in a limited manner.... part studio tabs can be copied between documents. Assemblies can be exported to disk and imported to the new document (with the companion imported part studio tab losing all feature history).
Subassemblies common to multiple documents where everything is in development and needs change propogation is not yet supported. Eventually inter-document references will be supported for this use case.
One issue to watch out for is that Onshapes management of organizations (what I would call user roles or user groups elsewhere) is a bit wimpy as you can't add an existing organization to a new organization, you have to manually go list the existing organization, get the email addresses, and add them to the new one.
Onshape does not publish a roadmap so while we know that between document re-use will be supported to some degree in the future, we don't know how long we'll have to wait.
5
Answers
Permissions are per-document.
I would create an organization for each customer (drop-down menu on the main page under your username). This will allow you to give permissions to documents quickly to the relevant people.
One document for each final assembly (what you ship to the customer).
Common sub-assemblies that are static (ie those whose changes don't need to propogate to other documents) can go in their own document and be re-used in a limited manner.... part studio tabs can be copied between documents. Assemblies can be exported to disk and imported to the new document (with the companion imported part studio tab losing all feature history).
Subassemblies common to multiple documents where everything is in development and needs change propogation is not yet supported. Eventually inter-document references will be supported for this use case.
One issue to watch out for is that Onshapes management of organizations (what I would call user roles or user groups elsewhere) is a bit wimpy as you can't add an existing organization to a new organization, you have to manually go list the existing organization, get the email addresses, and add them to the new one.
Onshape does not publish a roadmap so while we know that between document re-use will be supported to some degree in the future, we don't know how long we'll have to wait.
Well done
Regards
Marc J