From c8937518593a4f6adb3da0aac57ede5bf53b359e Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 24 Jul 2026 03:03:55 +0000 Subject: [PATCH] Document group-owned personal number assignment Update the dashboard's own Personal Numbers card description and the Anveo Direct setup guide to mention assigning a DID to a group instead of a single extension. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Ho9mZgAkVpdz7S5wJkg8Nf --- docs/anveo-direct-setup-guide.md | 8 ++++++++ services/security-dashboard.sh | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/anveo-direct-setup-guide.md b/docs/anveo-direct-setup-guide.md index 8b75bd9..967a6f9 100644 --- a/docs/anveo-direct-setup-guide.md +++ b/docs/anveo-direct-setup-guide.md @@ -159,6 +159,14 @@ In the Security Dashboard's PSTN Trunk tab: DID instead of the shared trunk DID. Enter the DID as **10 digits, no leading 1** (matches the same convention as the trunk DID above) — the dashboard's own input validates against exactly that format. + You can assign the DID to a **group** instead of a single extension — + pick `Group: ` in the owner dropdown (create the group first + under Groups if it doesn't exist yet). Every current member whose own + tier/approved-numbers authorize the caller rings, checked fresh on + every call, so membership changes apply immediately with no reinstall. + A group has no single extension to hang an outbound Caller-ID override + on, so the Caller-ID-override part above only applies to + single-extension assignments. ## 7. Test diff --git a/services/security-dashboard.sh b/services/security-dashboard.sh index 812b271..1e207bb 100644 --- a/services/security-dashboard.sh +++ b/services/security-dashboard.sh @@ -1625,7 +1625,7 @@ INDEX_HTML = """

Personal numbers

- Multiple DIDs can share this one trunk. Assigning a DID to an extension routes inbound calls to that DID straight to its owner (still gated by the owner's own tier/approved-numbers above — no ring-group fallback), and makes that extension's outbound calls show this DID as Caller-ID instead of the shared trunk DID. The shared DID/ring-group keeps working regardless. + Multiple DIDs can share this one trunk. Assigning a DID to an extension routes inbound calls to that DID straight to its owner (still gated by the owner's own tier/approved-numbers above — no ring-group fallback), and makes that extension's outbound calls show this DID as Caller-ID instead of the shared trunk DID. You can also assign a DID to a group instead of a single extension — every current member whose own tier/approved-numbers authorize the caller rings (checked fresh on every call, so membership changes apply immediately); a group has no single extension to hang the outbound Caller-ID override on, so that part only applies to single-extension assignments. The shared DID/ring-group keeps working regardless.