Secure Team Messaging: A Step-by-Step Guide for Organisations

In most organisations, team messaging starts by itself. Someone opens a group, everyone joins with the app on their personal phone, and within a few months shift rosters, site photos, customer addresses and official letters are all flowing through the same chat. It is fast and everyone is used to it; but the owner of the group is not the organisation, it is an employee. Secure team messaging is not just a matter of choosing an encrypted app. It means the organisation decides who is on the network, where messages are kept, and what happens when a phone is lost or an employee leaves. In this article we cover the four layers of secure messaging, the relevant rules in Türkiye, selection criteria and a practical order for setting it up.

In short

  • Secure team messaging has four layers: content, accounts, devices and where the data is kept. Encryption solves only the first of these.
  • In a notice dated 29 January 2026, Türkiye’s Personal Data Protection Authority (KVKK) stressed that public bodies should not share official documents through foreign-based apps that have no data centre in Türkiye.
  • Presidential Circular No. 2019/12 requires that classified data is not shared through mobile apps and that access rights are granted according to the work actually being done.
  • The US Cybersecurity and Infrastructure Security Agency (CISA) recommends using only end-to-end encrypted communications and also assessing how much metadata an app collects.
  • If even the most secure channel goes silent when the network drops, the team reaches for the first tool at hand; continuity is part of security too.

What does secure team messaging mean?

A message is only as secure as the weakest link in the chain. For an organisation, that chain has four links:

  • Content: The message cannot be read in transit or on the server. The key distinction is whether the message is encrypted only while in transit, or end-to-end from sender to recipient.
  • Accounts: Who decides who joins the network, who sees which group and who is removed.
  • Devices: The door that opens when a phone is lost, stolen or left without updates.
  • Data: Where messages and attachments are stored, how long they are kept and who can access them.

We explained what end-to-end encryption means, without the jargon, in our article on a private, closed communication network. In short: the message is locked on the sender’s device and only opened on the recipient’s device; the points it passes through on the way cannot read its content.

Even when the content is protected, the information about who sent a message to whom and when, in other words the metadata, is a separate matter. CISA’s December 2024 mobile communications guidance makes using only end-to-end encrypted communications its first recommendation, and advises that when choosing such an app you also evaluate the extent to which the app and its associated services collect and store metadata. Although the guidance specifically addresses people in senior government and political positions, it states that it is applicable to all audiences.

The problem with groups on personal apps

In a work group set up on a personal messaging app, the account, device and data links all sit outside the organisation. The account belongs to the employee, and the person who opens and runs the group is usually an employee too. When that person leaves, the group history and the shared documents can stay on their phone. The organisation cannot track who sees what, or which document was forwarded to whom.

In Türkiye this situation has also led to an official warning. In a public notice published on 29 January 2026, the KVKK addressed reports and complaints that staff in public bodies were being made to use WhatsApp and to join various WhatsApp groups, and that official letters and documents were being shared this way. Taking into account that foreign-based messaging apps have no data centre in Türkiye, the notice stresses that official documents that may contain classified or critically important data should not be shared through them. According to the same notice, sharing any information or document containing personal data about real people may be regarded as a personal data processing activity, and employees’ mobile phone numbers are personal data too.

The table below summarises the difference between the two approaches:

The difference between a group on a personal app and a channel managed by the organisation
TopicGroup on a personal appChannel managed by the organisation
Account ownerThe employeeThe organisation
Adding and removing membersWhoever opened the groupAn authorised administrator
When an employee leavesHistory and attachments can stay on their phoneAccess can be closed centrally
Lost deviceThe organisation has limited ways to actThe device can be removed from the network
Where messages are storedWherever the app provider decidesWherever the organisation decides
Record after an incidentScattered screenshotsA timestamped record with access tied to authorisation

What do the rules say?

Article 12 of Türkiye’s Law No. 6698 on the Protection of Personal Data, published in the Official Gazette on 7 April 2016, requires the data controller to take all necessary technical and administrative measures to ensure an appropriate level of security, in order to prevent unlawful processing of personal data, prevent unlawful access to it and ensure its safekeeping.

Two paragraphs of the same article bear directly on team messaging. People who process data may not disclose the personal data they learn to others or use it for purposes other than processing; this obligation continues after they leave their post. If processed data is obtained by others through unlawful means, the data controller notifies the data subject and the Personal Data Protection Board as soon as possible. So losing a team phone that carries personal data is not just losing a device; it is an event that may trigger a duty to notify.

Presidential Circular No. 2019/12 on Information and Communication Security Measures, published in the Official Gazette on 6 July 2019, is more concrete. Under Article 4 of the circular, classified data is not shared or communicated through mobile apps, except domestic mobile apps developed by institutions authorised under the legislation for coded or encrypted communication. Article 5 sets the same ban for social media, and Article 6 asks that domestic apps are preferred for social media and messaging. Under Article 9, classified data or data containing institutional confidentiality is not kept on devices that are not institutionally authorised or that are used personally. Article 15 requires that staff access rights to systems, including those of senior managers, are granted according to the work actually being done and the needs involved.

The circular was written for public bodies and businesses that provide critical infrastructure services. For an organisation outside that scope it still offers a good checklist: which information can travel on which channel, who can see what, and on which device can data be kept?

Selection criteria

When assessing a messaging solution, put the following questions to the provider in writing and tie the answers to the contract:

Selection criteria for secure team messaging
CriterionQuestion to askWhy it matters
EncryptionIs content encrypted end-to-end or only in transit? Can the provider see the content?Content left readable on a server is open to anyone who can reach that server
MetadataWhere, and for how long, is the record of who messaged whom and when kept?CISA recommends assessing metadata collection as well
Membership controlWho adds people to the network, and who removes them?Control should sit with the organisation, not with a single employee
Group separationCan teams be separated without seeing each other’s messages?Access should follow work and need (Circular 2019/12, Article 15)
Lost deviceCan a lost device be removed from the network?A lost device should not remain an open door to the network
Data location and retentionIn which country, on whose server and for how long are messages kept?The KVKK notice draws attention to in-country data centres
RecordsCan authorised people reach a timestamped record during an after-action review?It shows who reported what, and when
Working without a networkDoes messaging continue when mobile coverage or the internet goes down?If the channel goes silent, the team turns to an insecure tool

For a wider list of technical criteria see our field communication system buyer’s guide, and for the steps of trialling an app in the field see our article on how to choose a mobile field communication app.

Step-by-step setup

Secure messaging does not start with a product decision; it starts with putting an arrangement in place. The order below can be adapted from a small team to a large organisation:

  1. InventoryList which channels your teams use today and what information flows through them: personal data, customer information, location, official letters. CISA also recommends starting by taking an inventory of valuable accounts.
  2. ClassificationPut into a written rule which information may travel on which channel. Set a separate, stricter rule for classified information and special categories of personal data.
  3. One channel, managed accountsBring work messaging together on a single channel managed by the organisation. Tie membership to administrators, set up groups by task and give each person only the groups their work requires.
  4. Account protectionDo not rely on codes sent by SMS for sign-in. CISA notes that SMS messages are not encrypted and that someone with access to a telecommunications provider’s network can read them; it recommends phishing-resistant FIDO-based authentication and setting an extra PIN on the mobile carrier account against SIM-swapping attacks.
  5. Device hygieneKeep the operating system and apps up to date; CISA recommends checking weekly and enabling automatic updates. Review apps’ location, camera and microphone permissions and turn off the ones that are not needed.
  6. Leavers and lossesWrite down in advance who closes what, and how quickly, when an employee leaves or a device is lost. Remove the lost device from the network and record the incident.
  7. Breach planDecide who makes the call if data falls into unauthorised hands, and how the data subjects and the Board will be notified.
  8. TrialTest the lost-phone and network-outage scenarios at regular intervals. A procedure is proven in the field, not on paper.

We covered in detail how the record is used in an after-action review in our article on operation data logging.

Security and continuity

For field teams there is a dimension of security that is often overlooked: does the channel work at the moment it is needed most? When the mobile network goes down or becomes congested during a disaster, a major outage or a crowded event, and the secure app the organisation chose also goes silent, the team reaches for the first tool at hand: a voice call, SMS or another personal app. As CISA points out, SMS is not encrypted. The whole set of rules is then switched off at the most critical moment.

That is why the ability of the secure channel to work without a network, carrying messages from device to device without depending on central infrastructure, should be part of the assessment. It matters just as much that, in a crisis, the coordination centre can see on one screen which team has reported what.

Our approach

When we designed BosNets, we made leaving control of the network with the organisation a core choice. Message contents are encrypted with AES-256. Because communication is end-to-end encrypted, a message can only be opened on the sending and receiving devices; we cannot see the content of messages passing through the server either. The organisation decides who can join the network. Independent sub-groups can be set up for different units, and one group’s messages do not reach another. A lost device can be removed from the network.

When a private closed network is set up, records are kept on the organisation’s own server; the retention period and access rights are set by the organisation, and the data does not leave. The browser-based BosLog management interface records communication data. In mesh mode the system consists only of the devices in the field; no external server or infrastructure is involved. Where there is coverage BosApp works over the internet, and where there is none it works over the mesh through the BosMag beside it, switching automatically.

We do not aim to take the place of radio; voice coordination is radio’s job. We carry written messages, location and status on a network whose control stays with the organisation.

— Emir Tanrıver, BosNets co-founder

Frequently asked questions

Can a personal messaging app be used for work?

It depends on what information is shared. The KVKK notice of 29 January 2026 stresses that public bodies should not share official documents that may contain classified or critically important data through foreign-based apps with no data centre in Türkiye. Shares that contain personal data may also count as personal data processing. So put the rule in writing and set it together with your legal team.

Is end-to-end encryption enough on its own?

No. Encryption protects the content of a message in transit; who holds the account, a lost device, an outdated operating system and metadata are separate risks. CISA, too, recommends end-to-end encryption together with strong authentication, regular updates and restricted app permissions.

What should happen when an employee leaves?

Close their access the same day, remove them from groups and collect the organisation’s device. Under Türkiye’s Law No. 6698, the duty of people who process data not to disclose the personal data they learn continues after they leave their post; reminding them of this in writing as part of the leaving process is good practice.

Does keeping a message record conflict with privacy?

Not as long as it is clear who can access the record. The record shows, in an after-action review, who reported what and when. What matters is that the retention period and access rights are set by the organisation, and that the record is protected by the technical and administrative measures Law No. 6698 requires.

Sources

All posts