- Ya
- 10 Mei 2026, 20:36 UTC
- Mwandishi
- kamo
- Ahadi ya
- 298b24b
The wizard previously redirected the creator to **************** right after POST /api/security/org returned. The new org's domain has no DNS yet, so the redirect resolved to an unreachable host (e.g. https://internal.sign.pink) and the user was stuck. Now the wizard always pushes **************** on the current parent host (e.g. internal.kamocrm.com), where the creator can configure DNS for the new org's custom domain. Once SSL is confirmed, DnsProgressView's "Enter workspace" button (previously a hard-coded href="/") mints an OTK via /api/security/enter-as and jumps to https://internal.<new-domain> — the same pattern /network/page.tsx uses for entering an existing org. The page propagates orgId so the button knows which org to enter; without orgId it falls back to the old "/" href.