anbaric 1.74.0 → 1.76.0

package/docs/features/entitlements.md

@@ -61,9 +61,12 @@ return `true` in your app; only the global grant also satisfies every other app.
 
 ## Granting
 
-Apps can't grant. An administrator opens **Entitlements** in the console, picks
-the user, the entitlement and its scope, and adds a note; the same page revokes
-grants and creates global entitlements. Every grant records who made it.
+Apps can't grant. An owner or admin does it from the console's **Users** page:
+open a user and tick what they hold in each app, select several users and
+grant to all of them at once, or turn to the page's **Entitlements** tab,
+which lists each entitlement per app with who holds it, to grant one to many
+people or revoke it. Global entitlements are defined on that tab too. Every
+grant records who made it.
 
 ## Invitations and invite links
 

package/docs/patterns/authorization.md

@@ -71,7 +71,7 @@ if (! await hasEntitlement(request, "export")) {                     // per requ
 }
 ```
 
-Administrators grant and revoke them from the console's **Entitlements** page;
+Administrators grant and revoke them from the console's **Users** page;
 locally every check passes. See [Entitlements](../features/entitlements.md).
 
 ## Design tips

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anbaric",
-  "version": "1.74.0",
+  "version": "1.76.0",
   "description": "Everything needed to write an Anbaric app: state machines, jobs, document and secret stores, local in-memory implementations and the Anbaric Cloud clients",
   "license": "MIT",
   "type": "module",
@@ -24,9 +24,9 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "anbaric-impl-cloud": "^1.74.0",
-    "anbaric-data-store": "^1.74.0",
-    "anbaric-state-machine": "^1.74.0",
-    "anbaric-tsapi": "^1.74.0"
+    "anbaric-impl-cloud": "^1.76.0",
+    "anbaric-data-store": "^1.76.0",
+    "anbaric-state-machine": "^1.76.0",
+    "anbaric-tsapi": "^1.76.0"
   }
 }