Skip to main content
No. Forge is the AI work surface for context, reasoning, controlled action, and review. The PSA remains authoritative for provider-backed ticket, project, time, billing, assignment, and administrative records.
Navigation depends on your organization rollout and role. Ask an administrator to check the feature permission and whether that product area is enabled.
The system and tool must be valid for the current scope, connected, enabled for Chat, and allowed by your role. Account-scoped tools may also require an account mapping.
Ask mode is read-oriented. Full access can expose allowed write tools. Neither mode bypasses role permissions, system access, tool access, Availability, provider support, or configured interactive approvals.
No. Interactive approval prompts require a person to respond. Configure Custom Agent, Helpdesk, or other unattended tool access with Availability and the underlying role and tool controls.
That tool call does not proceed. The Chat remains available, so you can explain a safer alternative, change the request, or continue with read-only work.
No. It proves the configured workflow reached a successful terminal state. Review the source evidence, output, judge results, and any external writeback before relying on a material conclusion.
A runbook is a helpdesk procedure and can participate in AI Engineer eligibility. A skill is reusable guidance for a defined task across supported Forge surfaces.
No. Approval changes the proposal’s Forge review state. Complete the actual external action through the appropriate supported workflow, then record completion.
Confirm organization and account scope, check connection and sync health, compare the source provider, and refresh the supported sync. Do not make a material decision from a visibly stale record.
Use the Forge Audit Log for supported terminal write outcomes, then verify the result and provider audit history in the authoritative connected system.
Use several representative dry runs, including missing data, conflicting sources, provider failure, and a condition that should produce no action. Activate only after the workflow owner accepts the behavior and an administrator confirms Availability.