Go to Cmd
Project settings glossary
A detailed overview of the 'Project settings' menu, including teammates, servers, web app, agent, and integration settings.
Ben Ironside avatar
Written by Ben Ironside. Updated over a week ago

This page describes the options on the 'Project settings' menu. First it explains how to access the menu, then explains each setting in detail.

You may also be interested in the guide about first steps for configuring Cmd, or the glossaries of global security and integrations settings.
  

How to access project settings

  1. In the top-right corner of the web app, click the current project's name to open the drop-down list.

  2. Select Project & app settings.

  3. From the left-hand menu, under 'Project settings', select one of the following options:
    - Users & Roles
    - Servers
    - Web app
    - Agent
    - Integrations preferences
    - Project history

  4. When finished making changes, click Save at the bottom of the page.

 

Table of Contents

Teammates

Add new users to the project, update existing users, and update user roles (including which roles have PAM and package management privileges). For more information, see Adding new users.

Servers

Manage your servers, add new servers, manage your server groups, and more. For more information, see Monitoring sessions, Managing servers, or Managing server groups.

Web app

Customize settings related to the web app:

  • Set a trigger notification interval
    Cmd alerts sent to external apps such as email, Slack, or SumoLogic are batched in intervals between 1 minute and 60 minutes in length. Select how often you would like these alerts to send.

  • Hide non-interactive sessions
    Enable to hide non-interactive sessions from the results displayed on the 'Sessions' and 'Reports' pages of the web app. Choosing to enable this option can improve web app performance and reduce session noise.
    Note: With this setting enabled, you can still display non-interactive sessions in a particular search by including  session_include_non_interactive = 'true'  in your search query.

Agent

  • Live data scrubbing
    Configure the system to automatically sanitize sensitive data such as passwords. Sanitized content is redacted and no longer visible to anyone. For more information about setting up scrubbers in your Cmd projects, see RE2 scrubbers.

  • Environment variables capture
    Select up to five env vars to capture on session connect. Learn more.

  • Commands output
    Select which commands, output, and modified files Cmd will log.
        - Capture all command output:
          Allow Cmd to capture all command output.

        - Capture only command output with errors:
          Allow Cmd to capture only command output that results in errors.

        - Disable:
          Keep Cmd from logging output.

  • Inactive session timeout
    Enable this setting to automatically log users out of servers after periods of inactivity.

    When enabled, you can set the maximum amount of time (in minutes) that the user can be inactive before they are automatically logged out.

  • Offline settings
    Set the maximum amount of local storage for data collected on a server during offline mode. The default is 256MB, and the max is 2048MB.

    You can enable data prioritization to prioritize which data to store when the Cmd agent cannot communicate with the Cmd collector. When the amount of memory allocated for offline data is reached, data prioritization will remove data in the following order: output data, then non-basic command data, and then non-user entered commands.
    Note: If the data prioritization setting is disabled, data will be collected without priority until the maximum is reached.

  • Automatic agent updates
    Toggle automatic updates for agents on servers in this project.

    When automatic updates are off, you can also view and download various versions of the agent.

  • 2-factor authentication options
    Customize which 2FA methods may be used for authentication. By default all methods are enabled.
    Note: For more information, see the 'Authorization trigger actions available' section of Understanding trigger actions.

    Users must configure each method in account settings before using it, except for Duo. If setting up a Duo integration, this page is also where you'll choose which Duo integration you'd like to use for Duo authentication (simply choose the appropriate integration from the drop-down list).

Integrations 

Once a global admin has enabled an integration at the global level, you can set it up in a project.

Project history

Here, you can review changes to the project's configuration. To search for a specific type of activity, click All Activity in the top-right corner to open a list of filters. To locate a specific activity, use the search bar in the top-right corner of the page. To view more details about an activity, click the details icon on the left side of its row.
 
 

Did this answer your question?