...
For our early phase customers, sites can only be added by ‘superadmin’ users through the assistance of our support team via service desk ticket. This is by design, due to the potential cost implications for adding and using sites across the system for recruitment and study conductcollecting study data against external (non-core) sites. More details about those costs are noted here: https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3897294849/ClinSpark+Pricing#Multi-site-support
For our customers who use ClinSpark in an operational model supporting later-phase multi site trials, users with the Administration > Sites role action on their account will be able to add sites without ‘superadmin’ intervention. We have a more detailed guide for our customers who setup and use sites for this purpose in this article: Setting Up Sites
Adding sites
...
Fill out as much of the site details as possible including address, phone, and investigator details. Once a site has been added to a study configurations, the investigator details can be modified per study.
Always select a timezone setting that appropriately matches the physical location (closest city or region).
Establish height/weight unit of measure appropriate to the site geographic location.
Ensure proper volunteer display patterns to meet site regional privacy laws.
...
If customers have any questions about establishing site entities, they are encouraged to reach out to via service desk ticket.Sites are only allowed to be added into a ‘MAIN’ environment (such as PROD MAIN). Sites cannot be added into any environments that are running in Test Mode.
Through study design import functionality, sites are added and synchronized into matching TEST environments. Site attributes remain in synch between MAIN/TEST environment pairs through the import mechanism over time. More details about this process are here: https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3708944593/Notes+on+Study+Design+Export+and+Import#Site-configurations