topic How do I send a Fusion file to someone for feedback? in Fusion Design, Validate & Document Forum

How do I send a Fusion file to someone for feedback?

j9lemmon — Thu, 07 Mar 2024 15:23:19 GMT

I want to make a Fusion file available to someone in a different location who has Fusion.

Ideally, I'd like him to be able to make changes that I could see.

Since all my files are in the Cloud, I imagine there must be a way to do this.

Thanks for any advice.

Re: How do I send a Fusion file to someone for feedback?

g-andresen — Thu, 07 Mar 2024 15:32:58 GMT

Hi,

have a look Here

günther

Re: How do I send a Fusion file to someone for feedback?

j9lemmon — Thu, 07 Mar 2024 18:08:45 GMT

Thanks @g-andresen

This looks interesting. I have 2 questions:

1. I have a single-user Fusion license and so does the person I want to collaborate with. Will I have the ability to do the steps in your answer?

2. I see that these instructions are labelled Legacy. Since I'm new to this and will be creating new projects, perhaps I should just go ahead and learn the new way to do this; the instructions suggest: "If you have any legacy projects, consider upgrading them to Folder-Level projects."

Thanks for any clarification.

Re: How do I send a Fusion file to someone for feedback?

TrippyLighting — Thu, 07 Mar 2024 19:22:48 GMT

@j9lemmon wrote:

...

1. I have a single-user Fusion license and so does the person I want to collaborate with.

If you use a paid subscription you might still use the Single-User Storage, however, but you have access to Fusion Team

and should create a team hub and move all of your projects over to that tam hub, even if you are the only user.

The team hub has features that are not accessible through Single-User Storage.

What the article @g-andresen linked to is describing is very new Fusion functionality. Previously, a Project in Fusion was only the top level folder in the Fusion 360 data panel. Anything in that project was a folder or a Fusion design.

If you wanted to share a project, you could not limit that to only a folder. That is not considered legacy functionality and you can update that project to the new functionality.

Afterward you can limit accessibility not only to a project, but also to a folder within that project.