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.
Super light use without account?
I totally understand that Onshape is trying to get more and more people to sign up (and ideally pay), in an almost viral manner, but the current behavior of sharing a public link is frustrating at best. If I send someone a public link and they don't have an account (or can't remember their login), they get this:
There's zero incentive to create an account for a casual share. There's no preview of the document being shared, and no indication of what Onshape even is. If I don't make a big effort in my sharing of the link with screenshots and a description of why the recipient might want to create an account and open the document, this will go into a "maybe get to it later" pile, only to be lost/ignored.
If, instead, there were a super light mode that wouldn't allow much more than spinning the object around without an account, that would be excellent. Ideally this would be something that I could embed in a web page or Slack discussion etc.
There's zero incentive to create an account for a casual share. There's no preview of the document being shared, and no indication of what Onshape even is. If I don't make a big effort in my sharing of the link with screenshots and a description of why the recipient might want to create an account and open the document, this will go into a "maybe get to it later" pile, only to be lost/ignored.
If, instead, there were a super light mode that wouldn't allow much more than spinning the object around without an account, that would be excellent. Ideally this would be something that I could embed in a web page or Slack discussion etc.
6
Comments
But it's true it would be nice to get the same behavior with "public" documents (if you are sending a link to something you are not the author off).
It still seems weird that this landing page is so devoid of any indication of what it is.
Website: ovyl.io
I guess because I'm so conditioned by the Forum use of public documents, I've never really bothered with link sharing.
After playing with it a bit, I get why both things exist, but it is a bit confusing. The fact that a document can have "public" turned off, but is available to anyone with a link through "link sharing" is a little confusing, because at some level that's still "public" in the common definition of the word.
In another way it's kinda like many computer file systems (e.g. Unix, MacOS, Windows) which have User/Group/World permissions (of read/write/execute), and also the orthogonal attribute of being visible or not.
@Evan_Reese
It would be nice to be able to share a link specifically with a single person, or as you say have multiple links you can turn on and off, At that point that's pretty close to doing an "actual share" though, the only gotcha being that the person needs an account, so it's a nice to way for Onshape to try to strongarm people into creating an account but you need a pretty close relation with a vendor to convince them to do that!
Website: ovyl.io
When someone gets a Public link and their browser doesn't have an account cookied (so we assume they haven't created an account), it should really tell them more about what the document is (e.g. a thumbnail image at the very least), and what Onshape is.
Looking at these forums, there's this tag line (absent from the Public document landing page):
"Onshape is the only product development platform that unites CAD, data management, collaboration tools and real-time analytics."
On the front page of Onshape.com there's this:
"Agile Product Design with Cloud-Native CAD & PDM
https://forum.onshape.com/discussion/17826/time-limit-on-shared-link
https://forum.onshape.com/discussion/17460/request-access-option-when-receiving-a-link-to-an-unshared-document
https://forum.onshape.com/discussion/13767/link-expiration
https://forum.onshape.com/discussion/10561/access-limited-link-sharing
https://forum.onshape.com/discussion/10475/shared-files-summary-dashboard
https://forum.onshape.com/discussion/18122/comments-for-design-reviews-by-non-onshape-users
https://forum.onshape.com/discussion/5269/share-a-single-studio-with-teams-clients-etc
https://forum.onshape.com/discussion/9155/follow-me-link-with-no-sign-in
A lot of great work has been done here, but it's clear there are still places where sharing could be more useful.
And, BTW Onshape just posted this video Tech Tip: Adding ‘View Only’ Users to Onshape Professional Data.
I make a documentation privately in Japanese. Using Google Transe, you can see what I say.
https://onshape.jp/doc/%E3%82%88%E3%81%8F%E3%81%82%E3%82%8B%E8%B3%AA%E5%95%8F_faq#q_%E5%85%B1%E6%9C%89%E3%81%A8%E3%81%AF
Twitter: @BryanLAGdesign
Now that I understand Link Sharing better, I might be more inclined to share within my company that way, even with users who have accounts, just to take the friction out of getting them to look at it. I'd love to see some sort of embed version for Slack. There are certainly some users who we currently have as light, just in case they might look at something, but realistically they will most likely not go looking for anything. A link share which was only visible to company users might be interesting.
I find that there are many things (cross sections, simulations, etc) that I want to share, but screen shots end up being the easiest way. Ideally there would be an asynchronous way to send a link to things like that where the end user wouldn't need to understand how to open a saved view with a section, or wait for the simulation to re-run.
I also find that I need to do more checking to see what others will see when I send a URL to them. I have to remember how things will default (hide/show/isolate/make transparent, version vs workspace, releases, configuration variables, etc....). Part of this is a learning process on my part, but it's interesting how often I've been surprised by what others can see vs what I see and think I'm sharing. Even follow me is not the same as a screen share over Zoom. Each way of communicating requires some adjustments to how Onshape works.
We haven't actually done any "normal share" outside the company as requiring an account to view seems like too much of an ask...
I am assuming you are familiar with the link sharing icon? This gets you at least to right place, view, configuration, exploded view, etc directly and is much better than sharing just the general document URL when you want to show something specific (but it still doesn't capture "everything" like cross sections for example...).
We have also create a publication of just "top level" assemblies to share internally so that everyone can have a quick look at the product without having to navigate through a document.
I've noticed the link sharing icon, but what I'm now noticing is that in Safari I get an error when I try to use it:
[edited a lot because I think I finally understand]
Some recommendations:
Today I sent a publication via linksharing to our patent attorney. We did this with ftp server and password protection in earlier days.
Despite I fully trust in our attorney, the e-mail could get hacked from 3rd party. In other words I don't think link sharing is a very secure way of sharing data. And a lot of our partners don't want to sign up for a (free) onshape account. Of course I know the option for sharing export formats like stp or pdf with password protected download link. But that's the old fashioned way. Don't want to go back there.
Therefore I completely agree with the initial request of @S1mon.
A superlight viewer account would be helpful. So our partners can create a password and access shared data in a quick and secure way.
I think it is not far from a free account, but needs a bit more "love" for easy access and user guidance.
On the other hand I see the same request for more protection on link sharing is very old. Most of the IR's are 2years+
@Onshape: When can we expect progress on this? Seems important to me for professional work "the onshape way".
I understand your point and also our partners. It is probably not only because of signing-up but also because of the overwhelming environment they get when they sign in. Not everybody is a CAD user and familiar with Onshape. Many are even overwhelmed by the link access to a publication.
On the other hand registration with an e-mail offers a higher level of security compared to a public link. Even a public link with password protection is not so save because probably most would send the link including password in the same e-mail, which does not help at all.
So maybe as an idea a invitation could look like this:
User XY from company XY would like to transfer CAD Data to you. To ensure secure data transmission, please register with your e-mail address. To navigate the CAD Data please review following quick start guide.
After registration with the same e-mail adress as the invitation this user gets added to my company as "ultralight" user with read and export rights only on shared documents. In my company settings I can search users and kick them out of my company if I want to delete all access to ever given documents.
I could imagine this works well for publications. However I'd prefer to share single parts and drawings without need of publications.
What's your thoughts on this?
If you're trying to sell Onshape, sharing doesn't appear to work.
I'm not sure what happens on the receiving end of a share email to someone, but half the engineers will click to access the project. No one else does. I've had issues with engineers who already have OS accounts and they use that email vs. the one I sent. That doesn't work and they have to create a new account based on the company email I sent them.
Shared link is a scary concept for a project that's getting a patent or you're under an NDA. Even with a password link manager, all someone needs to do is copy the url after viewing the shared document. That would break your password protection scheme if someone knew thats all you need to do. You could then post the URL on a forum and expose the project to the world.
The problem with the cloud is that you don't know who a user is when they arrive to your site. That's why we log in. Once logged in, the browser is authenticated and you're assigned permissions. There has to be a way to authenticate a user when they arrive to your site.
Two factor is a way to solve this.
1. I share to an email address or phone number who doesn't have an account
2. On entry, Onshape sends an email or message to that address with a link allowing them in
3. Onshape now knows who they are
4. After they click the sent link, they're allowed in
I think people get 2-factor stuff and more would click a 2-factor link.
Most people I speak with still talk about files, hard drives & metadata like its 20 years ago and the DOS operating system. They have no idea what the cloud means or how it works. I think with time, it'll get better. For now, this collaborative environment we enjoy, people aren't ready for it.
Yesterday I had lunch with a computer scientist who ran a major computer server farm and I asked what he thought of the cloud and it's future. He replied it was going to be a permissions hell.
This on one hand is true, but realistically quite insular. The prime/bulk of your Onshape users (the people doing the work) are happy and enjoy the tool! (like me)
The giant umbrella of users that we might want to share our Onshape data with include grumpy sour toolmakers that use their own tool, and look at your link with a "what in the fresh hell is this crap?" point of view. In my Solidworks days I had shouting matches with graybeard engineers over Multi-body models (they forbade them, I wanted to use them). I think you might not have a full grasp of the people we might want to try and work with. They Do Not want to use your shiny new thing. They hate new stuff, are tired of learning it, and absolutely aren't making an account on your behalf. In this light, we need a PAINFULLY easy way to securely share, preferably with a splash screen with (I'm not joking) how to pan and view a model or be slightly oriented. I've had conversations with vendors where they tried for 10 seconds and then gave up, or were scared they were messing it up, or were confused on what was being shared with them…. etc. (Part Studio, Document, branch, version there's a lot there if you've never seen any of it before).
I think fundamentally the Onshape share button is super valuable and enables a lot — but it is built for CAD users, and best for people who are familiar with Onshape. The corollary to google docs is relevant here too, everyone knows what they're opening when they click a google doc link. There is no explanation necessary. But sharing CAD data at the document level with someone not familiar with Onshape is just not practical in my experience. We have resorted to exporting PDFs and part solids or assemblies, it is the fastest and least painful way to share with vendors.
Building on the UltraLight user theme above ^^ I am imagining some kind of view that is similar to what you see when you build a release but is like a 'review'? Where the viewport has no context of where this component/assembly/drawing package came from, but you can view it with all the normal tools, add comments, etc. It shows no details on any other tabs, or version history. It kind of sounds like a publication, but those are Tab-centric, and not very useful in my experience. And I'm talking like export level easy. Select objects, right click, 'start review', toggle how many times the link can be opened, and how long it can remain open, and you can send a link to this view to get feedback. If it's not that easy, people won't use it.
This is how I would like to see it work. That's a great system.