Basic sciNote components are organized into a hierarchical structure, where projects are considered as the first structural level, followed by the experiments and then finally tasks. Tasks can form an experimental workflow when connected to each other, otherwise they can be stand-alone units (see the image below).
When you open a task, each task includes an overview of protocols, results, activity, samples, reports and custom repositories (see the image below).
sciNote business model is based on the number of teams you wish to have. A team is usually a group of people working on the same projects or experiments and sharing the same repositories (e.g. protocol repository) as well as same database of samples. Teams could represent different departments within your company.