Choose how to share according to what the recipient needs to do. Working together in the original resource, using a finished experience, and adapting an independent copy are different relationships.
Choose the relationship
| Goal | Method | Boundary |
|---|---|---|
| Adapt a reusable foundation | Marketplace remix. | Independent work with recipient setup. |
| Collaborate on existing work | Resource invitation. | No broader Workspace access. |
| Take a result elsewhere | Supported export. | Independent of later edits. |
| Use an interactive result | Artifact sharing. | No source conversation access. |
| Visit released software | Site visitor access. | Separate from source editing and Site management. |
Resource collaborators need not become Workspace members. Use Permissions to understand roles and authority; use the relevant product guide for its sharing controls.
Example: deliver a calculator
Your team creates an interactive calculator using private customer research. A client who only needs the calculator can receive access to the retained Artifact. They do not need an invitation to the producing Chat or Project.
Review the calculator itself before sharing it. Separate access controls protect the original research, but information included in the calculator is visible to its audience.
If the client wants to adapt a reusable solution independently, consider a Marketplace template. If they need a production application, use a Site with the appropriate visitor controls.
Check the recipient's experience
Before sharing, decide:
- Which resource or result the recipient needs.
- Whether they should view, edit, run, manage, or reuse it.
- Whether the result itself contains information outside the intended audience.
- Whether their use can start chargeable work in the owning Workspace.
A link to a restricted resource does not replace an invitation. Public audiences, where supported, have different rules from authenticated collaborator roles. Follow the product's controls rather than assuming the same audience setting applies everywhere.
Use the relevant guide
After sharing
Review access when the collaboration ends or responsibilities change. Revocation can prevent future access, but it cannot recall a downloaded export or information already received.
A remix is also independent: changes to your original do not silently update someone else's copy. See Remixing for version behavior and Usage for who funds shared work.