> 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/project-workspace.md).

# Project Workspace

## Overview

Every project in AttackForge has a dedicated workspace where notes can be entered and files can be uploaded. The workspace allows project teams to consolidate all entry criteria required for an assessment, and place to store testing logs once the assessment has completed.

You can access the workspace from the project menu by clicking on `Workspace`.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FKcixXPFALhZLfQzNQQRl%2FScreenshot%202024-06-19%20at%209.12.08%E2%80%AFPM.png?alt=media&amp;token=4c589e3f-8de5-4f77-9d2b-5b386ee6609f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fo7h06to8yASYv7OGfOOe%2FScreenshot%202024-06-19%20at%209.12.16%E2%80%AFPM.png?alt=media&amp;token=c0739b0c-fd57-467f-a09c-3da8fbdc0b0e" alt=""><figcaption></figcaption></figure>

Only users with `Upload` or `Edit` permissions on a project can access the workspace.&#x20;

Edit users can see all uploaded files & notes. Upload users can only see the uploaded files.

Authorized users can create free-form notes in the workspace, which are relevant to the assessment.

For example:

* Test credentials
* Link's to solution interfaces or API specifications
* Notes relating to system functionality
* Steps on how to extract & set up solution
* Etc.&#x20;

You can assign each of the notes to project scope assets and also upload files directly to the notes.

Authorized users can also upload files to the project workspace and testing logs section.&#x20;

For example:

* Binaries for mobile applications
* API test harnesses
* Solution design and architectural documentation
* Codebase for source code review
* Etc.


---

# 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/project-workspace.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.