@terminal3/t3n-sdk 4.44.0 → 4.45.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli/index.js +1 -1
- package/dist/index.d.ts +11 -2
- package/dist/index.esm.js +1 -1
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/dist/index.d.ts
CHANGED
|
@@ -2848,8 +2848,17 @@ declare class T3nClient {
|
|
|
2848
2848
|
*
|
|
2849
2849
|
* The scope organisation is resolved node-side from the session DID, so
|
|
2850
2850
|
* there is no scope parameter and a caller can only ever read their own org.
|
|
2851
|
-
*
|
|
2852
|
-
*
|
|
2851
|
+
* How much of that org comes back depends on the caller's admin standing:
|
|
2852
|
+
* an **admin** of the organisation gets **every member's** activity, while
|
|
2853
|
+
* anyone else gets only the rows they took part in — the calls they made, plus
|
|
2854
|
+
* the calls their agents made in their name. The call succeeds either way, so
|
|
2855
|
+
* a smaller page is a narrower scope, not an error; label the view accordingly
|
|
2856
|
+
* rather than treating it as the whole organisation's log.
|
|
2857
|
+
*
|
|
2858
|
+
* A caller belonging to more than one organisation IS refused, since there is
|
|
2859
|
+
* no single scope to read. That arrives as an {@link RpcError} whose
|
|
2860
|
+
* `httpStatus` carries the JSON-RPC code `-32003` (Forbidden) — that field
|
|
2861
|
+
* holds `error.code`, not an HTTP status — with the reason in `detail`.
|
|
2853
2862
|
*
|
|
2854
2863
|
* Like {@link getAuditEvents} / {@link getUsage}, this runs the session
|
|
2855
2864
|
* payload encryption: entries carry principal DIDs, so params and response
|