> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/training-c1-intro-to-paragon/3.0-intro-to-projects-and-settings/3.2-sharing-projects-via-shared-sets.md).
# 3.2 Sharing Projects via Shared Sets
Estimated Completion Time: 7 minutes
## Description
This module introduces how to share and view projects in the Paragon Design App.
## Objectives
* Share projects outside your organization.
* Explain how to create a Shared Component Set.
* Open a Shared Set.
* Copy a Shared Set to your organization.
* Describe how change notifications apply to Shared Sets.
## Additional Resources
* [Share Projects and Designs Docs](/design/how-to/general/share-trusses-and-request-seals-or-repairs.md)
## Learning Activity
Watch video and follow along within the Paragon Design App.
{% embed url="" %}
Video Transcript:
Welcome back! In this video, we’ll go over how to share and view projects in the Paragon Design App.
When collaborating with others, you may choose to share your project with someone outside your organization. Paragon’s Share feature allows you to create a view-only version of your project, ensuring that the recipient can see everything but cannot make any changes.
To share a project, click Share to create a new Shared Set. A Shared Set can contain one or more components and can even include the Layout, if applicable. Components must be analyzed to be added to a Shared Set. Select the analyzed components you want to share.
Next, name the Shared Component Set and then click Create Shared Component Set. Once the Shared Set is created, anyone outside your organization can access the shared set in view-only mode.
Once shared, you have several options: you can Copy the Link, Download design drawings, Email the shared component set, or Request a seal or repair.
If you update project components or the layout after sharing, the changes won’t appear in the shared set. Create a new set and share the updated link.
If the shared set owner makes changes to the original project, anyone viewing the existing shared set will be notified that changes have been made and to contact the owner for any updates.
Let’s go back, select Share once again, this time select Choose Existing Component Set, and now we see all our existing component sets. Click on an existing shared set and you’ll see the same share options as before. We’ll click Copy Link which copies the link to your (virtual) clipboard.
Now, let’s try opening a Shared Component Set. Using the link that’s copied to our clipboard, Open a new browser tab and paste the link. As you can see, everything is in view-only mode, meaning no modifications can be made. This ensures that changes cannot be made to the original project.
If you want a copy of the shared project where you have the ability to edit and modify it, simply click Copy to my Organization. This will duplicate the project so you can modify it without affecting the original, shared version.
And that’s how you can collaborate using Shared Component Sets! I hope you found this helpful. Thanks for watching, and see you in the next one!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.paragontruss.com/training-c1-intro-to-paragon/3.0-intro-to-projects-and-settings/3.2-sharing-projects-via-shared-sets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
