A question can interrupt molecular modeling at exactly the wrong moment: an installation issue blocks a session, an extension does not behave as expected, or you need a precise reference for a feature you already know. The challenge is not always finding information—it is choosing the right kind of information without browsing the whole guide.
A useful first step is to describe the problem in one sentence. Are you looking for a recurring answer, trying to fix a symptom, or checking how a particular feature works? That small distinction points you toward the most relevant help page and can save you from following a longer path than you need.
Three questions, three destinations
- Is this a common question? Start with the FAQ for recurring questions about accounts, installation, updates, and extensions. It is a good first stop when you are not sure whether your question has a quick, established answer.
- Do you have a specific problem or symptom? Go to Troubleshooting. This is the practical route when something is not working as expected and you need a fix-oriented path.
- Do you know which feature you need information about? Use References to reach the detailed reference family for that area of SAMSON.
A quick example of the decision
Imagine that an extension is involved in your question. If you are asking a general, recurring question about extensions, begin with the FAQ. If an extension-related issue is preventing you from working, choose Troubleshooting. If you simply need the detailed information for a feature area, use References.
The subject alone does not determine the best page; your goal does. “I have a question about extensions” is less useful as a search strategy than “I need a common answer,” “I need to resolve a problem,” or “I need feature details.” Classifying the goal first helps keep the search focused.
When to skip a step
Not every question needs the same reading sequence. If the issue is clearly symptom-based, you can go straight to Troubleshooting rather than starting with the FAQ. If you only need a feature reference, you can skip troubleshooting. And if you need a quick answer or fix, you may not need to browse the broader References hub at all.
This is a simple way to avoid a common documentation detour: reading a broad reference when what you need is a practical fix, or looking through troubleshooting material when you are only trying to locate feature details. Use the shortest route that matches the task in front of you.
Keep the next step in view
Some questions point beyond immediate help. For installation, first-use orientation, and onboarding follow-up, continue to Start here. For SAMSON Connect, permissions, groups, and shared documents or jobs, visit Share and collaborate. For scripting, extensions, and developer-facing workflows, see Automate and extend.
When you are unsure, begin with the FAQ; then switch to a symptom-based fix or a feature reference as soon as you know which kind of help you need. To explore the full help map, visit the Reference and help documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.