> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/implementation/portal-configuration/portal-setup.md).

# Portal Setup

### Core configuration areas

A typical Submit portal setup includes the following settings.

#### Portal URL

The base URL customers will use to access the submission interface.

#### Accepted file types

Which file formats the portal accepts for upload.

This may be:

* PDF only
* PDF plus selected source formats that are converted before preflight

#### Maximum file size

The largest file size the portal will accept.

This should be aligned with the effective limits of the wider processing setup.

#### Default preflight profile

The profile used for the quick check during upload.

This should be lightweight and designed for fast customer feedback.

#### Production preflight profile

The profile used after submission for the full production check.

This is typically more comprehensive and may include corrections.

#### Editing capabilities

Which customer-side adjustment actions are enabled, such as:

* scale
* rotate
* mirror
* move

#### Proof page template

The process plan or template used to generate proof pages after successful processing.

### Practical advice

Keep the initial setup simple:

* start with a small set of accepted file types
* keep upload-stage checks fast
* enable only the editing capabilities customers genuinely need
* test proof output early with real product metadata

### Next steps

* Go to **Branding and Language**
* Go to **API Integration**
* Go to **Preflight Configuration**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.atomyx.io/atomyx-submit/implementation/portal-configuration/portal-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.