Project Configuration
This section helps sponsors, CROs, and project teams prepare a new SliceVault repository.
SliceVault handles the technical setup. Your role is to define the project workflow, what users should see, what they should do, and what outputs the project should produce.
A SliceVault repository is usually shaped by a small number of decisions: how uploaded data moves through the workflow, which visits exist, which forms users complete, how images are labeled, what different users are allowed to see, and which outputs or exports are needed. A useful planning question is this: When a user logs in, what should they see, what should they do, and what should happen next? If your team can answer that clearly, onboarding usually moves much faster.
How Onboarding Works
Onboarding is a collaboration between your project team and SliceVault. You describe how the study should work from the user perspective, including workflow steps, visit structure, forms, images, and any special settings. We then turn that into a configured repository, prepare a test environment, and support User Acceptance Testing (UAT) with your team.
Once the configuration is final, we will ask you to sign a system acceptance protocol. After that, we clone the testing repository and open the empty production repository so it is ready for your project.
The most helpful onboarding material is usually practical and concrete: a workflow description, visit schedule or protocol summary, example forms, short notes on responsibilities, screenshots of expected outputs, and anything important about image labeling, visibility, or special settings.
Work through these pages in order:
- Workflow
- Visit Schedule
- Forms
- Images and Labels
- Advanced Settings
- Technical Details
- Configuration Form