A molecular model can be ready for review while still being difficult for anyone else to find, open, or continue working on. The challenge is not only sharing a file: it is choosing the right route for the task, then making clear what others should be able to access. SAMSON’s documentation separates the relevant steps across SAMSON Connect, document sharing, and collaboration. Knowing what each part is for can make a handoff easier to plan.
Start by identifying what needs to move
Before sharing, ask a simple question: are you trying to give someone a document, coordinate access with a group, or manage visibility for a cloud job? These are related, but they are not the same workflow.
- A document needs to be shared or downloaded: start with Share documents.
- People, groups, or permissions need to be organized: go to Collaboration.
- You need to understand the website, your account context, or downloads and Marketplace access: begin with SAMSON Connect.
This distinction helps avoid a common source of delay: looking for a group or permission workflow when the immediate need is simply to share a document, or starting with collaboration settings when the account and site context are not yet clear.
A practical route for a handoff
If you are setting up collaboration from scratch, follow the documented sequence: SAMSON Connect, then Share documents, then Collaboration. Each step answers a different question: where the site workflows live, how documents are shared, and how profiles, groups, permissions, shared documents, and shared jobs fit into collaboration.
For a smoother handoff, pair that route with a short note to your collaborators. State what you are sharing, what you would like them to do next, and whether the task concerns a document or a job. This is a communication practice, not a setting in SAMSON, but it helps recipients understand why they have been given access and what kind of response is useful.
Choose the shortest path that fits
You do not need to explore every collaboration feature just because you are using SAMSON Connect. If your task is limited to downloads, Marketplace access, or account settings and you are not sharing work, the documentation says you can skip the Collaboration page for now.
When the goal is sharing documents or jobs, the recommended path is SAMSON Connect → Share documents → Collaboration. When you are specifically organizing groups and permissions, use SAMSON Connect → Collaboration. These paths are useful because they keep the task focused while still pointing you toward the foundational context when you need it.
Think beyond the moment of sharing
A handoff is more useful when it has a clear next step. Once a shared document is opened or downloaded, a collaborator may need guidance on inspecting or editing its contents; the documentation points to Work with structures for that stage. For cloud-job workflows, paths, and analysis, it points to Simulate and analyze. If the work involves scripted documents or automation, Automate and extend is the next relevant topic.
Thinking about these follow-on needs before sending a handoff can help you include the right context: what the recipient should inspect, whether they are expected to work with a document or job, and where to look for the next workflow. It does not replace access management, but it makes the collaboration easier to understand.
A quick checklist
- Identify whether you are sharing a document, coordinating a group, or dealing with a job.
- Start with SAMSON Connect if you need account or site context.
- Use Share documents for document-sharing workflows.
- Use Collaboration for profiles, groups, permissions, shared documents, and shared jobs.
- Tell collaborators what you shared and what action or review you need.
- Point them to the next relevant workflow if they need to inspect structures, analyze jobs, or extend the work with automation.
For the complete reading guide and suggested paths, see the Share and collaborate documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.