# Information To Send Us

## Tenant Details

| Field            | Example                               |
| ---------------- | ------------------------------------- |
| Tenant name      | Acme Network                          |
| Site name        | Acme Creator Network                  |
| Site description | Creator partnerships for Acme brands. |
| Logo URL         | `https://cdn.example.com/logo.png`    |
| Favicon URL      | `https://cdn.example.com/favicon.ico` |

Logo and favicon URLs must be public HTTPS URLs.

## Domains

| Field       | Example       |
| ----------- | ------------- |
| Root domain | `example.com` |

We will configure the app, API, admin, and `www` hostnames from this root domain.

Tell us if any hostname under this domain is already used by another service.

## DNS Provider

Send:

* DNS provider name, such as Cloudflare, Route53, GoDaddy, Namecheap, or Squarespace.
* Whether Cloudflare proxying is enabled, if you use Cloudflare.
* Whether your provider supports root-domain `ALIAS`, `ANAME`, or flattened CNAME records, if you know.

## Email

Send:

* General email domain.
* Email provider name.
* Whether the required sender addresses are mailboxes or aliases.
* Whether your provider supports SMTP login, app passwords, or OAuth, if you know.

Required sender addresses:

* `team@<generalEmailDomain>`
* `noreply@<generalEmailDomain>`
* `auth@<generalEmailDomain>`

Using one email domain is the simplest setup. If your team requires a separate auth email domain, tell us and we will coordinate it.

## Landing Page

Send one public HTTPS landing page URL.

The landing page can live on your root domain, `www`, a subdomain, Framer, Webflow, or another public HTTPS URL. The login buttons must point to the tenant root domain we configure for you.

Configure the landing page buttons as:

| Button               | URL                                          |
| -------------------- | -------------------------------------------- |
| Brand login/signup   | `https://<rootDomain>/continue?role=brand`   |
| Creator login/signup | `https://<rootDomain>/continue?role=creator` |

## Discord

Discord account linking is used for creator verification before creators submit posts. This does not require your own Discord server.

If you want Discord community links shown in your tenant, send your public Discord invite URL, for example:

| Field              | Example                      |
| ------------------ | ---------------------------- |
| Discord invite URL | `https://discord.gg/example` |

If you do not send a Discord invite URL, Discord community links will stay hidden in your tenant.

Automated Discord server membership checks, role grants, or private campaign channels require additional setup. For those features, our bot must be added to your Discord server and we will coordinate the required server and role details separately.

## Legal and Admin

Send:

* Legal entity name.
* Registered address.
* Contact address, if different from registered address.
* Governing state or jurisdiction.
* First admin email.
* Signup notification recipients.


---

# Agent Instructions: 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.anwhitelist.com/information-we-need.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.