> For the complete documentation index, see [llms.txt](https://docs.cleric.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cleric.ai/setup/providing-context.md).

# Providing Context

Provide documentation to improve investigations

Cleric can access documentation from multiple sources to understand your system architecture, operational procedures, and environment-specific context. Cleric references this context when planning investigations and interpreting results.

## Documentation via Integrations

Cleric can search and retrieve documentation during investigations using the [Atlassian](/integrations/supported-integrations.md#atlassian) and [GitHub](/integrations/supported-integrations.md#github) integrations.

Combined with [Memories](/learning/memories.md) that Cleric learns from your conversations, documentation integrations are a meaningful way to set up Cleric with a comprehensive understanding of your environment.

## Global Guidance

Global Guidance lets you provide preferences and context that apply to all investigations. Configure this from **Settings** in your Cleric dashboard.

Write guidance in plain text. Be direct and specific. Cleric references this context when planning and conducting investigations.

Use Global Guidance for preferences and tribal knowledge that isn't captured in Memories:

```
Always check for recent deployments first when investigating performance issues.

When investigating database issues, check the read replicas before the primary.

The checkout service depends on inventory-api and pricing-api. If checkout is slow, check those services first.

Our staging environment uses the naming pattern *-staging.

The payments-api service is owned by the payments team (#payments-oncall).
```