diff --git a/.agents/skills/inkreach-teable/api-reference/action-types.md b/.agents/skills/inkreach-teable/api-reference/action-types.md
index cf75b73..a253fa6 100644
--- a/.agents/skills/inkreach-teable/api-reference/action-types.md
+++ b/.agents/skills/inkreach-teable/api-reference/action-types.md
@@ -31,6 +31,26 @@ Inside a `script` action, these are available:
 
 **NOT available**: `fs`, `eval`, `Function`, `process` (only `process.env`), `child_process`.
 
+**Trigger user role** (user-initiated triggers only — buttonClick / recordCreated /
+recordUpdated / recordCondition / formSubmitted): when a real user fires the
+workflow, `triggerInput` also carries their role in THIS base:
+
+| Field | Type | Meaning |
+|-------|------|---------|
+| `triggerInput.user` | `{id,name,email}` | Who triggered (absent for scheduledTime/webhook) |
+| `triggerInput._triggerUserRoles` | `string[]` | Display names of the user's enabled, non-deleted roles in this base. `[]` for admins (admins have no AM role) |
+| `triggerInput._triggerUserIsAdmin` | `boolean` | `true` for space owner, AM admin users, or everyone when AM is disabled for the base |
+
+These fields are **absent** for system triggers (scheduledTime / webhook) — no
+user context. Branch on them in scripts:
+```js
+const roles = triggerInput._triggerUserRoles ?? [];
+const isAdmin = triggerInput._triggerUserIsAdmin ?? false;
+if (isAdmin) { /* admin path */ }
+else if (roles.includes('工厂运营')) { /* operator path */ }
+else if (roles.includes('售后客服')) { /* support path */ }
+```
+
 **Back-channel API access**: inside scripts, call the instance's own API:
 ```js
 const res = await fetch(triggerInput._apiBaseUrl + '/api/table/tblXXX/record', {