> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mindfort.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Targets

> Learn how to add and verify Web Application, API, and available Network targets, then manage credentials, scope, and target details.

## Add a Target

<Note>
  Only organization admins can add targets.
</Note>

1. Go to **Target Inventory**.
2. Select **Add Target** and choose the target type.
3. Enter the required target name, address, and description.
4. Optionally configure authentication.
5. Review the configuration and complete the applicable verification step.

The guided flow covers **Target Type**, **Target Details**, **Authentication**, **Review**, and **Verify Target**.

### Target URLs with a path

Include a path when it is part of the application or API address you want tested, such as `https://app.example.com/portal` or `https://api.example.com/v1`. Review the target's [scope and guardrails](/guides/scope-and-guardrails) to specify included and excluded areas.

## Verify a Web Application or API

1. Open target details.
2. Go to the DNS section.
3. Copy the TXT verification token.
4. Add it in your DNS provider.
5. Return and run **Verify**.

A target must be verified before it can be assessed.

## Network Targets

When Network targets are available for your organization, enter the authorized IP address. Network targets do not use DNS verification or stored credentials. After creating one, select **Contact Support** on the target to request approval before running an assessment.

## Manage Target Details

From the target detail page, you can:

* edit target name and description
* edit login instructions
* add, edit, and delete stored credentials
* add, edit, and delete target values (key-value context fields)
* review verification state

## Target Scope

Target details define the default testing scope for assessments and Agents. Keep the target address, login instructions, credentials, and target values current so the authorized boundary is clear.

Use target values for context that is required to stay in scope, such as:

* tenant slug
* organization ID
* workspace ID
* environment name
* account number
* required environment setting or region selector

Document any included or excluded areas before launching a run. For detailed scope and guardrail guidance, see [Scope and Guardrails](/guides/scope-and-guardrails).

## Credentials in Target Details

In **Stored Credentials**, you can:

* add new credentials
* edit existing credentials
* remove credentials

Use dedicated test credentials only.

## Login Instructions

In **Login Instructions**, document the exact login path to help MindFort agents authenticate and test areas behind login.

## Delete Target

Use **Delete Target** only when you intentionally want to remove this target from active use.

## Link source repositories

White-box assessments and patching use repositories associated with the target.

1. Connect GitHub in **Settings > Integrations** and grant access to the repository.
2. Open the target in **Target Inventory**.
3. Find **Associated Code Repositories**.
4. Select the repository, branch, and folder. Use `/` for the repository root.
5. Select **Add**.

Keep the linked branch and folder aligned with the application you intend to assess. Repository access depends on the GitHub App installation and your organization permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.