- About XNAT
- News & Events
- XNAT Marketplace
- Contact Us
XNAT is now easier to set up and configure than ever before, with more control being brought in front of admins via the Admin UI.
With that said, however, there are some tasks related to administering your XNAT that still require access to the file system (such as adding pipelines and plugins), and still some reporting (such as complex data freezes) that can only be done with access to the PostgreSQL database.
These guidelines will teach you the "what", "why", and "how" of being an XNAT Admin.
To get a guided walkthrough of the core tasks of administering an XNAT, try taking the free Admin 101 Course on XNAT Academy
See Getting Started With XNAT for a full guide to XNAT installation options
The first time you launch XNAT, there are a series of initial configurations that must be set. This will only happen once.
XNAT is a powerful set of software with a complex set of components under the hood. However, we provide administrative tools that allow you to control many core behaviors directly from the UI. You must be logged in as a site administrator to access these controls.
You can set XNAT Administrator privileges to give admin users access to all studies and study data in your XNAT. For more details, see Administering Users.
The Pipeline Engine is being deprecated in XNAT 1.8, and the "Autorun" pipeline is no longer running by default. Snapshot generation is now handled by an internal service. Processes can still be run in pipelines, but in the interest of reproducible science, we highly recommend converting your computational processes to containers.
Setting up the Container Service
Configuring The Pipeline Engine
Enabling the XNAT Event Service
Monitoring Event Service History
Known Caveats and Limitations of the Event Service
This section is also available in the XNAT IT Operations documentation.