> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-knowledge-base/notion-integration.md).

# Connect Notion

Connect Notion to Siit, choose the team spaces or parent pages to share, then pin and publish the imported pages in the Knowledge tab since they are not published automatically

Connect Notion to Siit to automatically sync and publish your knowledge base articles 🚀

This integration allows you to import Notion pages into Siit and publish them in your Knowledge base.

### How to Connect Notion to Siit

1. Log into **Siit**
2. Click the **⚙️ Settings** icon (top right corner)
3. Go to **Apps & Integrations**
4. Select **Notion**
5. Click **Connect now**
6. Click **Select pages**
7. Choose the **Team Space or parent pages** you want to connect
8. Click **Give access**

Once connected, Siit will be able to fetch the selected content.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-df456aaa8a5707f21365c43eff5160853cf2ffe2%2FCapture_decran_2023-05-12_a_11.57.06.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-db461a8a169c2af33897102f768abeca4b866b9a%2FCapture_decran_2023-05-12_a_12.02.41.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-123814bdfea5cf4e9be70b410548c5c0e1392c89%2FCapture_decran_2023-05-12_a_12.07.21.png?alt=media" alt=""><figcaption></figcaption></figure>

### Publishing Notion Articles in Siit

After the connection:

1. Go to the **Knowledge** tab in Siit
2. You will see the imported Notion articles
3. **Pin** the articles you want to make visible
4. Click **Publish**

👉 Articles are **not automatically published** when synced.\
This gives you full control and an additional safety step before making content visible to employees.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-b3f5ca3e2e2c03e1a1d2f73d0ed486a4edd296f4%2FCapture-d-%C3%A9cran-2024-01-16-%C3%A0-16.42.03.png?alt=media" alt=""><figcaption></figcaption></figure>

### Adding & Syncing New Notion Pages

If you create new pages in Notion:

* If they are inside a connected Team Space or parent page → they will sync automatically
* If they are outside of it → you must go back to:
  * **Settings → Apps & Integrations → Notion → Relink**
  * Click **Select pages**
  * Add the new page

### ⚠️ Important: Database / Table Limitation in Notion

When a Notion page contains a **database or table listing other pages**, the Notion API does not always recognize those entries as linked child pages.

This means:

* If your articles are stored only inside a database table
* And the parent page is connected to Siit
* The articles inside the table may not sync

This is a limitation of how Notion structures content through its API.

### Recommended Setup (Best Practice)

To ensure full synchronization, we recommend:

### 1️⃣ Use a Public Team Space for Your Knowledge Base

Create a dedicated Team Space such as:

* “HR Wiki”
* “IT Knowledge Base”
* “Internal Help Center”

Inside this Team Space:

* Organize content using parent/child page hierarchy (not only tables)
* Structure articles like a website (clear arborescence)

This allows Siit to properly detect the relationship between pages.

### 2️⃣ Separate Public and Private Content

If you manage sensitive content:

* Keep confidential documents in a **Private section**
* Move only public-facing articles to the **Public Home**
* Connect only the Public Team Space to Siit

This ensures:

* No sensitive information is synced
* Full control over what becomes visible
* Cleaner long-term organization

### 3️⃣ Avoid Linking Page-by-Page (Not Scalable)

It is technically possible to link individual pages manually.

However:

* It is not scalable
* New pages will not sync automatically
* Maintenance becomes complex over time

Connecting the full Team Space is strongly recommended.

### Content Safety & Access Control

Even after connecting Notion:

* Articles are not automatically published
* You must manually publish them from Siit
* You can review content before making it visible

This adds an extra layer of control and reduces the risk of publishing unintended content.

### Troubleshooting Checklist

If articles are not appearing:

✔ Confirm they are not only stored inside a database table\
✔ Check they are inside a connected Team Space\
✔ Use **Relink → Select pages** to refresh scope\
✔ Verify permissions allow access

### Summary

For a smooth and scalable Notion integration:

* Connect a structured Team Space
* Avoid relying only on database tables
* Separate public and private content
* Use the manual publish step for validation

This ensures your knowledge base stays synchronized, structured, and secure.


---

# 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://docs.siit.io/guides/integrations/integrations-knowledge-base/notion-integration.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.