Who can use the Call Flow Designer

A wrong publish can send every caller to the wrong place. Access is therefore layered: what your licence includes, what your PBX allows, and who inside your company can open the module.

1. The licence (per account)

The Call flow module is part of the JEDWare licence. Without it, ToolsCall flow does not appear for your users, and anyone who opens the page by its address sees “Call flow is not part of your licence” with a Contact support button. Your partner adds the module to your JEDWare account; the integration picks it up within a few minutes, no restart needed, and the sidebar entry follows within ten minutes or on the next visit to the page.

2. Live publishing (per account)

Even with the module, live publishing is switched on separately by JEDWare. Until then every administrator can build, save and Test in sandbox, but Publish live, a live call-script deploy and Undo last publish are not offered. This is deliberate: a new flow is built and tested first, then the account is unlocked.

Your partner can also pin a mode on the PBX itself, in the integration’s settings. That setting wins over the licence:

Badge on the pageMeans
Dry run: publishing is disabledyou can build, save and look at the change list; nothing is written
Sandbox: your numbers are not changedsandbox tests only
Sandbox and live: you choose when you publishboth, chosen per publish

Hover the badge to see where the mode comes from: “Live publishing follows the licence” or “Mode set in the integration settings”.

3. Who sees it (per user)

The module is for administrators. A JEDWare login with the administrator role, and JEDWare staff or partners working on your account, see ToolsCall flow. Report users, wallboard users and agents do not. Every administrator who can open the module can do everything in it, including publishing live when the account allows it.

The read-only demo site shows the module but cannot save or publish.

4. What is recorded

Every save, sandbox test, live publish, deploy and undo is recorded with the user’s name: on the flow, in the History… dialog, in the JEDWare web app’s own log, and in the integration’s log on the PBX host. JEDWare staff working through your account are marked as such. There is no anonymous publish.

5. What protects you even when the wrong person publishes

  • The change list is shown before anything is written, and a live publish asks a second time, naming the numbers.
  • The number is switched last, and a failed publish is rolled back automatically.
  • Every live publish saves a copy of the previous routing; Undo last publish restores it in one step.
  • Reused 3CX objects and inbound rules are never deleted.
  • Sandbox objects live in their own number range and never touch live numbers.

Next: Troubleshooting.