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

# Quickstart

> Connect a source, run your first scan, act on the first findings.

<Steps>
  <Step title="Create your organization and invite your team">
    Everything in Amnify belongs to an organization. See [Users and organization](/getting-started/organization).
  </Step>

  <Step title="Connect a source">
    A GitHub organization, an AWS account, an Azure tenant or a GCP connection. Cloud access is read only. GitHub also needs write, bounded to opening pull requests on new branches.

    Exact permissions per provider: [Azure](/connect/permissions/azure), [AWS](/connect/permissions/aws), [GCP](/connect/permissions/gcp), [GitHub](/connect/permissions/github).
  </Step>

  <Step title="Select your scopes">
    Everything arrives selected. Deselect anything Amnify should leave alone, then save.
  </Step>

  <Step title="Run the first scan">
    Amnify covers every selected scope and writes findings. Nothing is needed from you while it runs.
  </Step>
</Steps>

## Your first week

<CardGroup cols={2}>
  <Card title="Answer the open questions" icon="circle-question" href="/knowledge/context">
    The highest leverage thing you can do. It changes every future triage.
  </Card>

  <Card title="Upload your policies" icon="file-text" href="/knowledge/context">
    Questions then arrive pre-filled from what your organization already decided.
  </Card>

  <Card title="Turn on pull request review" icon="code-pull-request" href="/scanning/automation">
    So new code is checked before it merges.
  </Card>

  <Card title="Set a scan schedule" icon="calendar-clock" href="/scanning/automation">
    Per scope, plus free hourly dependency monitoring.
  </Card>
</CardGroup>