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

# Scopes, modes, and tools

> Control Chat context and understand when Forge can read, write, or request approval.

Chat combines three decisions: **what the conversation is about**, **which tools your role can use**, and **whether this session is read-oriented or can write**.

## Scope the conversation

Choose the narrowest scope that contains the work:

| Scope        | Best for                                                             |
| ------------ | -------------------------------------------------------------------- |
| Organization | Cross-account operations, policy, and shared knowledge.              |
| Account      | Customer-specific systems, service history, strategy, and reporting. |
| Ticket       | Investigation, Action Plans, notes, communication, and resolution.   |
| Project      | Scoping, work plans, delivery questions, project records, and tasks. |

Changing scope returns the conversation to Ask mode. Verify the scope shown in the workspace before requesting a material action.

## Choose a mode

<Tabs>
  <Tab title="Ask mode">
    Ask mode is read-oriented. It exposes only tools allowed for read work. If a protected read needs approval, Forge can still present an approval request.
  </Tab>

  <Tab title="Full access">
    Full access can expose both read and write tools allowed by your role and the current surface. It does not override role permissions, Availability, connection state, or provider support.
  </Tab>
</Tabs>

## Review approvals

Some interactive tools are configured to require a fresh decision. When Chat pauses:

<Steps>
  <Step title="Read the request">
    Confirm the system, tool, intended target, and effect.
  </Step>

  <Step title="Check the conversation">
    Make sure the proposed call matches what you asked Forge to do.
  </Step>

  <Step title="Approve or deny">
    Approval allows that specific call. Denying it does not end the conversation; explain the safer alternative and continue.
  </Step>
</Steps>

Several requests can be pending at once. Review each one separately.

## Why a tool may not appear

A system must be connected, available in the current scope, enabled for Chat, and allowed by your role. Account-scoped tools may also need a valid account mapping. The tools shown in Chat are the intersection of those controls.

<Warning>
  Approval policies apply to interactive work. Background surfaces such as Custom Agents use Availability because no person is present to answer an approval prompt.
</Warning>

Administrators can configure these boundaries in [Systems and integrations](/administration/systems-and-integrations), [Availability and approvals](/administration/availability-and-approvals), and [Roles and permissions](/administration/roles-and-permissions).