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.
Make Public
rod_muirhead943
Member Posts: 95 EDU
Our school district is not using or paying for enterprise. I have 6 classes with 24 students in each class. Why am I having to spend an exorbitant amount of time tracking and making documents Public? I don't have that kind of 365 24 7 time. What can I do to set up PUBLIC staying on all the time for students?
Thanks
Thanks
0
Comments
http://somup.com/crewIEbpal
The documents/folder need to have been shared with the Link Document permission so that the student can link the parts in a different document's assembly. Please check that the correct student was given Link Document permission in the share menu.
http://somup.com/crewIEbpal
What would an e-book do that Onshape help does not? I find their Help menu to be excellent. The opening page of Help is full of links for beginner through expert; it is a wonder of using the technology for training and reference. For example the 'Index' has 'Sharing and Collaboration' which is comprehensive and covers 'Link document'. And the forum is a unique resource putting us in touch with each other and Onshape developers.
Thanks!
Curious - your last comment on topic was ' it appears Domenico may have given the possible solution. "Link document" ' Sounds like you found success, then both Neil & I responded to your other points and did not see anything from you.
So when you ask 'What am I missing?' we do not understand how to help. If you keep a dialog going I think you will find help saving those 'hours'.
Mr. Cooke,
The students from day one have only used their school email address to use OS.
"What am I missing?" => What is the set up protocol that I missed in setting up OS? Not to upset either of you or sound rude or obnoxious, I don't have 365-24-7 to make files public so work can continue. If the world / globe icon is not showing to the students, they can not continue working.http://somup.com/crfI2DFcMr
Based on the video it seems the documents are owned by your user account which is why students would either need to be shared into the doc or the doc be made public.
Instead, the students should create/own the documents.
Onshape, Inc.
Creating and Using Folders (onshape.com)
I think your question about 'where is the index' is based on my comment April 9. I was talking about Help (Help menu under ? and then Help). See pic below and note the section on Folder Creation and Sharing.
Please accept my sincere apology if in anyway I have offended yourself or the OS team. Trying to learn OS. I appreciate your patience very much. Again, my apologies!
From your comment over in this thread, I'm assuming you still haven't figured out a way to easily set up the permissions you want. Let me see if I can help with that somewhat. Some of what I have to say is based on guesswork, since you haven't really explained your use cases very well. If I do miss something, feel free to let me know, and I can see what I can do.
Starting off, I'm assuming you've already organized your classes into Onshape teams. If you haven't done this, then you can find instructions for doing so in this blog post. Having your students organized into teams will make sharing documents much easier.
In a learning environment, there's a few different types of things I'd assume you'd wish to be able to do. The first is sharing documents containing one or more parts you'd like the students to be able to use, like if you wanted your students to practice making an assembly from a collection of provided parts. In this case, these parts would ideally be contained inside a single document, and you can enable the students to use said parts in an assembly in their own documents by sharing the document with the respective class team with the Link document permission enabled.
When documents are shared this way, students would not need to copy or move said documents, but would instead be able to use parts from it by choosing Other documents and navigating to the reference parts document shared with the team for the respective assignment. (They can also paste the browser link to the shared document into the Other documents search bar to more easily find it).
Students can also derive parts from the reference document into part studios, if it is desirable for students to be able to build off of reference parts directly - however, they won't have access to the feature tree of imported parts, so it'll be difficult to do things other than booleaning additional geometry onto said parts.
The second, more common use case for you is when you assign students to work on an individual project, then have them submit the project to you for grading after they've finished. As others have stated above, the easiest thing to do in this situation is to have the students create their own documents, then share them with you when they are finished. You can also share documents containing reference parts with the students, which will allow them to use said parts in their individual documents as they desire.
Since you no longer own the documents containing your student's work in this case, the onus for ensuring you have access to their work falls onto individual students, saving you from having to do the work of manually sharing documents with individual students. To prevent academic dishonesty, you can always review the edit history of documents as you please.
Lastly, if any student cannot edit any document, double check that their education license has not expired (it expires automatically every year). If it has, simply have said student fill out the education sign up form here, using the email address associated with their Onshape account.
I hope some of this helps, and saves you from having to spend "365 24 7 time" sharing documents with your students. If you have a use case I didn't cover, feel free to describe it, and myself and others can probably explain how you can more quickly accomplish your goals. Good luck, and I hope this helps!
I will step through this process. Thanks
I noticed you posted a comment on my profile asking for a bit more explanation, which I'm more than happy to provide. I did decide to post it in this thread, however, since I want my reply to be more visible (in case others in the community have similar questions), and because the editor for comments on a profile is worse than the editor for commenting on a post.
(For others, @rod_muirhead943's specific question can be found here, but it basically asks about sharing actual documents.)
Something I didn't get into to much in my original post was that there's actually multiple ways to share parts, sub assemblies, and documents with students. Addressing your question directly, you can share documents by selecting each one individually (you can't share more than one document at a time), then pressing the Share button on the upper right hand corner of the screen:
This will bring up the share menu. From there, you have two (primary) options:
1. Share your document with individual teams (classes) you'd like to have access to your documents. The key permission here is Link document, which is what will allow your students to insert the part into their assembly; you'll also want to set it to Can view, so that you don't have to deal with students accidentally modifying the master part.
You can also allow copying, but that probably isn't necessary unless you want students to be able to copy the document in order to make direct edits to the feature tree of individual parts (for less involved modifications, students can also derive shared parts into a part studio in their assignment, make changes (like coloring parts or whatnot), then use their derived version - no copying required!).
One downside of this approach is that it requires you to share each document manually with each class, which can be quite tedious, especially if you rotate class teams every school year/semester. This will also generate one email to every student per shared document; this is less of a concern, but it could get pretty annoying for students, especially over time.
The benefit of doing this is that it allows you to share the document with students via the link, and won't spam them with emails; however, you'll probably need to communicate the link to each document manually, outside of Onshape; otherwise, it may be a bit hard for students to find the appropriate document for each assignment.
A document which is public looks like the following:
If you want to play around with what is possible with a public document, you can try playing around with a copy of my VEXU team's VEX CAD library here:
Inside any assembly in any document you own (i.e. any document besides the one linked above):
Note that this method for using parts from a shared document with "Link document" permission is the same for any document, so your students can use the same procedure above to use parts from any document you share with them which has the "Link document" permission enabled (and/or is public).
I would also encourage you to take note of the numerous parts included inside the part library I shared above. Note that it includes parts and/or sub-assemblies of almost every vex component - by combining multiple parts and assemblies into a single document, my team made it extremely easy for us to get parts and assemblies as we wanted. Since everything is in one place, it's also very easy for us to share our library with others, as it's only one document.
This alludes to a good practice nobody's really touched on yet; combining multiple parts into a single document makes it a thousand times easier to share stuff. When applied to you, I would strongly recommend combing all of the parts for any given assignment into a single document for that assignment; this is equivalent to creating a folder containing all of the parts needed for said assignment, rather than making individual folders for each part in an assignment, which is obviously slower and more work for all involved.
Obviously, one important question which needs answering is how this can be accomplished. There's two ways to do so.
1. Use the derive tool to bring parts spread across multiple documents into a single document.
2. Import all of your parts into a single part studio in the first place (rather than importing them into multiple documents, one per document, which occurs by default). For more details on this method, see "To import data into an existing document, import from within an open document" here. Note that you've been importing data into brand new documents, rather into an existing document; you want to import into an existing document in most cases, as this will allow you to easily collect parts into a single location (for example, this is what we used when creating our VEX part library).
So, in conclusion, you can share your documents one by one with your teams, or make them public (as you've been doing), or you can combine your parts into fewer documents in order to more easily make multiple parts available to students without having to share a bunch of documents manually. For you, I would recommend creating documents with imported parts, one for each project or assignment; Create a document, then derive or import all of the parts needed for a particular assignment into a single part studio in said document. You can then make that document public and send the link to your students, or share the document with the appropriate class when it's time for them to work on the assignment.
I know this post has become quite long - If you want, I can make a better step by step guide for deriving/importing parts into a single document, or explain individual parts in more detail if they're unclear. Please let me know if you need any help. I hope some of this helps, and good luck!