> 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/manage-user.md).

# User Settings

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

Your user settings let you look after your own account: your profile, password and security, API key, email notifications, and how AttackForge looks and behaves for you. Open them from your **user menu**.

Your settings cover who you are, how you keep your account and integrations secure, and how you work. Notifications let you choose single emails for each event, or a daily or weekly summary.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F40FImf8nTJ6W80RjSERz%2Fuser-settings-at-a-glance.svg?alt=media&amp;token=9f754c75-cb7f-49d9-b627-01e74bdee5e7" alt=""><figcaption></figcaption></figure>

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

* **Stay secure.** Keep your password and two-factor authentication up to date, and manage your API key.
* **Get the emails that matter to you.** Choose which project emails you receive, and get a daily or weekly summary instead of lots of single emails.
* **Work your way.** Choose your landing page, theme and custom views.
* **Keep integrations safe.** Store passwords and API keys as secrets, so they can be rotated in one place.

## Settings at a glance <a href="#settings-at-a-glance" id="settings-at-a-glance"></a>

| Area                 | Use it to                                                                     |
| -------------------- | ----------------------------------------------------------------------------- |
| **Profile**          | Update your profile information                                               |
| **Account settings** | Change your account details                                                   |
| **Secrets**          | Store passwords and API keys, and share them                                  |
| **User API key**     | Get or regenerate your API key                                                |
| **Notifications**    | Choose which project emails you receive, and set up daily or weekly summaries |
| **Preferences**      | Choose your landing page and theme                                            |
| **Custom views**     | Set how each table looks for you, and revisit it with one click               |

## Update your profile <a href="#update-your-profile" id="update-your-profile"></a>

Open **Profile** from your user menu, and update your profile information.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F591p5Uf6gg7CpK8Fnv4f%2FScreenshot%202026-11-06%20at%204.42.04%E2%80%AFpm.png?alt=media&amp;token=d116222b-5d3a-4b4a-a625-5d92f9690807" alt=""><figcaption></figcaption></figure>

## Update your account settings <a href="#update-your-account-settings" id="update-your-account-settings"></a>

Use **Account settings** to change your account details, such as your password and two-factor authentication.

{% hint style="info" %}
**Note:** Administrators see more account details than other users.
{% endhint %}

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FgjshsDx9SfjziRorMTPx%2FScreenshot%202026-11-06%20at%204.43.08%E2%80%AFpm.png?alt=media&amp;token=324a35c9-3b34-4814-9ad2-157d50c43690" alt=""><figcaption></figcaption></figure>

## Store secrets <a href="#store-secrets" id="store-secrets"></a>

Secrets are confidential items, such as passwords and API keys. Storing them as secrets means you can rotate a password or key in one place, and everything that uses it is updated.

* Only the person who created a secret can create it and view it.
* You can share a secret with other users if you need to.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fm80J49YFYmI2hWlPFfef%2FScreenshot%202026-11-06%20at%204.44.02%E2%80%AFpm.png?alt=media&amp;token=b6b86190-894a-4ba5-af80-2c89f3bca8f4" alt=""><figcaption></figcaption></figure>

### Your user API key <a href="#your-user-api-key" id="your-user-api-key"></a>

Each user has one API key. It's static and doesn't expire. Use it with:

* the [Self-Service RESTful API](https://support.attackforge.com/app/modules/self-service-restful-api)
* the [Self-Service Events API](https://support.attackforge.com/app/modules/self-service-events-api)
* [HTTP Trigger Flows](https://support.attackforge.com/app/modules/flows#external-events)
* [Local MCP](https://support.attackforge.com/app/automations-and-integrations/ai-mcp-and-skills#configuring-local-mcp)

You can regenerate your key at any time, for example if it may have been exposed.

{% hint style="info" %}
**Note:** Your key only works with the APIs and endpoints an Administrator has given you access to. No one has API access by default. See [Users](https://support.attackforge.com/app/modules/users).
{% endhint %}

## Choose your email notifications <a href="#choose-your-email-notifications" id="choose-your-email-notifications"></a>

Use **Notifications** to choose which emails you receive.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FAMVurYsfqA3jwqeaY8Lh%2FScreenshot%202026-11-06%20at%204.46.17%E2%80%AFpm.png?alt=media&amp;token=14d35d58-2f2e-4b33-8a3a-b31fc15512a3" alt=""><figcaption></figcaption></figure>

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

Project update emails keep you informed as a project moves through its lifecycle. You'll receive them when all three of these are true:

1. You're on the project team, either directly or through a group that has email turned on.
2. Project emails are turned on for the project.
3. You haven't turned them off in the project's settings.

Administrators and Project Coordinators can also make specific emails required on a project.

You can choose:

| Option                   | You're emailed when                                                                        |
| ------------------------ | ------------------------------------------------------------------------------------------ |
| **No emails**            | Never                                                                                      |
| **All emails**           | Any of the events below happens                                                            |
| **Daily testing**        | Testing starts or stops each day                                                           |
| **New vulnerabilities**  | A new Critical, High, Medium, Low or Info vulnerability is found. Choose which priorities. |
| **Vulnerability status** | A vulnerability is ready for retesting, re-opened or closed                                |
| **Project role**         | Your role on the project changes                                                           |
| **On hold**              | The project is put on hold, or taken off hold                                              |
| **Retesting**            | A retest is completed                                                                      |

### Daily and weekly project updates <a href="#daily-and-weekly-project-updates" id="daily-and-weekly-project-updates"></a>

Instead of an email for every event, get a regular summary of activity across all your projects.

|                          | Daily project update | Weekly project update                       |
| ------------------------ | -------------------- | ------------------------------------------- |
| **Covers**               | The last 24 hours    | The last 7 days                             |
| **Turned on by default** | No                   | No                                          |
| **When it's sent**       | The hour you choose  | The day of the week and the hour you choose |

Both summaries include:

* vulnerabilities found, by priority
* vulnerabilities closed
* vulnerabilities ready for retesting
* projects in progress, completed and overrun
* projects starting in the next 7 days

The hour is based on your tenant's time zone.

## Set your preferences <a href="#set-your-preferences" id="set-your-preferences"></a>

Use **Preferences** to choose:

* your **landing page**: the page you see after you sign in
* your **theme:** the theme options

## Set up your custom views <a href="#set-up-your-tables" id="set-up-your-tables"></a>

**Views** save the way you've set up a table, so you can get back to it in one click instead of setting it up again each time.

Views belong to the table you create them on. You can name them, give them advanced filters, put them in the order you like, and duplicate them.

Set up a table, save it as a view, and open it again in one click. Personal and cross-table views are only visible to you. System views are shared by Administrators with the roles, groups and users who need them. See [Custom views](https://support.attackforge.com/app/getting-started/custom-views).

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

* **Turn on the daily or weekly project update** if you're on many projects. You'll get one summary instead of lots of single emails.
* **Only choose the new vulnerability emails you need**, such as Critical and High.
* **Regenerate your API key straight away** if you think it may have been exposed.
* **Store passwords and keys as secrets**, never in Flows or scripts.
* **Set your landing page** to the page you use most.

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

**Why am I not getting project emails?** You'll only receive them if you're on the project team (directly, or through a group with email turned on), project emails are turned on, and you haven't turned them off in the project's settings.

**Can I turn off an email that's required on a project?** Administrators and Project Coordinators can make specific emails required on a project.

**Are the daily and weekly updates on by default?** No. Turn them on in Notifications, and choose when they're sent.

**Does my API key expire?** No. It's static, but you can regenerate it at any time.

**Can other people see my secrets?** Only if you share them with them.

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

* [Users](https://support.attackforge.com/app/modules/users)
* [Notifications](https://support.attackforge.com/app/getting-started/notifications)
* [Custom views](https://support.attackforge.com/app/getting-started/custom-views)
* [Working with service accounts](https://support.attackforge.com/app/getting-started/working-with-service-accounts)
* [Flows](https://support.attackforge.com/app/modules/flows)


---

# 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/manage-user.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.
