> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/getting-started/concepts-and-access.md).

# Concepts and Access

## Overview <a href="#overview" id="overview"></a>

Security data is sensitive. A vulnerability report can show an attacker exactly where to look. AttackForge is built so that everyone, from internal testers to clients and external vendors, can work in the same platform, while seeing only the data they need.

This page explains the main data concepts in AttackForge, what access can be controlled, exactly what each role and project access level can do, and how to bring external testing vendors into AttackForge safely. Use the permission tables to choose the right role and project access for each person, to answer "why can't I...?" questions, and to show auditors that access follows least privilege.

Internal teams, external testing vendors, auditors and AI agents all work on the same record of every test. Groups, project access, field-level access controls, and API and MCP permissions make sure each of them sees only what they need.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FzE0WYBgp98dX2ukTJFbF%2Fstakeholders-working-together.svg?alt=media&amp;token=d2da2ed0-1db5-4228-ae62-404c50445192" alt=""><figcaption></figcaption></figure>

## Why it matters <a href="#why-it-matters" id="why-it-matters"></a>

* **One platform, many parties.** Internal teams, clients and several external vendors can all work in AttackForge without seeing each other's data.
* **Least privilege by design.** Access is set on each object, down to individual fields, API endpoints and MCP tools.
* **Easier audits.** Access follows clear rules, so it's easy to show who can see what, and why.
* **Scales with you.** Groups let you manage access for whole teams or vendors at once, instead of person by person.

## Who benefits <a href="#who-benefits" id="who-benefits"></a>

| Who                                  | How                                                                              |
| ------------------------------------ | -------------------------------------------------------------------------------- |
| **Administrators**                   | Design access once, using groups, and apply it consistently                      |
| **Enterprise security teams**        | Bring external vendors in without exposing other vendors' or internal data       |
| **External vendors and consultants** | Work directly in AttackForge, with access to exactly what their engagement needs |
| **Clients and stakeholders**         | See their own projects and findings, and nothing else                            |
| **Auditors and risk teams**          | Get a clear audit trail of who did what                                          |

## Data concepts <a href="#data-concepts" id="data-concepts"></a>

The diagram shows the data concepts in AttackForge, and how they relate.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FxMfKgRcS1WP7pwiIKceb%2FAF%20Data%20Concepts.png?alt=media&amp;token=09ee168e-d602-4153-8524-56ee90d80be5" alt=""><figcaption></figcaption></figure>

In summary:

* **Portfolios** and **streams** group projects by business area, application or programme, so you can see risk across them.
* **Project requests** are how work is asked for. An approved request becomes a **project**.
* **Projects** hold the engagement: its scope, team, test cases, workspace, pages, reports and retests.
* **Vulnerabilities** are found on projects, and are linked to the **assets** they affect.
* **Asset libraries** hold assets across projects, so a vulnerability's history follows the asset.
* **Writeup libraries** hold reusable vulnerability writeups, which testers use when they create vulnerabilities.
* **Test suites** hold reusable test cases. They become **project test cases** when added to a project.
* **Groups** bring users together, and are the main way to give a team or vendor access to data.

## What access can be controlled <a href="#what-access-can-be-controlled" id="what-access-can-be-controlled"></a>

Access can be configured on all of these:

| Area                        | Objects                                                                                                                                               |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Portfolios**              | Portfolios; streams                                                                                                                                   |
| **Projects**                | Project requests; projects, which also control access to their vulnerabilities; project test cases; retests; attack chains; workspace; pages; reports |
| **Libraries and templates** | Asset libraries; writeup libraries; test suites; report templates                                                                                     |
| **People**                  | Groups                                                                                                                                                |
| **Automation**              | Flows; Actions                                                                                                                                        |
| **APIs and AI**             | Self-Service REST APIs, for each API endpoint; Self-Service Events APIs, for each API event; Model Context Protocol (MCP), for each tool              |
| **Fields**                  | Custom fields, with field-level access control                                                                                                        |

## How access works <a href="#how-access-works" id="how-access-works"></a>

Two things decide what someone can do:

|                | Application role                                                    | Project access level             |
| -------------- | ------------------------------------------------------------------- | -------------------------------- |
| **Applies to** | The whole of AttackForge                                            | One project                      |
| **Options**    | Admin, Project Coordinator, Library Moderator, Client or Consultant | Edit, Upload or View             |
| **Decides**    | Which modules and functions they can use                            | What they can do on that project |
| **Set in**     | The Users module                                                    | The project's team settings      |

Administrators and Project Coordinators also appear in the project privileges table, because their role gives them access on projects, whatever their project access level.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FkEDyWrzrYb4e8GpFtB8b%2Faccess-control-at-a-glance.svg?alt=media&amp;token=d5598c8e-3933-44e1-a294-a3083f53ed5a" alt=""><figcaption></figcaption></figure>

View suits clients and stakeholders. Upload adds sharing files and creating project notes. Edit, for testers, adds working on vulnerabilities, test cases and retests. Administrators and Project Coordinators get their project access from their role.

### What "Based on configuration" means <a href="#what-based-on-configuration-means" id="what-based-on-configuration-means"></a>

Some cells in the matrix say **Based on configuration**. These permissions aren't fixed by the role. They depend on how something has been set up, such as:

* access controls on a portfolio, asset library, writeup library or group
* a user's delegations or Flows access
* a project's settings

See [Users](https://support.attackforge.com/app/modules/users).

## Application user roles <a href="#application-user-roles" id="application-user-roles"></a>

What each application role can do across AttackForge. The Library Moderator role isn't recommended. Library access is now managed with access controls on each library.

### Global Dashboard, Analytics and Vulnerabilities <a href="#global-dashboard-analytics-and-vulnerabilities" id="global-dashboard-analytics-and-vulnerabilities"></a>

| Function                                              | Admin | Project Coordinator | Library Moderator | Client / Consultant |
| ----------------------------------------------------- | ----- | ------------------- | ----------------- | ------------------- |
| **Global Dashboard:** Has full access to this module  | Yes   | Yes                 | Yes               | Yes                 |
| **Analytics:** Can filter analytics on their data     | Yes   | Yes                 | Yes               | Yes                 |
| **Vulnerabilities:** Can filter their vulnerabilities | Yes   | Yes                 | Yes               | Yes                 |

### Portfolios <a href="#portfolios" id="portfolios"></a>

| Function                                                  | Admin | Project Coordinator    | Library Moderator      | Client / Consultant    |
| --------------------------------------------------------- | ----- | ---------------------- | ---------------------- | ---------------------- |
| Has full access to this module, including CRUD operations | Yes   | No                     | No                     | No                     |
| Has view access to portfolios                             | Yes   | Based on configuration | Based on configuration | Based on configuration |
| Has view access to streams                                | Yes   | Based on configuration | Based on configuration | Based on configuration |

### Projects <a href="#projects" id="projects"></a>

| Function                                                                    | Admin | Project Coordinator                   | Library Moderator      | Client / Consultant    |
| --------------------------------------------------------------------------- | ----- | ------------------------------------- | ---------------------- | ---------------------- |
| Can view projects they have access to                                       | Yes   | Yes                                   | Yes                    | Yes                    |
| Can access all projects by default                                          | Yes   | No                                    | No                     | No                     |
| Can perform all workflows on a project by default                           | Yes   | No                                    | No                     | No                     |
| Can create new projects                                                     | Yes   | Yes                                   | Based on configuration | Based on configuration |
| Can update projects                                                         | Yes   | Yes (for projects user has access to) | Based on configuration | Based on configuration |
| Can archive and unarchive projects                                          | Yes   | No                                    | No                     | No                     |
| Can destroy projects                                                        | Yes   | No                                    | No                     | No                     |
| Can invite users to projects                                                | Yes   | Yes (for projects user has access to) | Based on configuration | Based on configuration |
| Can manage user access to projects                                          | Yes   | Yes (for projects user has access to) | Based on configuration | Based on configuration |
| Can request new projects and update own project requests                    | Yes   | Yes                                   | Yes                    | Yes                    |
| Can access all pending and actioned project requests                        | Yes   | Yes                                   | Based on configuration | Based on configuration |
| Can approve, reject or request information for all pending project requests | Yes   | Yes                                   | Based on configuration | Based on configuration |

### Scheduling <a href="#scheduling" id="scheduling"></a>

| Function             | Admin | Project Coordinator | Library Moderator | Client / Consultant |
| -------------------- | ----- | ------------------- | ----------------- | ------------------- |
| Can see own projects | Yes   | Yes                 | Yes               | Yes                 |
| Can see all projects | Yes   | No                  | No                | No                  |

### Assets <a href="#assets-if-enabled" id="assets-if-enabled"></a>

| Function                                          | Admin | Project Coordinator                                         | Library Moderator                                           | Client / Consultant                                         |
| ------------------------------------------------- | ----- | ----------------------------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------- |
| Can create new assets                             | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can see own assets                                | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can see uncatalogued assets                       | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can see all assets, including assets in libraries | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can update own assets                             | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can update all assets                             | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can delete own assets                             | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can delete all assets                             | Yes   | Based on configuration                                      | Based on configuration                                      | Based on configuration                                      |
| Can view linked projects and groups on assets     | Yes   | Yes                                                         | No                                                          | No                                                          |
| Can view vulnerabilities on assets                | Yes   | Yes, only for vulnerabilities and assets user has access to | Yes, only for vulnerabilities and assets user has access to | Yes, only for vulnerabilities and assets user has access to |
| Can view and restore archived assets              | Yes   | No                                                          | No                                                          | No                                                          |

### Writeups <a href="#writeups" id="writeups"></a>

| Function                                                                     | Admin | Project Coordinator                     | Library Moderator                       | Client / Consultant                     |
| ---------------------------------------------------------------------------- | ----- | --------------------------------------- | --------------------------------------- | --------------------------------------- |
| Can create, read, update and delete writeups in the Main Library             | Yes   | Based on configuration                  | Based on configuration                  | Based on configuration                  |
| Can create, read, update and delete writeups in the Imported Library         | Yes   | Based on configuration                  | Based on configuration                  | Based on configuration                  |
| Can create, read, update and delete writeups in the Project Library          | Yes   | Based on configuration                  | Based on configuration                  | Based on configuration                  |
| Can create, read, update and delete writeups in Custom Libraries             | Yes   | Based on configuration for each library | Based on configuration for each library | Based on configuration for each library |
| Can create, read, update and restore vulnerabilities in the Archived Library | Yes   | No                                      | No                                      | No                                      |

### Test Suites, Groups and Users <a href="#test-suites-groups-and-users" id="test-suites-groups-and-users"></a>

| Function                                                                   | Admin | Project Coordinator              | Library Moderator                | Client / Consultant              |
| -------------------------------------------------------------------------- | ----- | -------------------------------- | -------------------------------- | -------------------------------- |
| **Test Suites:** Has full access to this module, including CRUD operations | Yes   | Yes                              | No                               | No                               |
| **Groups:** Has full access to this module, including CRUD operations      | Yes   | No                               | No                               | No                               |
| **Groups:** Can manage group membership                                    | Yes   | Based on configuration per group | Based on configuration per group | Based on configuration per group |
| **Users:** Has full access to this module, including CRUD operations       | Yes   | No                               | No                               | No                               |

### Flows <a href="#flows" id="flows"></a>

| Function                    | Admin                                                                   | Project Coordinator         | Library Moderator           | Client / Consultant         |
| --------------------------- | ----------------------------------------------------------------------- | --------------------------- | --------------------------- | --------------------------- |
| Has ability to create Flows | Yes                                                                     | Based on user configuration | Based on user configuration | Based on user configuration |
| Has ability to view Flows   | Limited, see [Flows](https://support.attackforge.com/app/modules/flows) | Limited, see Flows          | Limited, see Flows          | Limited, see Flows          |
| Has ability to edit Flows   | Limited, see Flows                                                      | Limited, see Flows          | Limited, see Flows          | Limited, see Flows          |
| Has ability to run Flows    | Limited, see Flows                                                      | Limited, see Flows          | Limited, see Flows          | Limited, see Flows          |

### Actions <a href="#self-service-api" id="self-service-api"></a>

| Function                      | Admin                                                                                               | Project Coordinator         | Library Moderator           | Client / Consultant         |
| ----------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------- | --------------------------- | --------------------------- |
| Has ability to create Actions | Yes                                                                                                 | Based on user configuration | Based on user configuration | Based on user configuration |
| Has ability to view Actions   | Limited, see [Actions](https://support.attackforge.com/app/automations-and-integrations/actions.md) | Limited, see Actions        | Limited, see Actions        | Limited, see Actions        |
| Has ability to edit Actions   | Limited, see Actions                                                                                | Limited, see Flows          | Limited, see Actions        | Limited, see Actions        |
| Has ability to run Actions    | Limited, see Actions                                                                                | Limited, see Actions        | Limited, see Actions        | Limited, see Actions        |

### Self-Service API <a href="#self-service-api" id="self-service-api"></a>

| Function                                       | Admin                                        | Project Coordinator                          | Library Moderator                            | Client / Consultant                          |
| ---------------------------------------------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------------- |
| Can generate own API key                       | Yes                                          | Yes                                          | Yes                                          | Yes                                          |
| Can access SSAPI RESTful endpoints and methods | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) |
| Can access SSAPI Events                        | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) | Yes (for APIs user has been given access to) |

### AI MCP <a href="#reporting-templates-attack-chains-and-administration" id="reporting-templates-attack-chains-and-administration"></a>

| Function                  | Admin                                         | Project Coordinator                           | Library Moderator                             | Client / Consultant                           |
| ------------------------- | --------------------------------------------- | --------------------------------------------- | --------------------------------------------- | --------------------------------------------- |
| Can connect to Local MCP  | Yes                                           | Based on user configuration                   | Based on user configuration                   | Based on user configuration                   |
| Can connect to Remote MCP | Yes                                           | Based on user configuration                   | Based on user configuration                   | Based on user configuration                   |
| Can access MCP Tools      | Yes (for Tools user has been given access to) | Yes (for Tools user has been given access to) | Yes (for Tools user has been given access to) | Yes (for Tools user has been given access to) |

### Reporting Templates, Attack Chains and Administration <a href="#reporting-templates-attack-chains-and-administration" id="reporting-templates-attack-chains-and-administration"></a>

| Function                                                                      | Admin | Project Coordinator | Library Moderator | Client / Consultant |
| ----------------------------------------------------------------------------- | ----- | ------------------- | ----------------- | ------------------- |
| **Reporting Templates:** Has full access to this module                       | Yes   | Yes                 | No                | No                  |
| **Attack Chains:** Has full access to this module                             | Yes   | Yes                 | Yes               | Yes                 |
| **Administration:** Has full access to this module, including CRUD operations | Yes   | No                  | No                | No                  |

## Project privileges <a href="#project-privileges" id="project-privileges"></a>

What each person can do on a project. Administrators and Project Coordinators get their access from their role. Everyone else gets it from their project access level: Edit, Upload or View.

### Project <a href="#project" id="project"></a>

| Function                                        | Admin | Project Coordinator | Edit                               | Upload                             | View                               |
| ----------------------------------------------- | ----- | ------------------- | ---------------------------------- | ---------------------------------- | ---------------------------------- |
| Can view project dashboard                      | Yes   | Yes                 | Yes                                | Yes                                | Yes                                |
| Can invite users to project                     | Yes   | Yes                 | Based on configuration per project | Based on configuration per project | Based on configuration per project |
| Can view project team and project group members | Yes   | Yes                 | Yes                                | Based on configuration per project | Based on configuration per project |
| Can edit project                                | Yes   | Yes                 | Based on configuration per project | Based on configuration per project | Based on configuration per project |
| Can place project on hold or off hold           | Yes   | No                  | Yes                                | No                                 | No                                 |
| Can add custom tags                             | Yes   | Yes                 | Yes                                | No                                 | No                                 |
| Can delete or archive project                   | Yes   | Yes                 | No                                 | No                                 | No                                 |
| Can view project logs                           | Yes   | Yes                 | No                                 | No                                 | No                                 |

### Scope and assets <a href="#scope-and-assets" id="scope-and-assets"></a>

| Function                                       | Admin | Project Coordinator | Edit | Upload | View |
| ---------------------------------------------- | ----- | ------------------- | ---- | ------ | ---- |
| Can view project scope and assets              | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can create, update and delete scope and assets | Yes   | Yes                 | Yes  | No     | No   |

### Testing <a href="#testing" id="testing"></a>

| Function                                                                                                          | Admin | Project Coordinator | Edit | Upload | View |
| ----------------------------------------------------------------------------------------------------------------- | ----- | ------------------- | ---- | ------ | ---- |
| Can view test cases and execution flows                                                                           | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can update test cases, including actioning, adding notes and uploading evidence, adding workspace notes and files | Yes   | No                  | Yes  | No     | No   |
| Can assign assets and users to test cases on a project                                                            | Yes   | Yes                 | No   | No     | No   |
| Can lock, unlock and delete test cases on a project                                                               | Yes   | Yes                 | No   | No     | No   |
| Can send daily start and stop testing email notifications                                                         | Yes   | No                  | Yes  | No     | No   |

### Retesting <a href="#retesting" id="retesting"></a>

| Function                                     | Admin | Project Coordinator | Edit | Upload | View |
| -------------------------------------------- | ----- | ------------------- | ---- | ------ | ---- |
| Can mark vulnerabilities as ready for retest | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can request a retest                         | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can confirm retest is completed              | Yes   | No                  | Yes  | No     | No   |
| Can view retesting history on project        | Yes   | Yes                 | Yes  | Yes    | Yes  |

### Vulnerabilities <a href="#vulnerabilities" id="vulnerabilities"></a>

| Function                                                                | Admin | Project Coordinator | Edit | Upload | View |
| ----------------------------------------------------------------------- | ----- | ------------------- | ---- | ------ | ---- |
| Can view all vulnerabilities (except vulnerabilities in pending status) | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can view pending vulnerabilities                                        | Yes   | Yes                 | Yes  | No     | No   |
| Can create, update and delete vulnerabilities                           | Yes   | No                  | Yes  | No     | No   |
| Can view remediation notes                                              | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can add remediation notes                                               | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can view, create and reply to review notes                              | Yes   | No                  | Yes  | No     | No   |
| Can view revision history                                               | Yes   | No                  | Yes  | No     | No   |
| Can import vulnerabilities from tools and API                           | Yes   | No                  | Yes  | No     | No   |
| Can export vulnerabilities                                              | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can update SLA                                                          | Yes   | Yes                 | No   | No     | No   |
| Can re-apply SLA                                                        | Yes   | Yes                 | No   | No     | No   |
| Can remove SLA                                                          | Yes   | Yes                 | No   | No     | No   |
| Can update remediation plan                                             | Yes   | Yes                 | Yes  | Yes    | Yes  |

### Attack chains <a href="#attack-chains" id="attack-chains"></a>

| Function                                                         | Admin | Project Coordinator | Edit | Upload | View |
| ---------------------------------------------------------------- | ----- | ------------------- | ---- | ------ | ---- |
| Can view attack chains                                           | Yes   | Yes                 | Yes  | Yes    | Yes  |
| Can create, update, re-order, duplicate and delete attack chains | Yes   | No                  | Yes  | No     | No   |

### Reporting <a href="#reporting" id="reporting"></a>

| Function                                                     | Admin | Project Coordinator | Edit                   | Upload                 | View                   |
| ------------------------------------------------------------ | ----- | ------------------- | ---------------------- | ---------------------- | ---------------------- |
| Can download reports                                         | Yes   | Yes                 | Yes                    | Yes                    | Yes                    |
| Can download project JSON export                             | Yes   | Yes                 | Yes                    | Yes                    | Yes                    |
| Can download evidence in ZIP archive                         | Yes   | Yes                 | Yes                    | Yes                    | Yes                    |
| Can view executive summary                                   | Yes   | Yes                 | Based on configuration | Based on configuration | Based on configuration |
| Can update executive summary                                 | Yes   | No                  | Based on configuration | No                     | No                     |
| Can view, create and reply to executive summary review notes | Yes   | No                  | Yes                    | No                     | No                     |

### Daily tracking, collaboration and workspace <a href="#daily-tracking-collaboration-and-workspace" id="daily-tracking-collaboration-and-workspace"></a>

| Function                                                               | Admin | Project Coordinator | Edit | Upload                              | View |
| ---------------------------------------------------------------------- | ----- | ------------------- | ---- | ----------------------------------- | ---- |
| **Daily tracking:** Can view schedule and tracking                     | Yes   | Yes                 | Yes  | Yes                                 | Yes  |
| **Collaboration:** Can view project team member profiles               | Yes   | Yes                 | Yes  | Yes                                 | Yes  |
| **Workspace:** Can upload files to the project workspace               | Yes   | No                  | Yes  | Yes                                 | No   |
| **Workspace:** Can create, update and delete workspace notes and files | Yes   | No                  | Yes  | No                                  | No   |
| **Workspace:** Can upload testing logs                                 | Yes   | No                  | Yes  | No                                  | No   |
| **Workspace:** Can create project notes                                | Yes   | No                  | Yes  | Yes, however can only see own notes | No   |

## Onboarding external testing vendors <a href="#onboarding-external-testing-vendors" id="onboarding-external-testing-vendors"></a>

Many enterprise security teams use external consultants and MSSPs for some of their testing. Asking vendors to work directly in AttackForge, instead of sending reports to be imported, has many advantages.

Give each vendor its own group, and link the group to that vendor's projects and writeup library. Your own testers work through their own group. Nothing is given to the whole Consultant role, so vendors never see each other's data.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FvY8AUTzt9E3o8lXi39sb%2Fdata-access-at-a-glance.svg?alt=media&amp;token=7c041e0d-754f-4abb-9072-b6a193131538" alt=""><figcaption></figcaption></figure>

| Benefit                                                                         | Why it matters                                                                                                                                                                                                               |
| ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **No import pipeline to maintain**                                              | No custom import scripts for each vendor, so no format changes, rejected rows or reconciliation work at reporting time                                                                                                       |
| **Findings land as they're discovered**                                         | Critical findings appear straight away, so remediation can start while testing is still under way. This supports continuous threat exposure management (CTEM).                                                               |
| **Methodology and coverage are captured**                                       | Test cases are annotated as testers work, so you see what was tested and passed, not just what failed. Coverage is standard, and aligned to your organisation's risk appetite. This helps with audits and comparing vendors. |
| **Better prioritisation, clearer reporting, faster response, fewer duplicates** | Findings are linked to writeups, severities, CVSS vectors and assets. Deduplication, history and portfolio trends all rely on this clean data, and retests link back to the original finding.                                |
| **Automation fires at the right time, in the right order**                      | Flows, Actions, Jira sync and notifications run for each finding as it's created, and SLA clocks start on the actual discovery date                                                                                          |
| **Evidence lands with the finding**                                             | Screenshots, request and response pairs, PoC files and reproduction steps are attached as the finding is written, and ReportGen builds reports from them                                                                     |
| **The retest loop closes inside the platform**                                  | Retest requests, results and evidence are recorded on the same finding, with no emails or re-imports                                                                                                                         |
| **Direct communication with the person who found it**                           | Questions and comments sit on the finding, so the tester's answers are kept for auditors                                                                                                                                     |
| **Per-tester attribution and a real audit trail**                               | Every action is timestamped against the person who took it, which supports accountability and independence                                                                                                                   |
| **Vendor consistency at scale**                                                 | Every vendor works in the same structure, so coverage, quality and turnaround can be compared                                                                                                                                |
| **Data ownership and continuity**                                               | Findings belong to you from the moment they're written, whether or not you renew with the vendor                                                                                                                             |

### Checklist for onboarding vendors <a href="#checklist-for-onboarding-vendors" id="checklist-for-onboarding-vendors"></a>

The aim is that each vendor sees only its own projects and data, and never another vendor's.

1. **Check how vendor users sign in.** Vendor users should sign in with local accounts and have the **Consultant** role. If they use SSO, check your SSO role mapping. See [Administration: users](https://support.attackforge.com/app/modules/administration#users).
2. **Create a group for each vendor.** Make the vendor's point of contact a **group membership administrator**, so they can manage their own team. See [Groups](https://support.attackforge.com/app/modules/groups) and [Group membership admins](https://support.attackforge.com/app/modules/groups#group-membership-admins).
3. **Review existing access controls.** Remove any access given to the whole **Consultant** role, because every vendor user has that role. Give your own testers access through a group, such as an "Internal Pentester" group, instead. Vendors shouldn't be able to see each other's data. See "What access can be controlled" above.
4. **Give vendors their own writeup library, if they create writeups.** Create a writeup library for each vendor, and give the vendor's group **Edit** access to it. See [Writeups](https://support.attackforge.com/app/modules/vulnerability-library) and [Administration: writeups](https://support.attackforge.com/app/modules/administration#writeups).
5. **Share your writeup libraries as read-only.** Give each vendor's group **View** access to the writeup libraries you share, so vendors can use them but not change them.
6. **Add the vendor to each project.** When you create a project, link the vendor's group to it, or make the vendor's point of contact a **project membership administrator**. See [Projects](https://support.attackforge.com/app/modules/projects), [Linking groups](https://support.attackforge.com/app/getting-started/creating-and-managing-projects#linking-groups) and [Member admins](https://support.attackforge.com/app/getting-started/invite-user-to-project#member-admins).
7. **Test it.** Create a test account with the **Consultant** role, sign in as it, and check it can only see what it should.
8. **Decide whether vendors need asset library access.** Vendors only need access to an asset library to import vulnerabilities. They can see the asset data in a project's scope either way. If vendors don't import vulnerabilities, don't give them access to any asset library. If they do, create an asset library just for them, and give them **Edit** access to it. See [Grouping and managing access to assets](https://support.attackforge.com/app/modules/assets#grouping-and-managing-access-to-assets), [Importing vulnerabilities](https://support.attackforge.com/app/getting-started/creating-vulnerabilities#importing-vulnerabilities) and [Project scope](https://support.attackforge.com/app/getting-started/project-scope).

## Tips <a href="#tips" id="tips"></a>

* **Manage access through groups, not individuals.** It's easier to keep consistent, and to remove when a vendor or team leaves.
* **Avoid giving access to a whole role**, such as Consultant, when the role is shared by people who shouldn't see each other's data.
* **Give vendors the least access they need**, such as View on shared writeup libraries, and no asset library access unless they import vulnerabilities.
* **Let vendors manage their own teams** by making their point of contact a group or project membership administrator.
* **Always test with a vendor-style account** after changing access.

## FAQ <a href="#faq" id="faq"></a>

**Can one vendor see another vendor's projects?** Not if access is set up through a separate group for each vendor, and no access is given to the whole Consultant role.

**Do vendors need asset library access?** Only to import vulnerabilities. They can see the asset data in a project's scope either way.

**Can a vendor change our writeups?** Not if their group only has View access to your writeup libraries. Give them their own library, with Edit access, if they write their own.

**Who adds new vendor testers?** The vendor's point of contact can, if you make them a group membership administrator or a project membership administrator.

**Can access be controlled for APIs and AI tools?** Yes. Self-Service REST APIs are controlled for each endpoint, Events APIs for each event, and MCP for each tool.

**Do findings stay ours if we stop using a vendor?** Yes. Findings belong to you from the moment they're written.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Groups](https://support.attackforge.com/app/modules/groups)
* [Invite user to project](https://support.attackforge.com/app/getting-started/invite-user-to-project)
* [Creating and managing projects](https://support.attackforge.com/app/getting-started/creating-and-managing-projects)
* [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms)
* [Working with service accounts](https://support.attackforge.com/app/getting-started/working-with-service-accounts)
* [Access Control Matrix](https://support.attackforge.com/app/access-control-matrix)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.attackforge.com/app/getting-started/concepts-and-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
