@7365admin1/core 3.52.1-staging.233 → 3.52.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/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# @iservice365/core
|
|
2
2
|
|
|
3
|
+
## 3.52.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- a90696f: Let a client owner save their organisation details during onboarding.
|
|
8
|
+
|
|
9
|
+
`PUT /api/organizations/:id` — the write behind step 1 of the onboarding wizard —
|
|
10
|
+
was gated on `requireOrgAccess` (staff, or a live member of the organisation).
|
|
11
|
+
The client owner has no `members` row at that point; theirs is created at the
|
|
12
|
+
last step of the wizard. Every new client therefore got 401 on the first step of
|
|
13
|
+
onboarding and could not leave it.
|
|
14
|
+
|
|
15
|
+
The gate is now `requireOrgReach`: staff, a live member, **or** somebody holding
|
|
16
|
+
an invitation naming that organisation — the same rule the roles, members and
|
|
17
|
+
invite endpoints already use for the three pre-membership flows. Nothing is
|
|
18
|
+
widened: a member of another client, and a caller holding only a password-reset
|
|
19
|
+
row, are still refused.
|
|
20
|
+
|
|
3
21
|
## 3.52.0
|
|
4
22
|
|
|
5
23
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -1,17 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
"@7365admin1/core": patch
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
Let a client owner save their organisation details during onboarding.
|
|
6
|
-
|
|
7
|
-
`PUT /api/organizations/:id` — the write behind step 1 of the onboarding wizard —
|
|
8
|
-
was gated on `requireOrgAccess` (staff, or a live member of the organisation).
|
|
9
|
-
The client owner has no `members` row at that point; theirs is created at the
|
|
10
|
-
last step of the wizard. Every new client therefore got 401 on the first step of
|
|
11
|
-
onboarding and could not leave it.
|
|
12
|
-
|
|
13
|
-
The gate is now `requireOrgReach`: staff, a live member, **or** somebody holding
|
|
14
|
-
an invitation naming that organisation — the same rule the roles, members and
|
|
15
|
-
invite endpoints already use for the three pre-membership flows. Nothing is
|
|
16
|
-
widened: a member of another client, and a caller holding only a password-reset
|
|
17
|
-
row, are still refused.
|