Swift Security Docs
  • Introduction to Swift Security
  • Onboarding
    • Tenant Setup
    • Product Deployments
      • Browser Extension
      • LLM Guardrails
        • LLM Guardrails API Integration
      • VS Code IDE Extension
    • Directory Sync
      • Configuring Google Directory Sync
      • Configuring Microsoft Directory Sync
    • MDM
      • Extension Deployment Via Google Workspace
      • Extension deployment via google workspace + MDM at device level
      • Extension Deployment Via Microsoft Intune
        • Chromium Browsers in Windows
        • Edge Browsers in Windows
        • Firefox Browsers in Windows
      • Extension Deployment Via Kandji
        • Chromium Browsers in Mac
    • Infrastructure
      • SaaS Model
      • Hybrid deployment (coming soon)
  • SSO (Single Sign-On)
    • SSO Configurations identity provider - Google workspace
  • Administrative Guide
    • Console Users
      • Role Creation
      • RBAC General Settings for Login Methods (for the Console)
      • User Creation
      • SSO login(okta)
    • Swift Detection Engines
      • Data Identifiers
        • Custom Data Identifiers
      • EDM Dictionaries
        • EDM Rule
        • EDM Profile
        • EDM Extension Policy
      • Data Rules
        • Custom Rules
      • Data Profiles
      • LLM Guardrail Scanners
        • Data Protection Scanner
        • Gibberish Scanner
        • Ban Substrings Scanner
        • Invisible Text Scanner
        • Code Scanner
        • Language Scanner
        • Sentiment Analysis Scanner
        • Jailbreak Scanner
        • Toxicity Scanner
        • Prompt Injection Scanner
        • Token Limit Scanner
        • Reading Time Scanner
        • Language Same Scanner
        • No Refusal Scanner
        • Factual Consistency Scanner
        • Bias Detection Scanner
        • URL Reachability Scanner
        • Nudity Scanner
        • Gender Scanner
        • Celebrity Scanner
        • Face Scanner
        • Race Scanner
        • Performance and Benchmark
    • Browser Extension
      • Extension Installation
      • Granular Policies
        • Control URL access
        • Protect company data
        • Protect against Threats (Coming Soon)
      • Extension Alerts
      • Extension Events
      • Extension Popups
      • Browser Extension Coverage
    • LLM Guardrails
      • LLM Guardrails Policies
      • LLM Guardrails Alert
      • LLM Guardrails Events
    • Regulation Laws
  • Assets
    • Applications
    • Users
    • Extensions
  • Integration
    • Notification
      • Jira
      • ServiceNow
      • Slack
      • Splunk
    • Forensic
    • Feature
      • Rules Glossary
        • United States
        • Canada
        • Latin America
        • European Union
        • Australia
        • APAC (Asia-Pacific)
        • EMEA Countries
        • Others
      • Data identifiers Glossary
        • United States
        • Canada
        • Latin America
        • European Union
        • Australia
        • APAC (Asia-Pacific)
        • EMEA Countries
        • Others
      • Supported MIME Types
      • Supported OCR Format
    • Manage unauthorized access from unmanaged browser
  • Settings
    • Manage Reasons
    • Audit Log
  • Release Notes
    • Version - 1.27
    • Version - 1.26
    • Version - 1.25
    • Version - 1.24
    • Version - 1.23
    • Version - 1.16
    • Version - 1.15
    • Version - 1.14
    • Version - 1.13
    • Version - 1.12
    • Version - 1.11
    • Version - 1.10
    • Version - 1.09
    • Version - 1.08
    • Version - 1.07
    • Version - 1.06
    • Version - 1.05
    • Version - 1.04
    • Version - 1.03
    • Version - 1.02
    • Version - 1.01
Powered by GitBook
On this page
  1. Administrative Guide
  2. Console Users

Role Creation

PreviousConsole UsersNextRBAC General Settings for Login Methods (for the Console)

Last updated 10 months ago

When an organization is successfully onboarded to our Swift Security platform, the following steps are carried out to ensure a smooth and professional integration:

Role Configuration:

  • The Tenant Admin will then configure roles for the organization's users. These roles will be tailored to the specific needs and structure of the organization, ensuring that users have the appropriate level of access and permissions to perform their duties.

In our system, we have predefined roles to ensure proper access control and manageability. These roles are as follows:

  1. Tenant Admin: This role is designed for administrative users who need comprehensive access to the system. Users assigned to the Tenant Admin role have permissions that allow them to both read and manage all aspects of the system.

  2. Normal User: This role is intended for regular users who require access to view information within the system. Users assigned to the Normal User role have read-only permissions, meaning they can view content but do not have the ability to make changes.

  3. Delegated Admin: This role is for administrators with all privileges except the ability to manage other admins.

  4. Restricted Admin: This role is for administrators with read-only access to all areas.

  5. Directory Admin: An administrator responsible for managing users.

  6. Security Admin: An administrator responsible for managing settings related to security.

  7. Security Architect: An administrator responsible for managing policies.

  8. Analyst Permissions: An administrator who has permissions to manage Alerts, Events, and Assets.

Custom Role Creation for Users:

  • Login: The Tenant Admin logs into the Swift Security platform.

To create a new role in the RBAC settings, please follow these steps:

  1. Navigate to the Settings Section:

    • Begin by accessing the main menu and selecting "Settings."

  2. Select the RBAC Option:

    • Within the Settings menu, locate and select the "RBAC" (Role-Based Access Control) option.

  3. Click on the Role Tab:

    • Once in the RBAC section, click on the "Role" tab.

  4. Create a New Role:

    • On the right side of the Role section, look for a button labeled "NEW ROLE."

    • Click the "NEW ROLE" button to begin the process of creating a new role.

Configure the New Role:

  • A form or wizard will appear where you can enter details for the new role. This typically includes:

    • Role Name: A descriptive name for the role.

    • Description: An optional description of what the role is for.

    • Permissions: Select the permissions or access rights this role will have.

Save the New Role:

  • After configuring the role, there should be a button to save or create the role. Click this button to finalize the creation of the new role.

View the New Role:

Once the role is created, ensure it appears in the list of roles.

To edit or delete a role within the RBAC settings, please follow these detailed instructions:

Editing a Role

  1. Choose the Role to Edit:

    • Find the role you wish to edit from the list.

    • Click on the three vertical dots (also known as the action menu) next to the role you want to modify.

  2. Edit the Role:

    • Select the "Edit" option from the action menu.

    • Update the necessary details in the role form, such as the role name, description, or permissions.

  3. Save the Changes:

    • After making the required changes, click the "Save" button to apply the updates to the role.

Deleting a Role

  1. Choose the Role to Delete:

    • Find the role you wish to delete from the list.

    • Click on the three vertical dots (action menu) next to the role you want to remove.

  2. Delete the Role:

    • Select the "Delete" option from the action menu.

    • A confirmation pop-up will appear. Review the details to ensure you are deleting the correct role.

  3. Confirm the Deletion:

    • Click the "Confirm" button in the pop-up to permanently delete the role.

By following these steps, you can effectively manage your roles within the RBAC settings, ensuring that roles are edited or deleted as per the organization's needs.