User Manuals Overview

User Roles

While the DetaBord development platform can be freely configured for different roles and access schemes via it’s powerful policy system per default there are three main user roles with different responsibilities:

AdministratorData OwnerData Scientist
The IT department is responsible for installing and maintaining DetaBord. DetaBord can be used as a cloud platform. Nevertheless, since sensitive data is included in the core of the DetaBord software by the secure enclave (also called “data quarantine”), it often makes sense to choose the “on-premise” version of DetaBord, which installs the software in the customer’s data center where the data is stored.The Data Owner role describes those users who own the data but do not necessarily want to analyze it themselves. Data Owners decide which data sources are made available via DetaBord for secure data science analysis. They also monitor the modeling on the data and decide on the accessibility of models (pre-checked by DetaBord).Data Scientists are the users who develop the analytics and models on the data. With DetaBord you can use the known methods and frameworks of machine learning and analysis. You simply implement the specified interfaces to DetaBord in order to be able to work securely with the sensitive data.
InstallationTechnical DocumentationCLIAPIIntroDatasetsApprovalsAuditsPoliciesIntroDatasetsRuns & ExperimentsModelsSQL QueriesApprovalsSDKML ExampleSQL Example

DetaBord Software Clients

DetaBord uses an end-to-end encrypted messaging protocol through which users of the platform communicate with the secure platform instance, managing the sensitive datasets. There are three ways to communicate with DetaBord:

  • studi0 – the DetaBord web application, this is the recommended choice
  • cli – the DetaBord command line interface
  • API – the DetaBord application programming interface to integrate DQ0 into existing solutions

The studi0 web application uses the DetaBord cli program locally to communicate via encrypted messages. See the architecture documentation for more details.

There are dedicated manuals for the CLI and the API, the rest of these manuals refer to the studi0 web application.

Join Waitlist

Join the AI for Life Sciences Challenge

Let's talk