A molecular modeling task rarely ends at the moment one person saves a document. A collaborator may need to inspect a structure, continue an analysis, run a job, or simply understand what has already been done. When the work moves between people, uncertainty about where to find it—and who can access it—can become its own obstacle.
SAMSON’s sharing and collaboration resources are organized around a useful distinction: SAMSON Connect explains the website and account context, while the collaboration material covers profiles, groups, permissions, shared documents, and shared jobs. Following that distinction can help you choose the right starting point instead of searching through unrelated instructions.
Start with the handoff you need
Before sharing, name the practical outcome. Are you giving someone a document to open, setting up a group, or coordinating access to a cloud job? Those needs lead to different parts of the documentation:
- Sharing or downloading a document: begin with Share documents.
- Organizing people or controlling access: read Collaboration for profiles, groups, and permissions.
- Finding account, download, Marketplace, or site information: begin with SAMSON Connect.
If you are new to the site, the recommended sequence is SAMSON Connect, then Share documents, then Collaboration. If your account is already set up, jump to the page that matches the handoff. This small choice saves time and makes it easier to focus on the actual work.
A practical pre-share checklist
Use these questions to make a handoff clearer for both sides. They are not extra SAMSON settings; they are a simple way to decide what to do before you follow the relevant sharing instructions.
- What should the recipient do? Open or download a document, join a group, or access a job? State the intended next step in your message.
- Which resource is being shared? Identify the document or job clearly so the recipient does not have to guess which item you mean.
- Who needs access? If the work involves a team, review the collaboration guidance on groups and permissions. Check that the access you arrange matches the people who need it.
- What should happen afterward? Tell the recipient whether you want them to inspect the work, make changes, or continue with another task. A clear request can prevent duplicate effort.
- Where does the workflow go next? After opening a shared document, the documentation points to Work with structures for inspecting or editing its contents. For cloud-job workflows, paths, and analysis, continue to Simulate and analyze.
Keep documents and jobs in view
Document sharing and job access are related, but they are not interchangeable tasks. A collaborator who needs a document may need the instructions for publishing or downloading shared documents. Someone coordinating a job should also consult the collaboration material, which includes job visibility and permissions. Treating these as separate parts of the handoff helps you avoid assuming that access to one resource automatically explains access to another.
For teams, it can help to agree on a lightweight routine: identify the item, name the intended collaborators, check the relevant permissions guidance, and include a short note about what the recipient should do next. That routine is useful whether the work is a one-time exchange or part of an ongoing group workflow. It also gives collaborators a shared reference point when they return to the project later.
When you are only managing downloads, Marketplace access, or account settings—and are not sharing work yet—you can postpone the collaboration guide. When sharing becomes part of the task, the documentation’s suggested paths make it easy to pick up from there.
For the full navigation and recommended reading order, see the Share and collaborate documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.