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.
What belongs in a Project?
S1mon
Member Posts: 2,910 PRO
I'm just setting up a new Enterprise system as Admin. What belongs in a "Project" in Enterprise, besides documents which are obviously part of a project? Do common parts libraries go in projects? How do other Enterprise admins like to set this up?
So far I've turned off the ability for any users to create documents at the top level to avoid it becoming a mess, and I created a top level "user" folder which is shared with the team so that they can have individual folders for tutorials and other scratchpad stuff.
So far I've turned off the ability for any users to create documents at the top level to avoid it becoming a mess, and I created a top level "user" folder which is shared with the team so that they can have individual folders for tutorials and other scratchpad stuff.
Tagged:
2
Comments
CAD Engineering Manager
The team can also use cad.onshape.com instead of your enterprise domain for things like tutorials that your enterprise really doesn't probably need to own (unless you want to see how much time people are spending on learning things). It can help keep clutter down.
CAD Engineering Manager
I don't see using Projects at all... or if I do, it will be only one Project for every Document created in our Company. In fact I feel creating a Project is added effort if our Company is going to have many Common Libraries (Folders). It would be simpler to just allow everyone to create content in My Onshape (free for all), with Release Management Control, what does it mater if this fills with garbage, you can ignore unreleased content. Also, Onshape is a searchable database unlike file servers making it fairly easy to find something.
I wonder if I am missing out by not using Projects?
-Projects
-Products
-Purchased Components
Many of the items that are originated in Projects eventually become Products
CAD Engineering Manager
If "Purchased Components" were in a Project - we'd use the project to share them out to users that need them - and also to see how much time was spent messing around with Purchased Components - since projects are a nice Unit of analysis in the Analysis tab (in Enterprise).
I've never wanted to manage a library folder so I've never created one. After I build something and use it in a project I just promote it to a library component by clicking on a system variable. My library is all over the place. I don't have to manage anything and they all become available when I'm inserting an assembly and I look for the property "lib" in other documents. I tend to promote library stuff towards the end of a project so document versioning isn't much of an issue. I could move them to their own document, but I usually don't because I don't want to manage that.
It's a lazy person's data management and it seems to be working for me. I'd rather spend time making working assemblies from mcmaster and misumi rather than managing a folder. OS is a database yet we still treat it like it's a hard drive's tree structure. I'm not sure this is a good thing.
At a top level, that's what I'd put in the enterprise project folder. Who wants to look through a million documents to find the top document for all your company's projects? Or, you could just set a property in the "top" document and search on those. I don't run analytics and it's not important to me. I know Adrian does and is really good at organizing this type of stuff. He's been working on it for a while and probably has it figured out.
Those who have set up an enterprise, does your structure look like an inverted tree?
Onshape provides different tools to be flexible and allow you to fit your business needs. Projects are one of those mechanisms, that allow your company to set up role-based access control, so instead of sharing by selecting permissions for the individual or team, the user that is sharing just has to select the role and the permissions are already defined for that role. It is a way for admins to be more prescriptive in how users can share within the enterprise. Using projects can also limit who can share the project, as you must have permissions to that project, and even a global permission to create a project and select the permission scheme associated with it. The video in the training uses one example where you might decide to use a mixed method, to share different types of data in different ways.
You may find using the regular sharing method works better for your enterprise, or you might like the extra control of role-based access and projects. Either way it is so great to see all the different ways you guys are utilizing these tools in this thread!
I also see that Folders within the Project will hinder us in the future as more and more sub-levels of Product are attempted to be grouped but trying to manage common Parts in a Common Part Folder will become make-work. I hope that Onshape Developers work on creating Company Labels... see Company wide labels — Onshape