> ## 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.

# Your first day in Forge

> A safe tour of Chat, tickets, projects, and connected knowledge.

This tour helps you learn the shape of Forge without making an external change.

## Before you begin

You need a Forge user account and access to at least one customer workflow. The sections and tools available to you depend on your role and your organization's configuration.

<Steps>
  <Step title="Orient in the navigation">
    Open Forge and scan the main groups: **Helpdesk**, **Automations**, **Account Strategy**, and **General**. Common shortcuts such as **My Tickets** and **Chat** appear near the top.
  </Step>

  <Step title="Open a scoped Chat">
    Create a Chat and choose **Organization**, **Account**, **Ticket**, or **Project**. Pick a real item you recognize so you can judge whether the context is correct.
  </Step>

  <Step title="Stay in Ask mode">
    Ask Forge to summarize the situation, identify missing information, and suggest the next step. Ask mode is the right default while you learn because it is read-oriented.
  </Step>

  <Step title="Inspect a ticket or project">
    Open a ticket's **Plan**, **Activity**, and **Overview**, or a project's **Overview** and **Work Plan**. Notice how Chat stays connected to the work rather than starting from a blank prompt.
  </Step>

  <Step title="Find the evidence">
    Ask Forge which records or connected systems informed its answer. Check the source record before relying on a material detail.
  </Step>

  <Step title="Review before you write">
    If your role allows Full access, inspect the proposed action, target, and approval prompt before approving it. You can deny an approval and keep working in Chat.
  </Step>
</Steps>

## Useful first prompts

* “Summarize this item for a teammate taking over.”
* “What facts are confirmed, what is inferred, and what is still missing?”
* “What is the smallest safe next step?”
* “Which runbook or skill is relevant here?”
* “Show me the source for the most important claim.”

<Tip>
  Give the outcome, constraints, and audience—not just a command. “Draft a customer update that explains what we know, what we tried, and when we will update them next” is more useful than “write a reply.”
</Tip>

## If something is missing

A tool may be unavailable because the system is not connected, the account is not mapped, the tool is disabled for this surface, or your role does not include it. Ask an administrator to check [Systems and integrations](/administration/systems-and-integrations), [Availability and approvals](/administration/availability-and-approvals), and [Roles and permissions](/administration/roles-and-permissions).