Hey,
Currently viewpoints are only saved when creating a comment or thread.
can we have the option to save viewpoints to models (or the project, when viewing multiple modes federated).
These viewpoints could of course need the annotations made saved to them if possible 
It would also be cool if these viewpoints can be synched to the native software
Totally agree. All of my colleagues who are using Autodesk Docs are complaining about the same thing … why can’t I store this view or dimensions … it continues with Desktop !Viewers! like BIMcollab Zoom. I’m usually hearing the counterargument PDF. You have my vote!
Hello All,
We agree and the requested features are already on our backlog list 
Thank you for your support,
Agi
Any updates on this suggestion?
For reference, maybe this could be implemented similarly to how Revizto handles custom viewpoints:
Hi Henrik. This is one of the next up items on the roadmap after we’ve wrapped up some other work. I’ll let you know when it arrives! We agree it’s much needed.
What are the feature requirements in your mind? What we’ve discussed internally is to allow saving views, naming them, and potentially structure them into folders. Some tools also allow to create views only visible to you vs. visible to anyone with access to the model – is this important to you? Ideally I’d like to release it without this level of complexity, but it would be good to learn about your use case :).
@benjavo Thanks for getting back to me! Good to hear it’s on the roadmap.
Saving, naming and managing views in folders is definitely the most important feature imo. It would also be nice to be able to create private vs. shared views. If all views are public by default, it will become messy pretty quickly; but if all views are private by default, you obviously can’t share them with the team.
I think this is becoming even more relevant now that we have AI rendering straight from Speckle.
I would also like to be able to set a saved viewpoint as the “Home View” for a project or model. We sometimes have projects where the internal origin (and coordination marker) are quite far from the model itself, so defining a custom starting view would allow for a much better overview over the project.
Thanks for the additional context! And oh yes, your last point also makes sense. We’ve heard this before. I’ve added it to the list. I’m unsure how much of it make it into the very first version but let’s see :).
