Welcome to Cmd. 

All Cmd environments start with one user who has a global admin account, and manages the initial configuration of Cmd.

Cmd setup tasks for a global admin

Several tasks can be completed only by a global admin:

  1. Invite additional users to Cmd:
    If you add more global admins, they can help with the following steps.

  2. (Optional) Build your projects:
    Projects organize your Cmd-enabled servers into separate environments, which can help with the management of log data and security rules.

  3. Configure global permissions:
    Customize Cmd for the preferences of your organization.
    - Configure global security settings.
    - Set global integrations permissions.
    Note: All integrations are enabled by default (i.e. they can be enabled by project administrators).

Cmd setup tasks for global admins, admins, or managers

  1. Add additional users:
    - Admins/managers who can configure your Cmd platform;
    - Viewers, who can monitor Cmd data; and,
    - Server operators, who can access Cmd-enabled servers.

  2. Add servers:
    - Install the Cmd agent on a single server using a bash script, or...
    - Deploy the Cmd agent to a fleet of servers or containers.

  3. Configure project settings:
    Configure settings related to the Cmd web app and agent.

  4. Set up project-level integrations:
    Configure specific integrations at the project level.

  5. Create your first triggers:
    Triggers form the heart of Cmd's enforcement capabilities. They enable you to make rules about what happens on your servers.

  6. Set up reports:
    Cmd's reporting tools help filter through Cmd data and quickly summarize it in meaningful ways.



Did this answer your question?