PenTest.WS Documentation
  • What is PenTest.WS?
    • Tier Comparison
  • Getting Started
    • Dashboard
    • Creating An Engagement
    • Main Window Layout
    • Engagement Console
    • Import Nmap & Masscan XML
    • Port Scan Templates
    • Adding Hosts Manually
    • Adding Ports to Hosts
    • Capturing Credentials
  • Hosts & Services
    • Host Page
    • Port Page
    • Global Service Notes
    • Service Command Library
    • Default Service Checklist
    • Scratchpad Editor
  • Views & Filtering
    • Boards
    • The Matrix
    • Subnetting
  • User Libraries
    • Shells Library
    • General Command Library
    • General Notes Library
    • Bookmark Library
  • Built-In Tools
    • Echo Up
    • CyberChef
    • Venom Builder
  • Search Capabilities
    • CVE DB
    • Exploit-DB
    • Nmap Scripts
    • Metasploit Modules
    • Keyword Search
  • Findings
    • Findings Admin
    • Findings Library
    • Engagement Findings
  • Clients & Reporting
    • Write-Ups
    • Clients Manager
    • Reporting Templates
    • Generating Deliverables
  • Collaboration
    • User Maintenance
    • Shared Engagements
    • Access Control List
  • Automation & Integration
    • API
    • SMTP
  • Authentication
    • Two-Factor Authentication
    • LDAP Authentication
  • Exporting & Importing
    • Export Account Items
    • Import Account Items
    • Export to CSV / JSON
  • Pro Tier
    • Admin Panel
    • Intranet Mode
    • Solo Mode
    • Large Engagement Support
Powered by GitBook
On this page
  • Team Missions
  • Tier Availability
  1. Collaboration

Access Control List

PreviousShared EngagementsNextAPI

Last updated 2 years ago

Example URL: http://localhost:7897/e/{engagement.id}/console

In a Pro Tier's Shared Engagement, the owner of an Engagement (the user who created the Engagement) can grant Read Only or Full Access to teammates on an individual basis.

Alternatively, you can choose to make an Engagement Public, granting full access to all teammates. Engagements default to Restricted Access with all teammates in the No Access bucket.

An Engagement’s Access Control is available in the Console tab.

Team Missions

  • In the example above, we are logged into the "alice" account.

  • The user "demo" has given "alice" Full Access to the "Demo" engagement.

  • The user "bob" has made his "ABC Widgets" engagement Public

Team Missions only appear if you have access to another user's Shared Engagement.

Tier Availability

Access Control is available on Pro Tier.

Shared Engagements appear on the remote user’s under the Team Missions section.

Dashboard
Shared Engagement's Access Control
Team Missions