A modeling workflow can be interrupted by a small but frustrating question: Is this a common setup issue, a problem that needs troubleshooting, or a question about how a particular SAMSON feature works? Choosing the wrong kind of help can add unnecessary browsing when all you need is a clear next step.
A useful way to get unstuck is to classify the question before searching. The SAMSON documentation’s help pages are organized around three different needs: quick answers, symptom-based fixes, and detailed feature references. Once you know which one fits, you can go directly to the relevant resource instead of treating the whole guide as one long search.
First, name the problem you are trying to solve
Take a moment to describe the question in plain language. Is it about an account, installation, update, or extension? Is something not working as expected? Or do you already know the feature you are using and need its detailed reference?
This simple distinction matters because those questions call for different reading paths. A question about an account or installation is not necessarily a software malfunction. A reproducible problem is not necessarily answered by a feature reference. Starting with the right category helps keep the search focused.
Use this three-way decision
- Looking for a recurring answer? Start with the FAQ. It is the recommended first stop for common questions about accounts, installation, updates, and extensions.
- Trying to fix a problem described by a symptom? Go to Troubleshooting. This is the practical path when you need to diagnose an issue and find a possible fix.
- Need details about a particular feature family? Open References. Use it when you know the feature area and want its deeper reference information.
A quick example of choosing a path
Suppose you are preparing to work in SAMSON and have a question about an update. That is a recurring, general question, so the FAQ is a sensible first stop. If instead something in the platform is behaving unexpectedly and you need a fix path, start with Troubleshooting. If the problem is no longer about diagnosing an issue and you want the detailed information for a known feature area, move to References.
The key is to follow the kind of question, not just the fact that it arose while modeling. A workflow interruption can feel like one big problem, but identifying whether you need an answer, a fix, or a feature description makes it easier to choose what to read next.
Keep the search efficient
- Write down the question in one sentence. For example: “I need a common answer,” “I need to diagnose a problem,” or “I need details about a feature.”
- Choose the matching resource. Use FAQ for recurring questions, Troubleshooting for symptom-based problems, and References for feature details.
- Switch paths only when the question changes. If an FAQ answer does not address a practical malfunction, move to Troubleshooting. If troubleshooting is no longer the goal and you need feature specifics, consult References.
This approach also helps when you are unsure where to begin: the recommended order is FAQ, then Troubleshooting, then References. But it is a guide, not a requirement to read every page. If you already know that you have a symptom-based problem or need a feature reference, you can go straight to that resource.
When your question belongs elsewhere
Not every question is a help or reference question. For installation and first-use orientation, continue to Start here. For SAMSON Connect, permissions, groups, or shared documents and jobs, visit Share and collaborate. For scripting, extensions, and developer-facing workflows, see Automate and extend.
When a modeling task is stalled, you do not always need to search more—you may simply need to choose a more fitting kind of help. Use the Reference and help guide to find the right route.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.