From eab287d224e3acd1fa6c5676fa06f4f5ff523403 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 16 Aug 2026 05:46:44 -0700 Subject: [PATCH] docs(gateway): correct node pairing storage (#124571) --- docs/gateway/operator-scopes.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/gateway/operator-scopes.md b/docs/gateway/operator-scopes.md index 02bdcdb3e46c..fb2dd97f7ad5 100644 --- a/docs/gateway/operator-scopes.md +++ b/docs/gateway/operator-scopes.md @@ -198,10 +198,10 @@ can approve, reject, rotate, revoke, or remove only its own device entry. ## Node pairing approvals -Legacy `node.pair.*` methods use a separate Gateway-owned node pairing store. -WS nodes use device pairing (`role: node`) instead, but the same approval -vocabulary applies. See [Gateway pairing](/gateway/pairing) for how the two -stores relate. +`node.pair.*` capability approvals are stored on the paired device record in +the shared SQLite pairing store. Gateways migrate any remaining entries from +the retired standalone `nodes/paired.json` store into those records once at +startup. See [Gateway pairing](/gateway/pairing) for details. `node.pair.approve` derives extra required scopes from the pending request's command list: