--- title: "Assay Overview" slug: "assay-overview" updated: 2026-09-09T13:54:27Z published: 2026-09-09T13:54:27Z canonical: "docs.discngine.com/assay-overview" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.discngine.com/llms.txt > Use this file to discover all available pages before exploring further. # Assay Overview Assay is an application that enables users to analyze data from in vitro plate-based experiments in a structured and efficient manner. See [Application Navigation](/public/docs/application-navigation-assay) for guidance on navigating the application. ## Run A run is a step-by-step analysis of plate-based experimental data. Runs can operate in different modes, each offering varying levels of automation. The process begins with raw data import, followed by calculations, visualizations, and data validation, and concludes with the publication of analyzed results. Runs may be executed in several modes, depending on the stability of the experimental protocol and the degree of automation provided by the platform. See [Runs documentation](/public/docs/runs-overview) for details on navigating and managing runs. ### Design Mode In `Design Mode`, each step of the analysis workflow must be manually defined. This mode allows you to specify data sources, integration methods, calculation steps, and publication settings. At the end of the process, you can save the configuration as a template, which can later be used to create new runs in `Execution Mode` with pre-filled, non-editable settings. Only users with the `Assay Designer` role can access `Design Mode`. See [Design Modes guide](/public/docs/design-modes-overview) for instructions on creating runs in `Design Mode`. ### Design from Template `Design from Template` mode allows you to modify the configuration of an existing template to create a new one. The template's information is pre-filled and fully editable, enabling you to generate new templates for use in `Execution Mode`. See [Design Modes guide](/public/docs/design-modes-overview) for instructions on using `Design from Template` mode. ### Execution Mode In `Execution Mode`, the run configuration is pre-filled and cannot be modified. This configuration is derived from a template created in `Design Mode`. `Execution Mode` is intended for screeners to perform standardized, routine analyses. Although the core settings of a run in `Execution Mode` are fixed, you can: - Upload raw data - Adapt or change predefined plate layouts - Set well information as needed - Assign well samples and doses - Define well experimental conditions - Invalidate aberrant wells, fields, or source data `Execution Mode` is available to users with the `Assay Screener` role. See [Execution Mode guide](/public/docs/execution-mode-overview) for details on creating and managing runs in this mode. ## Cross Runs A `Cross Run` is a collection of runs that can be analyzed together, facilitating comparison of key data points across multiple experiments. See [Cross Runs and Campaigns guide](/public/docs/cross-runs-and-campaigns) for more information on creating and using cross runs. ## Campaign A `Campaign` is a group of experiments designed for cross-analysis. Typically, the same experimental protocol is applied to different samples, which are then analyzed in a consistent manner. By default, all runs are visible to users with access to the application. If campaign security is enabled, only runs associated with a campaign are visible to users with access to that campaign. Contact your administrator if you require this setting. See [Cross Runs and Campaigns guide](/public/docs/cross-runs-and-campaigns) for guidance on using campaigns. ## Administration The `Administration` page is used to configure the application and manage customizable elements such as Readers, Layouts, and Normalizations. See [Administration guide](/public/docs/administration-overview-assay) for instructions on using the administration features.