Enable a Command in Your Project

New Container Service Accessibility feature
As of Container Service version 3.7.0+, containers can have one of three accessibility modes: Public (default), Private and Protected.

In order to launch containers using Container Service context menus, the corresponding container commands need to be enabled at the project level by a project owner or a site admin.

Before configuring container project settings, commands must first be installed and enabled for your project by a Container Manager. See Enabling Site-wide Commands

To enable commands, navigate to your project’s page. Click the Project Settings link in the Actions box.

Click the Configure Commands tab. Here you will see a list of installed commands that are available to your project. These commands are either public to all projects on your XNAT, or protected/private commands that have been specifically enabled for your project.

Click the Enabled toggle on the wrapper you want to enable.

Setting Project-specific Defaults

Optionally, you can click the Set Defaults button in the Actions column to customize the default values and matchers for the command and wrapper inputs in your project.

Specifying input config values in this window will override site-wide and command default values.

Note: Use caution in overriding values for inputs configured to “User-Settable=No” or in changing the value of User-Settable, as doing so may short-circuit auto-discovery of derived container input values.

Requesting Access to Protected Commands

Project Owners who are looking to enable commands in their project will see protected commands listed, even if they are have not been explicitly made available to their project. XNAT will show a “Request Access” button next to these commands in the Project Settings.

Project availability must be set by the Container Manager. See Enabling Commands and Setting Site-wide Defaults. e