@7365admin1/layer-common 4.148.2 → 4.149.0

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/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @iservice365/layer-common
2
2
 
3
+ ## 4.149.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 9692f90: Security role catalogue: add People Mgmt (people-mgmt) with the same six actions as the Property Management catalogue, so Security roles can be granted the People Mgmt page.
8
+
3
9
  ## 4.148.2
4
10
 
5
11
  ### Patch Changes
@@ -3530,11 +3536,11 @@ Monthly report: a month that had patrols opens the list of that month's patrol r
3530
3536
  `utils/console-tier.ts` + `composables/useConsoleTier.ts` mirror the server's
3531
3537
  own rule from two endpoints the console already calls, unprojected:
3532
3538
 
3533
- GET /api/members/user/:user/app/admin the Seven365 staff membership
3534
- GET /api/roles/id/:role that membership's role document
3539
+ GET /api/members/user/:user/app/admin the Seven365 staff membership
3540
+ GET /api/roles/id/:role that membership's role document
3535
3541
 
3536
- owner = member.type === "admin" && role.type === "admin" && role.default === true
3537
- staff = member.type === "admin" && role.type === "admin"
3542
+ owner = member.type === "admin" && role.type === "admin" && role.default === true
3543
+ staff = member.type === "admin" && role.type === "admin"
3538
3544
 
3539
3545
  `role.default` is the marker because it is the only property of a platform
3540
3546
  staff role no API caller can set - `role.controller.ts` validates create and
@@ -327,6 +327,38 @@ export default function useSecurityPermission() {
327
327
  },
328
328
  },
329
329
 
330
+ // People Mgmt in the Security app (owner, 2026-10-27): the same six
331
+ // actions, spelling and wording as `usePropertyPermission`, because both
332
+ // apps open the same `/api/people` records.
333
+ "people-mgmt": {
334
+ "add-people": {
335
+ check: true,
336
+ description: "Allows the user to add a new person to the system.",
337
+ },
338
+ "see-all-people": {
339
+ check: true,
340
+ description: "Allows the user to view the list of all people.",
341
+ },
342
+ "see-people-details": {
343
+ check: true,
344
+ description:
345
+ "Allows the user to view the details of a specific person.",
346
+ },
347
+ "update-people": {
348
+ check: true,
349
+ description: "Allows the user to update person details.",
350
+ },
351
+ "delete-people": {
352
+ check: true,
353
+ description:
354
+ "Allows the user to remove a person from the system permanently.",
355
+ },
356
+ "see-people-nric": {
357
+ check: true,
358
+ description: "Allows the user to see a person nric from the system.",
359
+ },
360
+ },
361
+
330
362
  // "guest-mgmt": {
331
363
  // "add-guest": {
332
364
  // check: true,
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@7365admin1/layer-common",
3
3
  "license": "MIT",
4
4
  "type": "module",
5
- "version": "4.148.2",
5
+ "version": "4.149.0",
6
6
  "author": "7365admin1",
7
7
  "main": "./nuxt.config.ts",
8
8
  "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",