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

# Require clients to sign contracts before viewing

> Require clients to sign your contract before they can view photos or download a delivery package.

Contracts let you attach a legally binding agreement to any project and require your client to sign it before they can view photos or download their delivery. Once a client signs, you see confirmation in the project,and you can revoke the requirement at any time without losing the signed record.

Contracts are available on the **Beta**, **Studio**, and **Agency** plans.

## Set up a contract template

Before attaching a contract to a project, create the contract text you want to reuse. Shootbin stores these per-account so you can apply the same agreement across many projects.

<Steps>
  <Step title="Open your profile contracts">
    Go to **Profile → Studio** and scroll to the **Contracts** section. This is where you manage reusable contract templates for your account.
  </Step>

  <Step title="Create a new contract">
    Click **Add contract**, give it a name, and paste or write the contract text. Shootbin includes a few starter templates (paid shoot, TFP model release, expense reimbursement) that you can use as a starting point.
  </Step>

  <Step title="Save the contract">
    Save the contract. It's now available to attach to any project.
  </Step>
</Steps>

<Tip>
  Use descriptive names like "Commercial Usage Agreement 2025" or "Wedding Photography Contract" so you can tell them apart when attaching to projects.
</Tip>

## Attach a contract to a project

<Steps>
  <Step title="Open the project contracts page">
    Inside a project, navigate to **Contracts** in the project sidebar.
  </Step>

  <Step title="Choose your contract">
    Select **Use a saved contract** and pick the contract you created in your profile. A live preview of the contract text appears on the right side of the page.
  </Step>

  <Step title="Set signing requirements">
    Choose when a signature is required:

    * **Require signed contract before viewing**, the client must sign before they can open the project at all.
    * **Require signed contract before downloading delivery**, the client must sign before they can download the delivery package.

    You can enable one or both options depending on your workflow.
  </Step>

  <Step title="Save the contract selection">
    Click **Save contract selection**. Shootbin will ask you to confirm the change before applying it, so you have a chance to review the settings.
  </Step>
</Steps>

<Warning>
  Once you save a contract requirement, any client who hasn't yet signed will be prompted to sign the next time they visit the project. Make sure your contract text is final before enabling the requirement.
</Warning>

## How the client signing flow works

When a contract is required and a client visits the project, they are shown the contract and must sign it before accessing the project content.

<Steps>
  <Step title="Client reaches the contract prompt">
    The client sees a prompt explaining that they need to sign a contract before proceeding. The purpose shown (viewing or downloading) matches whichever requirement was enabled.
  </Step>

  <Step title="Client reads the contract">
    The full contract text is displayed in a scrollable panel. The client must scroll through and check the acceptance checkbox before the sign button becomes active.
  </Step>

  <Step title="Client signs or refuses">
    The client can either sign the contract or refuse it.

    * **Signing** records a digital signature and immediately grants access to the project.
    * **Refusing** blocks access. The client will see the contract prompt again if they return.
  </Step>
</Steps>

<Note>
  Guest-role members cannot sign contracts. If a guest visits a project with a contract requirement, they will see a message explaining they cannot proceed and will be redirected to their dashboard.
</Note>

## Check signature status

After a client signs, the Contracts page for that project shows a green confirmation card. You can see at a glance that the requirement is fulfilled.

If no one has signed yet and a contract requirement is active, the page shows an amber warning card so you know the requirement is active but no signature has been recorded.

## Revoke contract requirements

If you want to remove the signing requirement,for example, after a project review is complete,you can revoke requirements without losing the signature record.

<Steps>
  <Step title="Open the project contracts page">
    Navigate to **Contracts** inside the project.
  </Step>

  <Step title="Revoke requirements">
    Click **Revoke requirements**. This removes the signing requirement so clients can access the project freely.
  </Step>
</Steps>

<Info>
  Revoking requirements does not delete the existing signature. The signed record is retained and still visible on the Contracts page.
</Info>

## Contract settings summary

<CardGroup cols={2}>
  <Card title="Require for viewing" icon="eye">
    Client must sign before they can open the project and see any photos.
  </Card>

  <Card title="Require for download" icon="download">
    Client must sign before they can download the delivery package.
  </Card>

  <Card title="Saved contract templates" icon="file-text">
    Create reusable contracts in **Profile → Studio → Contracts** and apply them to any project.
  </Card>

  <Card title="Revoke without losing data" icon="shield-off">
    Remove the signing requirement at any time. The signature record is always preserved.
  </Card>
</CardGroup>