Whistleblowing system deployment models
How do we set this up: a single company, a corporate group or outsourced handling? Three proven layouts of accounts, permissions and billing; each compliant with the law and with how the organisation actually works.
Single organisation
One company or institution, but many departments, branches and locations. This model organises reporting for a single employer: separate channels where they make sense, and one register with one handling team where the law requires it.
- Separate forms and reporting pages per branch or department, all in one account
- Permissions per channel and per case: a report bypasses the local hierarchy where configured
- One domain and brand, one register, one handling team with roles
- Statutory deadlines, the audit log and register export for inspections included
Corporate group
A whistleblowing system in a corporate group is not one shared channel: each company is a separate employer with its own duty and its own register. In sygnadesk every company gets everything a single organisation has, and headquarters gets oversight of the whole without a shared case database.
- Each company has its own account: register, forms, reporting page, domain and team
- A whistleblowing committee at headquarters: people invited into companies, with the role granted locally
- One login and an organisation switcher; the "My organisations" screen collects deadlines and overdue cases from all companies
- A written authorisation for each person in each company kept in the repository, every access logged on both sides
MSP partner and outsourced handling
An IT provider or a law firm sells the white-label whistleblowing system to its clients, and where the client wishes, also handles reports on the client’s behalf as an outsourced service. Selling and handling are two separate roles; both leave a trail and both are controlled by the client.
- Client accounts created and billed in one panel, under the partner’s brand
- Volume discounts from 15 to 35% depending on the number of clients
- Handling on the client’s behalf: the role is granted by the client, director at most, never administrator
- Authorisation kept in the client’s repository, access cut with one click
- In end-to-end encryption mode the partner cannot read report content
The commercial terms of the partner model, discount tiers and the partner panel are described separately. See the partners page
Not sure which model fits?
Describe your structure and we will suggest the layout of accounts and permissions. No obligations.