> 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/modules/groups.md).

# Groups

## Overview

Groups give you enterprise-level user administration, and control over your data. A group brings users together, such as a customer, a vendor or an internal team. You give access to the group, and its members inherit that access through the group.

People join a group directly, through SSO groups, or by a Group Membership Admin. Each member has a Project Access Level and a Project Request Access Level. Whatever the group is linked to, its members can access, at their own level.

Most access controls in AttackForge can be applied to roles, groups or individual users. Groups are usually the easiest to manage, because you change access in one place when people join, move or leave. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FPxtHioti2CR6HRUdrk9w%2Fgroups-at-a-glance.svg?alt=media&amp;token=0aa8c15c-1edf-4c63-ad84-d9e215306c14" alt=""><figcaption></figcaption></figure>

## What groups can manage

| Area                  | What groups manage                                                                                                    |
| --------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **People**            | Users and SSO groups, customers and teams                                                                             |
| **Testing data**      | Portfolios, projects (including their vulnerabilities), project requests, assets, writeups, reports and custom fields |
| **Automation and AI** | Self-Service APIs, events, Flows, Actions and AI MCP                                                                  |

And more.

## Why it matters

* **Simple, manageable access.** Change a group once, and every member's access changes with it.
* **Keep customers and vendors apart.** Each one gets its own group, and only sees what that group can access.
* **Share the work.** Group Membership Admins let customers and teams manage their own people, without involving application administrators.
* **Stay in step with your identity provider.** Link a group to IDP or AD groups, and membership is added and removed at each SSO login.

## Who uses it

| Who                           | To                                                                            |
| ----------------------------- | ----------------------------------------------------------------------------- |
| **Administrators**            | Create groups, link them to data, and decide who manages each one             |
| **Group Membership Admins**   | Add and remove members, and invite new users, within the limits they're given |
| **Security teams**            | Separate internal teams, vendors and customers, and control who sees what     |
| **Customers and vendors**     | Manage their own team's access to their projects and project requests         |
| **Identity and access teams** | Link groups to IDP or AD groups, so access follows your directory             |

## Create a group

Click `New` to create a group. Fill in the details including any custom fields.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FoRThMDKScKBpCk8r7yh2%2FScreenshot%202026-11-10%20at%2011.46.20%E2%80%AFam.png?alt=media&amp;token=38b4c244-d0eb-4fe3-a93b-19f78aac4fba" alt=""><figcaption></figcaption></figure>

When you create a group, you can also set the options below. After creating the group, you can invite members, assign Group Membership Admins, and link the group to the data and features it should have access to.

## Auto Add Project Request

With this option on, the group is automatically added to project requests that its members create, and any custom access controls on the group apply straight away.

This lets a dedicated team, such as a customer's security team, view, edit and approve its own project requests, without involving Administrators or Project Coordinators.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F1twiHxNr7vYJ9HAc4Fwl%2FScreenshot%202026-11-10%20at%2011.47.33%E2%80%AFam.png?alt=media&amp;token=46c798b0-ad9e-461b-87a6-bb7b37951b74" alt=""><figcaption></figcaption></figure>

## Project Team Notifications

This option puts the group in scope for project email notifications. Whether each member actually receives the emails depends on the project's email settings and the member's own notification preferences. See [Notifications](https://support.attackforge.com/app/getting-started/notifications).

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FOi4AStmq2K76mTy1bLyk%2FScreenshot%202026-11-10%20at%2011.48.05%E2%80%AFam.png?alt=media&amp;token=4795941a-a1e2-479f-ab8b-1af6a2c554a6" alt=""><figcaption></figcaption></figure>

## Group Overview

The Group Overview gives you a single view of the group's projects and vulnerabilities. You can also see the group's assets and attack chains, and view and manage its members.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FD2ewOjtCBCHLWlziWwoy%2FScreenshot%202026-11-10%20at%2011.48.40%E2%80%AFam.png?alt=media&amp;token=cb07a2c6-a7b2-4c56-848a-b063dd0ea526" alt=""><figcaption></figcaption></figure>

## Manage members

Group membership makes sure the right people have the right access, in a way that's easy to manage.

1. On the group, click `Members`.
2. Manage existing members, or add a new one.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F9WNQA2PCDC4R9jaEFblR%2FScreenshot%202026-11-10%20at%2011.49.09%E2%80%AFam.png?alt=media&amp;token=add94829-2799-4734-99d5-c3d1d11b8d7d" alt=""><figcaption></figcaption></figure>

When you add a member, you can, depending on your access:

* choose a user from a drop-down list, or enter their email address
* invite a new user to AttackForge and make them a group member
* set their **Project Access Level**, which applies to every project linked to the group
* set their **Project Request Access Level**, which applies to every project request linked to the group

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FQXSkUbA3WzKqtaS8pREZ%2FScreenshot%202026-11-10%20at%2011.49.39%E2%80%AFam.png?alt=media&amp;token=b8f67bf5-874e-48e5-a837-e4e237778b22" alt=""><figcaption></figcaption></figure>

### Project Access Level

| Level      | What the member can do on the group's projects                             |
| ---------- | -------------------------------------------------------------------------- |
| **None**   | No access through this group                                               |
| **View**   | View the project, its vulnerabilities and reports                          |
| **Upload** | Everything in View, plus upload files and create project notes             |
| **Edit**   | Everything in Upload, plus work on vulnerabilities, test cases and retests |

See [Invite user to project](https://support.attackforge.com/app/getting-started/invite-user-to-project#access-roles) and [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access) for the full detail.

### Project Request Access Level

| Level      | What the member can do on the group's project requests |
| ---------- | ------------------------------------------------------ |
| **None**   | No access through this group                           |
| **View**   | View the project request                               |
| **Edit**   | View and update the project request                    |
| **Action** | Edit, plus approve or reject the request               |

See [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project#project-request-direct-access-controls).

## Delegate management with Group Membership Admins

You can delegate the management of a group to other users or groups. This helps you:

* let customers and engineering teams manage which stakeholders can access their projects and project requests
* let security teams manage groups as they need to
* reduce the workload on application administrators

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FkzFQfibQ8GxSJr2m4cf4%2FScreenshot%202026-11-10%20at%2011.51.27%E2%80%AFam.png?alt=media&amp;token=aa9197c3-74fd-4b26-9c95-f83bc62410f7" alt=""><figcaption></figcaption></figure>

When you make a user or group a Group Membership Admin, you can set:

| Setting                                | What it controls                                                                    |
| -------------------------------------- | ----------------------------------------------------------------------------------- |
| **Project Access Level Limit**         | The highest project access level they can give a member                             |
| **Project Request Access Level Limit** | The highest project request access level they can give a member                     |
| **Add User Method**                    | Whether they choose existing users from a drop-down list, or enter an email address |
| **Allow User Invite**                  | Whether they can invite new people to your AttackForge tenant                       |

{% hint style="info" %}
**Note:** Group Membership Admins can't see the projects, vulnerabilities, assets or attack chains linked to the group. They only see the group's details, such as its owner and primary contact, and its current members.
{% endhint %}

### Let admins invite new users

With **Allow User Invite** on, a Group Membership Admin can bring the right people into AttackForge quickly, without involving application administrators. This helps you:

* let customers invite their engineering teams straight to the right projects or groups
* let account managers manage their customer accounts
* share vulnerability information faster, so issues are fixed sooner

## Manage membership with SSO groups

On SSO-enabled tenants, you can link Identity Provider (IDP) or Active Directory (AD) groups to an AttackForge group. Members are then added to, and removed from, the AttackForge group and its projects automatically, based on their IDP or AD groups. This keeps project access in line with your enterprise's access control groups, and removes access people shouldn't have, at every login.

This is off by default. It's only turned on for a group when you link an IDP or AD group to it.

### How it works

1. When you create or edit a group, you can link one or more IDP or AD groups to it.
2. Once a group is linked, all of its membership is controlled through SSO.
3. When a user signs in with SSO, and their profile includes IDP or AD groups, AttackForge checks each AttackForge group that has linked IDP or AD groups.

| If one of the user's IDP or AD groups... | Then...                                                                                                               |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Matches a linked group**               | The user is added to the AttackForge group, if they're not already a member, with the access level set in the mapping |
| **Doesn't match any linked group**       | The user is removed from the AttackForge group, if they're a member                                                   |

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F77kHMmv1kgI7Wkzt5LAl%2FScreenshot%202026-11-10%20at%2011.52.45%E2%80%AFam.png?alt=media&amp;token=b1defe28-4086-49e2-8d5f-defb1d152334" alt=""><figcaption></figcaption></figure>

## Link groups to data

Linking a group to something gives every member access to it, at the level set for the group or for each member.

| Link a group to               | Where you set it                                | What members get                                        |
| ----------------------------- | ----------------------------------------------- | ------------------------------------------------------- |
| **Projects**                  | The project                                     | Access at their Project Access Level                    |
| **Project requests**          | The project request                             | Access at their Project Request Access Level            |
| **Assets**                    | Asset libraries, in the Administration module   | Access to the library's assets                          |
| **Writeups**                  | Writeup libraries, in the Administration module | Access to the library's writeups                        |
| **Portfolios**                | Portfolio settings                              | Dashboards for the portfolio or its streams             |
| **Custom fields**             | Custom field settings                           | View or edit access to the field                        |
| **Reports**                   | The `Report Templates` module                   | Access to download the report                           |
| **Flows**                     | The group's `Other Access`                      | Access to Flows                                         |
| **Actions**                   | The group's `Other Access`                      | Access to Actions shared with the group                 |
| **AI MCP**                    | The group's `Other Access`                      | Access to AttackForge through AI MCP                    |
| **Self-Service RESTful APIs** | The group's `Other Access`                      | Access to the RESTful API methods the group is given    |
| **Events**                    | The group's `Other Access`                      | Access to events, through Flows or the Self-Service API |

### Projects

Group members get access to the project at their own Project Access Level. Linking a group to a project means members:

* automatically get access to the project, at the access level set in the group
* can filter Analytics by the group
* see the project's data, including vulnerabilities, on their dashboards

See [Projects](https://support.attackforge.com/app/modules/projects.md).

### Project requests

Group members automatically get access to the project request, at their Project Request Access Level.

See [Projects](https://support.attackforge.com/app/modules/projects.md).

### Assets

Link groups to asset libraries in the Administration module. For example, to:

* let customers see or change their own assets
* let technology teams see the assets that belong to them
* let security teams manage the assets they're responsible for

See [Assets](https://support.attackforge.com/app/modules/assets.md).

### Writeups

Link groups to writeup libraries in the Administration module. For example, to:

* let technical writers work on the writeups they manage
* let pentesters see or change only the writeups they're allowed to
* let security teams control which writeup libraries internal and external teams can use

See [Writeups](https://support.attackforge.com/app/modules/writeups.md).

### Portfolios

Link groups to portfolios and streams in the portfolio settings. For example, to:

* let customers see dashboards for their whole portfolio
* let customers see dashboards for parts of their portfolio
* help teams track and manage compliance

Members only see data from projects they have access to on the portfolio or stream. See [Portfolios](https://support.attackforge.com/app/modules/portfolios).

### Custom fields

Link groups to custom fields in the custom field settings. For example, to:

* let customers see only the project and vulnerability data that relates to them
* let Red and Blue Teams see, but not change, each other's data during Purple Team assessments
* let security teams set up and use data on a need-to-know basis

Members can only see or change the custom fields their access allows. See [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms).

### Reports

Link groups to reports in the `Report Templates` module. For example, to:

* let customers see only the reports that relate to them
* create reports that only auditors can download
* let security teams create need-to-know reports for their team

Members only see the reports their access allows. See [Reporting](https://support.attackforge.com/app/getting-started/reporting).

### Flows

Give a group access to Flows in the group's `Other Access`. For example, to:

* let an automation team build and run Flows, without making them Administrators
* let a customer's team use Flows that connect AttackForge to their own tools

See [Getting access to Flows](https://support.attackforge.com/app/automations-and-integrations/flows#getting-access-to-flows).

### Actions

Give a group access to Actions in the group's `Other Access`. For example, to:

* share an Action with the team that needs it, such as a remediation team's "raise a ticket" Action
* keep Actions for one customer or team away from everyone else

See [Sharing Actions](https://support.attackforge.com/app/automations-and-integrations/actions#sharing-actions).

### AI MCP

Give a group access to AI MCP in the group's `Other Access`. For example, to:

* let testers use AI assistants and agents with AttackForge data
* limit AI access to the teams that are approved to use it

Members only see data they already have access to. See [User access to MCP](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills#user-access-to-mcp).

The Flows, Actions and AI MCP use cases are examples.&#x20;

### Self-Service RESTful APIs

Give a group access to Self-Service RESTful APIs in the group's `Other Access`. For example, to:

* let an integration team or service account use only the API methods it needs
* let a customer's team pull their own vulnerabilities into their ticketing system

Self-Service API access is off by default for everyone, including Administrators. Members also need their own API key. See [Self-Service RESTful API](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api).

### Events

Give a group access to events in the group's `Other Access`. Events can be received in two ways:

| Through                  | What it's for                                                                                             | Learn more                                                                                                                                         |
| ------------------------ | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Flows**                | Running a Flow automatically when something happens in AttackForge, such as a vulnerability being created | [Flows: internal events](https://support.attackforge.com/app/automations-and-integrations/flows#internal-events)                                   |
| **The Self-Service API** | Sending events to your own systems as they happen                                                         | [Self-Service Events API: getting started](https://support.attackforge.com/attackforge-enterprise/modules/self-service-events-api/getting-started) |

For example, to let a remediation team's integration hear about new vulnerabilities as soon as they're visible. These use cases are examples.

## Give groups other access

Administrators can also give a group's members access to:

* events through Flows
* events through the Self-Service API
* Self-Service RESTful APIs
* Flows
* Actions
* AI MCP

On the group, click `Other Access`.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F1cmH9jATKAVi8WBLN4mE%2FScreenshot%202026-11-10%20at%2012.00.26%E2%80%AFpm.png?alt=media&amp;token=7a0c2b00-99d7-487f-bd4a-920c7ce8041b" alt=""><figcaption></figcaption></figure>

| Access                                  | Learn more                                                                                                                                         |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Events through Flows**                | [Flows: internal events](https://support.attackforge.com/app/automations-and-integrations/flows#internal-events)                                   |
| **Events through the Self-Service API** | [Self-Service Events API: getting started](https://support.attackforge.com/attackforge-enterprise/modules/self-service-events-api/getting-started) |
| **Self-Service RESTful APIs**           | [Self-Service RESTful API](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api)                              |
| **Flows**                               | [Getting access to Flows](https://support.attackforge.com/app/automations-and-integrations/flows#getting-access-to-flows)                          |
| **Actions**                             | [Sharing Actions](https://support.attackforge.com/app/automations-and-integrations/actions#sharing-actions)                                        |
| **AI MCP**                              | [User access to MCP](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills#user-access-to-mcp)                        |

## Tips

* **Give access to groups, not individuals.** It's easier to keep right as people join, move and leave.
* **Create one group for each customer, vendor or team** that should only see its own data.
* **Turn on Auto Add Project Request for customer groups**, so their requests are visible to the right people straight away.
* **Set limits on Group Membership Admins.** Use the access level limits so they can't give more access than they should.
* **Use SSO groups where you can.** Access is added and removed at every login, so leavers lose access automatically.
* **Use custom field access for Purple Team assessments**, so Red and Blue Teams can see, but not change, each other's data.
* **Test with a member's account** after changing a group's access.

## FAQ

**Who can create groups?** Administrators. Only Administrators have full access to the Groups module.

**Do members get the same access on every project?** On the group's projects, each member gets access at their own Project Access Level, set when they're added to the group.

**Can Group Membership Admins see the group's projects?** No. They can't see the group's projects, vulnerabilities, assets or attack chains. They only see the group's details and its members.

**Can a Group Membership Admin give someone Edit access?** Only if their Project Access Level Limit allows it.

**Can Group Membership Admins invite new users?** Yes, if **Allow User Invite** is on.

**Is SSO group management on by default?** No. It's only turned on for a group when you link an IDP or AD group to it.

**What happens when someone leaves an IDP group?** At their next SSO login, they're removed from the linked AttackForge group.

**Will every member get project emails if Project Team Notifications is on?** Not always. It depends on the project's email settings and each member's notification preferences.

**Can a group get access to APIs, Flows, Actions and MCP?** Yes. Administrators set this in the group's `Other Access`.

## Related pages

* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)
* [Users](https://support.attackforge.com/app/modules/users)
* [Invite user to project](https://support.attackforge.com/app/getting-started/invite-user-to-project)
* [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project)
* [Portfolios](https://support.attackforge.com/app/modules/portfolios)
* [Custom fields and forms](https://support.attackforge.com/app/getting-started/custom-fields-and-forms)
* [Assets](https://support.attackforge.com/app/modules/assets.md)
* [Writeups](https://support.attackforge.com/app/modules/writeups.md)
* [Reporting](https://support.attackforge.com/app/getting-started/reporting)
* [Notifications](https://support.attackforge.com/app/getting-started/notifications)


---

# 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/modules/groups.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.
