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

# N3Auto Options

This page provides detailed configuration options for specific theme features, including Listings, User Dashboard, Login, Payments, and more.

| Group             | Source-verified important fields                                                                                                                                  |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| General           | Maximum gallery photos, allowed formats, maximum image size.                                                                                                      |
| Listing Archive   | Main/search layout, search width, desktop/tablet/mobile columns, result count, category slider.                                                                   |
| Listing Search    | Enable search, transmission, fuel, categories, price, sortable field order.                                                                                       |
| Listing Single    | Three layouts; gallery/video/images, compare, favorite, share, test drive, offer, finance, map, reviews, dealer card/chat, report, related and sortable sections. |
| Listing Submit    | Sortable frontend form sections.                                                                                                                                  |
| Dashboard         | Dealer/buyer navigation toggles/icons and base/section slugs.                                                                                                     |
| Compare           | Enable and compare slug.                                                                                                                                          |
| Currency          | Position, name, symbol, thousand/decimal separators, decimal count.                                                                                               |
| Map               | Type/style, API key, latitude, longitude, zoom.                                                                                                                   |
| Payment           | Bank, PayPal mode/credentials, WooCommerce switch.                                                                                                                |
| Login / Email     | Google; registration, password, package and message email templates.                                                                                              |
| Slug / Site modes | Listings/taxonomy URLs; Coming Soon and Maintenance page assignment.                                                                                              |

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FkzarRyiyhKxqg6a54lbb%2Fimage.png?alt=media&amp;token=6b6902b2-90dc-4b2b-aa25-279f66915be2" alt=""><figcaption></figcaption></figure>

### Coming Soon and Maintenance

After importing the demo, the **Coming Soon** and **Maintenance** pages should already be available under **WordPress Dashboard > Pages**.

To set them up:

* Go to **N3Auto Options > Coming Soon**
  * **Enable Coming Soon:** On
  * **Coming Soon Page:** Coming Soon
* Go to **N3Auto Options > Maintenance**
  * **Enable Maintenance Mode:** On
  * **Maintenance Page:** Maintenance Mode

If the **Coming Soon** or **Maintenance** pages are not available, you can create them manually:

Go to **WordPress Dashboard > Pages > Add New**, enter **Coming Soon** (or **Maintenance**) as the page title, then click **Publish**. Next, click **Edit with Elementor**, search for the **Coming Soon** (or **Maintenance**) widget, drag it into the page content area, customize the available settings and content, and click **Publish**.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FfPlzmPhb2Mwy17myMg32%2FScreenshot%202026-08-27%20161633.png?alt=media&amp;token=a4b2694c-7c6d-472a-8e8a-a249dd258b6e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FSuFms8KRXcbOVEGqxXg9%2FScreenshot%202026-08-27%20161953.png?alt=media&amp;token=76a9fd12-85e4-4033-83bc-605cf7f9f2e0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2F8TlR9nkdcmWRnuqBz7nx%2FScreenshot%202026-08-27%20162049.png?alt=media&amp;token=f311e01f-1554-480d-be92-7a37cf34e71c" alt=""><figcaption></figcaption></figure>

After that, assign the newly created page as the **Coming Soon** or **Maintenance** page by following the steps above.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2Fb0sAtfc10wu0jEgOf2d3%2Fimage.png?alt=media&amp;token=0347a435-d435-4655-9167-ab36a3a752e8" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FHkvnVM3ghnr80KUjMke9%2Fimage.png?alt=media&amp;token=e7270e50-8c9a-4f3c-8e80-175af79e17be" alt=""><figcaption></figcaption></figure>

### Compare

Compare: enable it, define a unique slug

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2Fm0ZdcuftfZ68IDDhaq5M%2Fimage.png?alt=media&amp;token=e626d677-842d-44e6-89cd-d15b7182661f" alt=""><figcaption></figcaption></figure>

### Single Listing

Choose the listing single detail layout: `layout-01`, `layout-02`, and `layout-03`

Sortable content and optional gallery, video, compare, favorite, share, test drive, offer, finance, map, reviews, dealer card/chat, report, and related listings are available.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2F7mx0WyeDmhWCoFLqIUUE%2Fimage.png?alt=media&amp;token=ab7e8e07-d6a8-47bc-b50c-ce00c965feef" alt=""><figcaption></figcaption></figure>

### Archive and Search

Choose archive/search layouts, search width, per-device columns, and listings per page.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2Fzhw25Ydb7k7kuuLBLnIk%2Fimage.png?alt=media&amp;token=4b1580d0-c85d-4ca2-8d83-e6f0b0464bc0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FMe6De1Frd9CpQGyEcHsV%2Fimage.png?alt=media&amp;token=a5b25ce1-1344-4dc6-9ee4-112918d7f410" alt=""><figcaption></figcaption></figure>

### Listing Submit <a href="#wp-settings-section-n3auto_opt7_section-7" id="wp-settings-section-n3auto_opt7_section-7"></a>

This is the setup within the listing submit section.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FyMXn6jelnERIA62i4dIh%2Fimage.png?alt=media&amp;token=4bc27d69-7e2c-457d-816e-a792a34a6774" alt=""><figcaption></figcaption></figure>

### Login and Email

#### Login&#x20;

* Enable Google.
* configure its API value.

Seyarat's Google Api field requires a Google OAuth 2.0 Web Client ID, for example `1234567890-example.apps.googleusercontent.com`. It does not require the Google Maps API key and the current login integration does not ask you to paste a Client Secret.

Do not paste a Client Secret

Only paste the Web Client ID into WordPress. Keep any Client Secret private and never place it in documentation, screenshots, source control, or support tickets.

#### Get a Google OAuth Client ID

1. Sign in to [Google Cloud Console](https://console.cloud.google.com/) using the account that should own the website integration.
2. Create a new project or select an existing project for this website. Use a clear name such as *Seyarat Production Login*.
3. Open [Google Auth Platform → Branding](https://console.developers.google.com/auth/branding). Enter the application name, support email, logo, authorized domain, homepage, privacy policy, and optional terms URL. These links should use the real HTTPS production domain.
4. Open Audience. Choose the audience suitable for the website. While testing an external app, add the Google accounts that may test login as Test users. Publish or complete verification when Google requires it before public use.
5. Open Data Access. For normal sign-in, use only the basic identity scopes needed by the integration, such as email/profile/openid. Do not request unrelated sensitive scopes.
6. Open [Google Auth Platform → Clients](https://console.developers.google.com/auth/clients) and click Create Client.
7. For Application type, select Web application. Enter a name such as *Seyarat Website*.
8. Under Authorized JavaScript origins, add the exact website origin: scheme plus hostname only, for example `https://example.com`. Add `https://www.example.com` separately when the site can use both hosts. Add staging as a separate origin.
9. For local testing, Google allows origins such as `http://localhost` and `http://localhost:8080`. Do not add localhost to the production website unless it is actually needed for development.
10. The verified Seyarat flow uses a JavaScript token callback and does not define a custom redirect endpoint, so leave Authorized redirect URIs empty unless a future plugin version or Google setup screen explicitly provides a required callback URL.
11. Click **Create**. Copy the complete Client ID ending in `.apps.googleusercontent.com`.

#### Enter the Client ID in WordPress

1. Open **WordPress Admin → N3Auto Options → Login Option → Login Social**.
2. Set **Enable Google** to **Enable**.
3. Paste the complete OAuth Web Client ID into Google Api. Do not add spaces, quotation marks, or a Client Secret.
4. Click **Save Changes** and clear WordPress, server, CDN, and browser caches.
5. Open a page containing the N3Auto Sign In or Sign Up widget in an incognito/private browser window.
6. Click Google, choose an allowed Google account, approve the requested basic profile access, and confirm that WordPress signs in or creates the expected account.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FAoWuDUUsTekVUbFg4FYj%2Fimage.png?alt=media&amp;token=10d1259d-be15-44de-8529-0b5dc12087c5" alt=""><figcaption></figcaption></figure>

#### Email

Configure Registered User (user/admin), Forgot Password, Activated Package, and Send Message templates. Preserve documented placeholders.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FwuwcFdJLVgXe6tFr85BK%2Fimage.png?alt=media&amp;token=4a652f05-7af5-4635-9eff-124f6bbbb4d5" alt=""><figcaption></figcaption></figure>

### Map

#### Open the Map settings

1. Sign in to WordPress as an administrator.
2. Open **N3Auto Options → Map Option**. If the submenu is not visible, open the **N3Auto Options** page and select **Map Option** in its left navigation.
3. Choose **Google Map, Map Box, or OpenStreetMap** in **Map Type**.
4. For **Mapbox**, choose **Streets**, **Light**, **Dark**, **Outdoors**, or **Satellite** in **Map Style**. The source default is Light.
5. Paste the provider credential into Key Api when that provider requires one. Follow the provider-specific instructions below.
6. Enter the default **Map Latitude** and **Map Longitude**. These coordinates are used as the initial map position when a listing does not provide a more specific location.
7. Set **Zoom Level** from 1 to 20. A lower value shows a larger region; a higher value shows streets or buildings more closely.
8. Click **Save Changes**, clear caches, and test the listing submission form, listing detail map, archive map, and Contact Map widget if used.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FDadIsS0E5m6YYsbAdlAD%2Fimage.png?alt=media&amp;token=ea05f0aa-a6ce-4f28-baff-6421559fae76" alt=""><figcaption></figcaption></figure>

### Currency

Set position, name, symbol, separators, and decimals. Verify cards, singles, filters, packages, orders, emails, and gateways. This does not convert exchange rates.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2Fs6ZnCeur5yN0sfFpV8Li%2Fimage.png?alt=media&amp;token=174e3cd2-fb60-4938-9ead-f26620e67a35" alt=""><figcaption></figcaption></figure>

### Slugs

This is the setup within the Slug Options section. Configure listings/taxonomies, compare, dashboard base and account sections.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2F1s8iH87M6KeedFSj5BLa%2Fimage.png?alt=media&amp;token=4e239054-5599-435f-891c-3e8ee1fbf054" alt=""><figcaption></figcaption></figure>

### Payments

#### - Bank Transfer

Enable it and enter bank/account details and instructions; staff manually verify and activate.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FWgcwGstNhlR8I90BdGDR%2Fimage.png?alt=media&amp;token=3a8b8a7c-1b2b-4867-b109-130850865298" alt=""><figcaption></figcaption></figure>

#### - PayPal

Choose mode and matching Client ID/Secret. Begin in sandbox.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FB4eqD4wAbW0EhERYPvW6%2Fimage.png?alt=media&amp;token=30747c9e-ad3d-4a6d-93d6-1722eda0c868" alt=""><figcaption></figcaption></figure>

#### - WooCommerce

Enable after configuring WooCommerce and a compatible gateway.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FtWVALsTapbJb2w8OuY71%2Fimage.png?alt=media&amp;token=861ce8d8-06c3-4a55-bfcb-627fd4aca24a" alt=""><figcaption></figcaption></figure>

### Dashboard Option

This page configures the **Dashboard URL slugs used by dealer accounts**, the **Dashboard URL slugs used by buyer accounts**, and the **Dashboard navigation used by buyer accounts**.

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FUs2BweQyhVQOCqHi3O2d%2Fimage.png?alt=media&amp;token=b2fbade3-75d4-4eac-bbed-6c6978bbc60a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FnANc9asW60MFEwcWy5cp%2Fimage.png?alt=media&amp;token=2874b310-3c90-477d-9a5a-306dbc2c2017" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://seyarat.gitbook.io/seyarat-docs/configuration/n3auto-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.