# Supplier submissions

> Invite suppliers to submit AGS data, have it auto-vetted against your rules, then review and import it.

Where [sharing with clients](/manage/sharing-with-clients) sends a project *out* to
external contacts, **supplier submissions** bring data *in*. You invite a supplier -
a driller or lab - to upload AGS through [Connect](/connect/submitting-data); it is
automatically checked against your rules; and it lands in a review queue for you to
accept straight into the project.

You run all of this from a project's **Connect** area, which has three segments:
**Recipients** (clients you share with), **Suppliers** (who can submit) and
**Submissions** (the review queue). The **Submissions** tab shows a badge with the
number of submissions waiting for you.

## Invite a supplier

In the **Suppliers** tab, choose to invite a supplier and enter their **name** and
**email**. They receive an email to set up a Connect account and can then submit
data to this project. You can also set which ruleset their submissions are checked
against - see below.

Manage each supplier over time much like a client: edit them, revoke and restore
access, and see their activity.

## Project rules

Submissions are vetted against an **acceptance ruleset** - the same rules layer
called **Project rules**. The rules themselves are authored once per configuration
in [Product OS](/product-os/configurations/rulesets); here you choose which one a
project uses.

- **Project default** - set on the project itself (in the project's
  **create**/**edit** dialog), or from the **Suppliers** tab. A project inherits
  the configuration default until you pick a specific ruleset or **None**.
- **Per-supplier override** - when inviting or editing a supplier, you can give
  that supplier a different ruleset, or none, just for their submissions.

<Callout type="note" title="What an error means for a supplier">
  In a ruleset, **Error** rules block a supplier's submission until fixed;
  **Warning** and **Info** are advisory. Severities are set per rule in Product OS.
</Callout>

## The review queue

The **Submissions** tab lists every submission with its status:

| Status | Meaning |
| --- | --- |
| **Submitted** | The supplier has sent it; waiting for review. |
| **Under review** | You have opened it to review. |
| **Changes requested** | You asked for changes; the supplier can resubmit a new version. |
| **Accepted** | You accepted it and imported the data. |
| **Rejected** | You declined it. |

## Review a submission

Open a submission to see its **files**, the full **vetting report**, and a
**message thread** with the supplier. The report groups findings into three layers:

- **AGS format** - is the file valid AGS (structure + the BGS validator)?
- **Validation engine** - advisory geotechnical and data-quality checks.
- **Project rules** - your acceptance ruleset.

From here you have three actions:

- **Request changes** - send the submission back with a note saying what to fix. The
  supplier resubmits a new version, which is re-vetted.
- **Reject** - decline the submission.
- **Accept & import** - bring the data into the project.

## Accept and import

**Accept & import** hands the submission's files straight to the normal Manage
[import wizard](/manage/importing-data), pre-loaded - so you pick locations and
tables, review the import plan, and run it exactly as you would for your own files.
The submission is marked **Accepted** once the import is created.

<Callout type="note" title="Everyone stays in the loop">
  Submitting, requesting changes, accepting and rejecting all send an email - to
  your team when a supplier submits, and to the supplier when you respond - so
  nobody has to keep checking the queue.
</Callout>