Spyderbat
Book a DemoStart FreeContact Us
  • Spyderbat Product Docs
  • Getting Started
    • Create an Organization
    • Install the Nano Agent
    • Three Things to Try with Spyderbat Community Edition
    • Manage Users and Roles
  • Installation
    • Spyderbat Nano Agent
      • Kubernetes
        • Pre Deployment Environment Data Collection Script
      • Linux Standalone
      • AWS Unattended Install
        • Secure your Registration Code with AWS Secrets Manager
      • Create a Golden Image with the Nano Agent Pre-Installed
    • Spyderbat AWS Agent
      • AWS Linux VM
      • Kubernetes
      • Configuration Guide - AWS Linux VM
      • Configuration Guide - Kubernetes
    • Install Spyctl CLI
      • Initial Configuration
    • Install Spydertop CLI
    • Install the Spyderbat Event Forwarder
      • Helm Chart
      • Traditional Installer
  • Concepts
    • Guardian & Interceptor
      • Ruleset Policies
      • Workload Policies
    • Flashback (Go Back In Time)
      • Investigations
    • Search
      • Saved Searches
    • Summarize
      • Spydertrace Summarize
    • Dashboards
      • Dashboard Categories
    • Reports
    • Notifications
      • Notification Targets
      • Notification Templates
    • Actions
    • Integrations
      • AWS Integration
      • Spyderbat Event Forwarder
    • Suppression & Tuning
    • Scout (Detections)
      • Custom Flags
  • Tutorials
    • Flashback
      • How to Use the Investigations Feature in Spyderbat
    • Guardian
      • How to Lock Down Your Workloads With Guardian Policies Using Spyctl
      • How to Put Guardrails Around Your K8s Clusters Using Spyctl
    • Integrations
      • How to Configure Event Forwarder Webhook for Panther
      • How to Set Up Spyderbat to Ingest Falco Alerts
      • How to Create and Use a Spyderbat API Key
    • Notifications
      • How to Set Up Notifications Using Spyctl
      • How to Set up Agent-Health Notifications Using Spyctl
    • Dashboards
    • Miscellaneous
      • How to Set Up Spyderbat to Monitor Systems From vulnhub.com
    • Scout (Detections)
      • How to Set Up Custom Flags Using Spyctl CLI
  • Reference
    • Policies
      • Response Actions
    • Rulesets
    • Selectors
    • Notifications
    • Spyctl CLI
      • Spyctl Commands
      • Guardian Policy Management using Spyctl
      • Notification Template Management using Spyctl
      • Notification Target Management using Spyctl
    • Search
      • All Operators
      • All Fields
      • All Related Objects
  • Quick Links
    • Contact Us
    • Try Spyderbat for Free
    • Book a Demo
Powered by GitBook

© SPYDERBAT, Inc., All Rights Reserved

On this page
  • Organization Management Section Overview
  • Adding and Removing Users in Your Organization in Spyderbat UI
  • Spyderbat User Roles and Definitions
  • Changing User Roles (Upgrading or Downgrading Permissions)

Was this helpful?

Export as PDF
  1. Getting Started

Manage Users and Roles

Learn about creating, modifying and deleting users, as well as assigning access permissions and privileges, in the Spyderbat UI.

Last updated 1 year ago

Was this helpful?

Published: July 20, 2023

You have set up your organization in the Spyderbat UI, maybe even installed a few Spyderbat Nano Agents. It is time to invite additional team members and set up their login credentials as well as access permissions. In this article we are going to cover the user and role management within your organization.

Organization Management Section Overview

If you are the Spyderbat Organization owner, then by default you will be set up with Admin level permissions and therefore will have access to the Admin section of the console, located at the bottom of the left hand navigation panel:

Only Admins are able to see this section in the UI. No other user role grants access to Organization Management options.

Here you are able to perform standard user management activities, as such as:

  • Invite new users

  • Remove existing users

  • Change user roles

Adding and Removing Users in Your Organization in Spyderbat UI

If you are an organization Admin and would like to grant access to the Spyderbat UI to other users, you can do so by populating the user’s email address and selecting a role that they should be assigned from the Roles drop-down:

Once the desired selections have been made, click “Add User” and you will see their email address and role come up under Accounts below and a confirmation will pop up:

The user will then receive an email confirmation letting them know they have been added by you to your organization in the Spyderbat console.

To remove a user from the Organization, the Admin must hover over the row with the user’s email address and click the “delete” icon next to it:

A confirmation will pop up that the user has been removed successfully:

No notification email will be sent to the user to let them know they have been removed from the organization.

Once the user has been removed, if they had an active session at the time of removal, they will immediately see the following page:

Spyderbat User Roles and Definitions

There are four distinct roles to choose from in every organization in the Spyderbat platform that are available to help manage access to different parts of the UI as well as define permissions associated with managing the monitoring scope, the collected data and the data consumption methods.

The roles offered today are:

Admin

Power

User

Agent

Deployment

Read

Only

Organization and user management

Full access

No access

No access

No access

Nano agent install and addition of new sources to scope

Full access

Full access

View and add access

View access

Agent health monitoring

Full access

Full access

View access

View access

Dashboards review

Full access

Full access

No access

View access

Dashboard creation

Full access

Full access

No access

View access

Search query creation and execution

Full access

Full access

No access

View access

Process investigations

Full access

Full access

No access

View access

K8S investigations

Full access

Full access

No access

View access

Notifications setup

Full access

No access

No access

No access

  • Admin

    Users with this role are able to access all sections of the UI and have Read, Edit and Delete permissions where these actions are available. Admins are also able to manage users and access by inviting new users into the organization, deleting existing users or upgrading/downgrading user privileges by changing the assigned roles.

    As a best practice recommendation, you should not have a lot of users with the Admin role in your organization and should likely be limited to 1-2 users

  • Power User

    This user will have full access to all sections of the UI (except for organization and user management) and have Read, Edit and Delete permissions where these actions are available.

  • Agent Deployment

    This role is intended for an onboarding engineer(s) who will be responsible for installing Spyderbat Nano Agents on the hosts (VM’s and K8s clusters) that are part of the organization’s monitoring scope. These users can access Sources and agent Health sections of the Spyderbat UI and have access to agent install scripts and commands.

  • Read Only

    This role is self explanatory. Users with Read Only access are able to see all sections of the UI, except for the Admin section. They can view dashboards, all monitoring and other metadata collected by the Spyderbat Nano Agents in the Sources and Agent Health sections, as well as view process and K8s investigations and share permalinks. They will not be able to make any changes to the data, like change source names, or archive offline sources, for example.

Changing User Roles (Upgrading or Downgrading Permissions)

If you are an organization Admin, you are able to change user roles of your organization members in the Admin → Organization Management section. To modify a user’s role, you need to click on the Roles drop-down, select the new role, deselect the existing role and click “Save”:

Note: if you do not deselect the existing role, then the user will be saved with both roles associated with their account and the higher-permission role will prevail in that case: