@aastrika/ai-elements 0.2.0 → 0.2.1

package/README.md

@@ -260,7 +260,7 @@ Three things, and nothing else.
 |---|---|
 | `apiBase` | Where the service is, no trailing slash. Empty string means same-origin. |
 | `getAuthHeaders` | Headers proving the caller may use the service — in practice a bearer token. |
-| `creator` | The username of whoever is signed into **your** application. |
+| `creator` | Who is signed into **your** application — their name or email, shown as-is in the usage report. |
 | `onError` | Optional. Called whenever a request fails, so your monitoring hears about it. |
 
 **Both are functions, and both are called on every request.** Tokens expire: a
@@ -268,6 +268,9 @@ string handed over at startup stops working mid-session and the package has no
 way to ask for a fresh one. A function lets you return whatever your own auth
 library currently holds, and lets you switch user without reloading.
 
+`creator` should be a **name or email** — it is displayed as-is in the usage
+report, so `asha.kumari` reads well and a UUID does not.
+
 `creator` is **attribution, not identity**. It is recorded against anything the
 call creates and the usage report groups by it. Nothing verifies it — the
 gateway decides whether the call is allowed at all.
@@ -284,8 +287,8 @@ needs:
 
 | Feature | Groups |
 |---|---|
-| `aastrika-content-studio` | `contentCreate`, `contentRead`, `contentUpdate` |
-| `aastrika-assessment` | `contentCreate`, `contentRead`, `contentUpdate` |
+| `aastrika-content-studio` | `contentCreate`, `contentAccess`, `contentUpdate` |
+| `aastrika-assessment` | `contentCreate`, `contentAccess`, `contentUpdate` |
 | `aastrika-reports` | `contentAdmin` |
 
 Deleting anything needs `contentAdmin` as well. Without `contentUpdate` the