Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata


The Mission Control Admin module provides access to a variety of configuration screens as well as scripting and other functionality as follows:

Create and modify service configuration scripts and configure how they are managed in version control.
Define and configure proxies through which Mission Control will access the services under its control.
Add and modify users and their privileges in Mission Control.
Notifications Group

Define usage policies and thresholds that specify when notifications will be sent and configure a mail server through which to send them.

Manage license buckets or individual licenses for specific services.
Configure Master and Target pairs for disaster recovery.

Admin Module

Page Contents

Read More





Scripts are an easy way to define standard, repeatable and automated configuration for the different managed services.

To access your library of scripts, under the Admin module select Scripts | Scripts Lib.

For full details on how to work with scripts, please refer to Configuration Scripts

Version Control

Mission Control supports versioning for configuration scripts in a Git repository. To configure a Git repository for configuration script versions, in the Admin module select Scripts | Version Control.

For details, please refer to Git Integration  

Configuring Proxies

For each managed service, you can configure a proxy through which Mission Control will access it.

To view the list of proxies configured, in the Admin module, select Proxy | Config proxy.

Proxy List

To edit or delete a proxy, hover over the proxy's row in the list and click the corresponding icon.

To create a new proxy, click Create Proxy.

Create Proxy

A logical name for this proxy
The proxy URL
User Name
A user name required to access the proxy server (optional).
The password required to access the proxy server (optional).

Configuring Users

To manage users in Mission Control, in the Admin module select Security | User Management.

Mission Control users vs. Artifactory users

Be careful not to confuse this feature with managing users in the services managed by Mission Control.

Users List

To edit or remove an existing user, click the corresponding link in the user's row in the table.

To create a new Mission Control user, click "Create User".

Create or edit a user

Fill in the fields and click "Submit"

MC password

The Mission Control password must be at least 8 characters long and contain both letters and numbers.


Mission Control sends email notifications to users for different events that occur; for example, notifications that are generated due to storage policies that are defined for instances or repositories.

To enable mail notifications, you need to configure Mission Control with your mail server details in the Admin module under Notifications Group | Mail.

Mail configuration

Enables the configured mail server
The host name of the mail server.
The port of the mail server.
The username for authentication with the mail server.
The password for authentication with the mail server.

The "from" address header to use in all outgoing mails.

Subject Prefix
A prefix to use for the subject of all outgoing mails.
When set, uses Transport Layer Security when connecting to the mail server.
Send Test Mail
Click to send a test message to the specified email address.


Mission control can send email notifications based on policies you define for instances and repositories. For example, you can configure Mission Control to send an email message if any Artifactory instance exceeds a limit for usage of storage. For details, please refer to Notifications.


The Admin module provides access to the Update Licenses and License Bucket screens where you can manage licenses for specific services or license buckets for a group of services. For details, please refer to Licenses under Managing Services.

Disaster Recovery

The Admin module provides access to the Disaster Recovery screen where you can configure Master and Target pairs of Artifactory services. For details, please refer to Disaster Recovery


  • No labels