You are trying to make progress on a molecular model, but something gets in the way: an installation question, an extension that is not behaving as expected, or a feature whose details you need to check. The next step can feel surprisingly unclear. Should you search for a quick answer, follow troubleshooting instructions, or open a detailed reference?
Choosing the right kind of help first can save time. The SAMSON documentation organizes these needs into three paths: FAQ for recurring questions, Troubleshooting for problems described by their symptoms, and References for detailed information about a particular feature area.
Start with the kind of question you have
Before browsing, take a moment to describe the obstacle in one sentence. For example: “I need an answer about an account or update,” “Something is going wrong at runtime,” or “I know which feature I’m using and need its reference.” This small distinction helps you choose a useful starting point instead of scanning documentation that may not address your immediate need.
- Is this a recurring question? Start with the FAQ. It is the recommended first stop for common questions about accounts, installation, updates, and extensions.
- Do you know what is going wrong from its symptoms? Go directly to Troubleshooting. This is the practical path when you need to diagnose a problem and find a possible fix.
- Do you know the feature area you need to understand? Use References to find the relevant detailed reference family.
Why the order matters
These resources serve different purposes. A reference page can explain a feature in depth, but it may not be the quickest way to resolve a common account or installation question. Conversely, an FAQ answer may not give you the detailed feature information you need. Troubleshooting is useful when the issue is defined by what you observe, rather than by a general question about how something works.
Think of the choice as matching the documentation to your next action: answer a recurring question, investigate a symptom, or look up a feature. You do not need to read every section before getting help. If you already know which category fits, skip the other paths and go straight to the relevant resource.
A quick decision guide
- Write down the question or symptom in plain language.
- If it concerns accounts, installation, updates, or extensions, check the FAQ.
- If you are trying to resolve a specific problem, use Troubleshooting.
- If you need the canonical details for a known feature area, browse References.
- If none of these is the right next step, return to the broader Start here guide for installation and first-use orientation.
This approach is especially handy when you are switching between modeling work and documentation. Instead of treating every question as a search through the whole guide, identify what kind of answer would let you continue: a short recurring answer, a fix path, or feature-specific detail. That gives you a clear next destination while keeping deeper references available when you actually need them.
For questions about sharing work, permissions, groups, or shared documents and jobs, the Share and collaborate guide is another relevant route. For scripting, extensions, and developer-facing workflows, see Automate and extend.
For the full help overview, visit the Reference and help documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.