> ## Documentation Index
> Fetch the complete documentation index at: https://akron-cdb9eaf4.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> Akron configuration workflow, import and export, and safety defaults for first use.

Akron configuration is organized around the overlay, setup packs, and feature-specific options. Configure the visible setup first, then tune individual tool options.

## Configuration Order

<Steps>
  <Step title="Open the overlay">
    Use Akron's overlay as the main player-facing control surface. Confirm the current status and active tools before changing individual options.
  </Step>

  <Step title="Confirm the current policy state">
    Check the visible policy and status state before enabling features. The status indicates whether features are allowed, blocked, or would escalate the attempt status.
  </Step>

  <Step title="Set overlay behavior">
    Configure overlay scale, opacity, pause behavior, search behavior, and visual defaults so the UI is usable in your setup.
  </Step>

  <Step title="Enable specific tools">
    Enable only the tools needed for the current workflow. Keep state-changing features out of submitted-run setups.
  </Step>

  <Step title="Export a backup">
    Export a `.akr` backup once the setup is stable, especially before sharing settings or experimenting with attempt-changing features.
  </Step>
</Steps>

## Import and Export

Use `.akr` files for backup and sharing. You can export the whole Akron setup or a scoped section such as StartPos, keybinds, Auto Kill, Auto Deafen, recorder settings, audio settings, or HUD settings.

See [Import and export .akr packs](/akr-packs/import-export) for the workflow and [Akron .akr archives](/reference/akr-archives) for the reference contract.

## Safety Defaults

Keep these defaults unless you know why you need a different setup:

* Keep submission-oriented workflows in explicit proof-specific setups.
* Keep StartPos restore, warps, hitboxes, entity inspection, and timescale inside explicit room-lab or testing setups.
* Export a `.akr` backup before importing community packs.
* Treat Cheat feature use as attempt-changing even if the feature is later disabled.