From ee41815df373622d67cd280b1469dfb12b735918 Mon Sep 17 00:00:00 2001 From: Jerry Ren Date: Tue, 20 Oct 2026 15:53:46 +0800 Subject: [PATCH] docs: clarify HTML page account token requirements --- docs/html-pages/getting-started.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/html-pages/getting-started.md b/docs/html-pages/getting-started.md index b3a0cbaa..a36b80bd 100644 --- a/docs/html-pages/getting-started.md +++ b/docs/html-pages/getting-started.md @@ -74,9 +74,18 @@ These values are registered to `window.__HTML_PAGE_DEV_CONFIG__` and picked up b !!! note "Where the values come from" - - `accountToken` — an API token you generate in the base in advance. See [how to create API tokens](https://seatable.com/help/create-api-tokens/). + - `accountToken` — your account token, available under **Personal settings -> Profile -> Account-Token**. This is not a base API token. - `server`, `appUuid` and `pageId` — shown under **HTML page development information** in the page's configuration (see below). +!!! note "Why use accountToken instead of baseAPIToken?" + + Some HTML page features require user information that a base API token cannot provide. Local development therefore uses an account token for: + + - Checking HTML page access permissions. + - Calling APIs that retrieve the current user's information. + + If view support is added in the future, some view filters may also require user information. + The HTML page configuration shows these values ready to copy, alongside the upload area you will use later: ![HTML page configuration with development information and upload area](../media/html-page-config.png)