---
title: "Run more than one help center site"
description: "Create sites with their own address, appearance, access and collections, while writing articles once."
url: https://help.gleap.ai/it/articles/16752002-run-more-than-one-help-center-site
collection: "Help center"
updated: 2026-11-01
language: it
alternates: [en]
---

# Run more than one help center site

Create sites with their own address, appearance, access and collections, while writing articles once.

A project can have several help center sites, subject to its plan’s site limit. Each site has its own address, appearance, access and collections. Articles are written once; a collection belongs to one site.

Open **Settings → Help center → Sites** to see the sites and the limit for your plan.

### Add a site

1.  Choose **New site**.
    
2.  Enter its name and available address.
    
3.  Choose **A copy of your help center** or **A clean start**.
    
4.  Choose the layout, then **Create site**.
    

![Help center sites screen in the Pied Piper demo project.](https://staticfiles.gleap.io/p613b5dd730aed737108f87ab/8j2AWVJJK04aSlROsBOtUyRNw06mqYjPD3vnY0Xc0NJNKmBADtwpAkSMCSDSQzx6twoukjALLF6.png)

Copying the starting configuration does not create a permanent link between the sites’ settings. After creation, changes are made on the new site’s own page.

### Configure the site

Open its row to see **General**, **Appearance**, **Collections, API reference, AI and search**, **Translations** and **SEO & custom code**.

Set the address and access for that site, then configure its look and search settings. Check which site is selected before changing a domain or access rule.

### Put collections on the right site

On the site’s **Collections** tab, move the top-level collections it should contain. Moving a collection also moves its subcollections and articles. Old links redirect.

Moving content changes where it is served. Check the destination site’s access rules first, especially when moving between an internal and public site.

### Choose the Messenger’s Help site

The Sites overview has **Shared by all sites** settings. **Help in the Messenger** chooses which site the widget’s Help tab shows. Password-protected and team-only sites cannot supply that tab in the same way as a public site.

The **AI chatbar** is shared widget configuration. Edit it under **Settings → Widget → AI chatbar**.

### Check AI access

Where shown, **Kai may answer from it** controls the site’s use for AI. Kai does not quote a site to a visitor who cannot open it. Continue using the agent’s knowledge scope and content audience rules as appropriate.

### Related

-   [Publish, brand and protect your help center](https://help.gleap.ai/en/articles/266-publish-brand-and-protect-your-help-center.md)
    
-   [Help center languages, SEO and redirects](https://help.gleap.ai/en/articles/16751973-help-center-languages-seo-and-redirects.md)
    

### Publish an API reference

Use the site’s **API reference** tab to import an OpenAPI spec and generate endpoint pages with code samples and Try it. See [Publish an API reference from OpenAPI](https://help.gleap.ai/en/articles/16752005-publish-an-api-reference-from-openapi.md) for setup and syncing.