• View detailed information about the system configuration and installed modules.
• Audit user activity including who is logged in and when.
• Customize the LabKey site, including configuration and testing of LDAP settings.
• View information about the JAR files and executable files shipped with LabKey.
• View information about memory usage and errors.

Navigate to the Admin Console

The Admin Console can be accessed by Site Administrators:

• At the top right of your screen, select Admin > Site > Admin Console

Use the Admin Console

A variety of tools and information resources are provided on the Admin Console.

Configuration

• Analytics Settings. Add JavaScript to your HTML pages to enable Google Analytics or add other custom script to the head of every page.
• Authentication. View, enable, disable and configure authentication providers (e.g. LDAP, CAS, Duo).
• Change User Properties. Edit fields in the Users table.
• Email Customization. Customize auto-generated emails sent to users.
• Experimental Features. Offers the option to enable experimental features. Proceed with caution as no guarantees are made about the features listed here.
• Files. Configure file system access by setting site file root and configuring file and pipeline directories.
• Flow Cytometry. Settings for the flow module.
• Folder Types. Select which folder types will be available for new project and folder creation. Disabling a folder type here will not change the type of any current folders already using it.
• Look and Feel Settings. Customize colors, fonts, formats, and graphics.
• Mascot Server. Set up integration with a Mascot server.
• Missing Value Indicators. Manage indicators for datasets.
• Profiler. Tracks the duration of requests and any queries executed during the request. Available on servers running in dev mode or for developers in production mode.
• Project Display Order. Choose whether to list projects alphabetically or specify a custom order.
• Short URLs. Define short URL aliases for more convenient sharing and reference.
• Site Settings. Configure a variety of basic system settings, including the name of the default domain and the frequency of system maintenance and update checking.
• System Maintenance. These tasks are typically run every night to clear unused data, update database statistics, perform nightly data refreshes, and keep these server running smoothly and quickly. We recommend leaving all system maintenance tasks enabled, but some of the tasks can be disabled if absolutely necessary. By default these tasks run on a daily schedule. You can change the time of day which they run if desired. You can also run a task on demand by clicking these links:
• Database Maintenance.
• Report Service Maintenance.
• MS1 Data File Purge Task.
• Search Service Maintenance.
• Purge Unused Participants.
• Refresh Study Snapshot Specimen Data. Refreshes the specimen data inside of published studies.
• Views and Scripting. Allows you to configure different types of scripting engines.
• Configure Scripting Engines. Configure scripting engines for quality control or transformation of assay data.
• Install and Set Up R. Configure R scripting engine.

Management

• Audit Log. View the audit log. This includes Copy-To-Study History.
• ETL-All Job History. View a history of all ETLs that have run on the site.
• ETL-Run Site Scope ETLs. ETLs that are "site scoped" (not scoped to a particular folder/container) can be run from here.
• Full-Text Search. Configure and view both primary and external search indexing.
• MS1 and MS2. Administrative information for these modules.
• Ontology. Admin console for defining types, such as SampleSets or Forms.
• Pipeline. Administrative information for the pipeline module.
• Pipeline Email Notification. Enable pipeline notification emails.
• Protein Databases. Protein Database Administration interface.
• Site-Wide Terms of Use. Require users to agree to a terms of use whenever they attempt to login to any project on the server.

Diagnostics

Various links to diagnostic pages and tests that provide usage and troubleshooting information.

• Actions. View information about the time spent processing various HTTP requests.
• Caches. View information about caches within the server.
• Check Database. Check database table consistency, validate that domains match tables, and generate a database schema in XML format.
• Credits. Jar and Executable files distributed with LabKey Server modules.
• Data Sources. A list of all the data sources defined in labkey.xml that were available at server startup and the external schemas defined in each.
• Dump Heap. Write the current contents of the server's memory to a file for later analysis.
• Environment Variables. A list of all the current environment variables and their values, for example, CATALINA_HOME = C:apacheapache-tomcat-7.0.52
• Loggers. Log4j loggers. Set the level (info, warn, error, etc.). Use the text box to enter filters.
• Memory Usage. View current memory usage within the server.
• Queries. View the SQL queries run against the database, how many times they have been run, and other performance metrics.
• Reset Site Errors. Reset the start point in the labkey-errors.log file. See View All Site Errors Since Reset below.
• Running Threads. View the current state of all threads running within the server.
• Site Validation. Runs any validators that have been registered. (Validators are registered with the class SiteValidationProvider.)
• SQL Scripts. Provides a list of the SQL scripts that have run, and have not been run, on the server. Includes a list of scripts with errors, and "orphaned" scripts, i.e., scripts that will never run because another script has the same "from" version but a later "to" version.
• System Properties. A list of current system properties and their values, for example, devmode = true.
• Test Email Configuration. View and test current SMTP settings. See labkey.xml Configuration File for information about setting them.
• View All Site Errors. View the current contents of the labkey-errors.log file from the TOMCAT_HOME/logs directory, which contains critical error messages from the main labkey.log file.
• View All Site Errors Since Reset. View the contents of labkey-errors.log that have been written since the last time its offset was reset through the Reset Site Errors link.
• View Primary Site Log File. View the current contents of the labkey.log file from the TOMCAT_HOME/logs directory, which contains all log output from LabKey Server.

Core Database Configuration and Runtime Information

View detailed information about the system configuration.

Module Information

View detailed version information for installed modules.

Active Users in the Last Hour

Lists who has used the site recently and how long ago.