URGENT NEED? Secure your communications today. 
Salt Communications Platform Onboarding Guide
Welcome to Salt Communications
This guide has been designed to help you prepare for your onboarding session and understand the key decisions that will shape your deployment.
During the onboarding process, our team will work with you to configure the platform, establish your communication structure, and ensure your users are onboarded successfully.
Who Should Read This Document
This document is intended for individuals responsible for implementing, managing, securing or overseeing the Salt Communications platform within their organisation. Such as:
- System Administrators
- Risk Managers
- Chief Information Security Officers
- Risk Team Coordinators
What Salt Communications Provides
Salt Communications delivers secure communications for organisations that require enhanced privacy, control, and resilience.
The platform enables organisations to:
- Communicate securely across teams and departments
- Create structured communication environments
- Control user visibility and access
- Broadcast information quickly to selected groups
- Apply security policies based on organisational requirements
- Support business continuity and operational communications
Decision: Whether you are deploying to a small team or a large organisation, the platform can be configured to align with your operational structure and security requirements.
Understanding your deployment
Before the onboarding session, it is useful to consider the size of your intended deployment.
Typical organisation sizes include:
- 10–99 Users
- 100–249 Users
- 250–499 Users
- 500–999 Users
- 1,000–4,999 Users
- 5,000+ User
Tip: Understanding the expected user population helps us recommend the most suitable platform structure and onboarding approach.
Planning Your Initial Rollout
Most organisations with more than 100 users begin with a phased rollout rather than inviting all users immediately. We always recommend getting 3-5 of the technical team to validate the system before inviting the initial users.
Before the onboarding session, consider:
- Who should be included in the first wave of users
- Whether key stakeholders or administrators should be onboarded first
- Whether a pilot group would be beneficial before wider deployment
Decision: Whether you are deploying to a small team or a large organisation, the platform can be configured to align with your operational structure and security requirements.
User Invitations
During onboarding, we will discuss how users will be invited onto the platform.
Organisations typically choose between:
- A mobile telephone number.
(NOTE: Some regions restrict Salt from sending SMS invites. Please speak to your Salt contact if this is your preference) - Corporate email address.
- Personal email address.
- Self generated random identifier which is shared offline with the user.
- A combination of all of the above.
Tip: Corporate email addresses provide the greatest level of organisational control and user management. However, for truly “out-of-sight” secure communication, organisations often use a personal email or a randomly generated code delivered out-of-band.
Understanding Circles
A Circle contains a contact list within Salt Communications.
It contains the people you are permitted to communicate with based on your corporate relationship and is defined by your organisation’s administrators.
Unlike traditional messaging platforms, users do not automatically have access to a company wide directory. Instead, administrators control who can see and communicate with whom. Depending on your organisation’s requirements, a Circle can be limited to a small team, department, project group, or expanded to include the entire organisation.
Circles ensure users have access to the people relevant to their role while maintaining appropriate security, privacy, and operational control. Most people are usually a member of multiple circles. The exception is for protected VIPs who can maybe only see a small group of trusted contacts.
Note: Salt does not need access to your personal contacts on your phone, helping to protect your privacy by keeping contacts separate.
What Is a Circle?
A Circle is a structured communication environment that groups users together based on a common purpose, role, department, project, or operational function.
Examples may include:
- Leadership Team
- Operations Team
- Incident Response Team
- Regional Teams
- Project Groups
Decision: During onboarding, we will work with you to determine the most appropriate Circle structure for your organisation.
Broadcast Channels
Broadcast channels provide a simple way to distribute information quickly to large audiences.
Common use cases include:
- Organisation wide announcements
- Operational updates
- Emergency notifications
- Executive communications
- Regional messaging
Decision: During onboarding, we will discuss whether broadcast channels would be beneficial and how they should be structured.
Security and Policy Configuration
Salt Communications provides a range of security controls that can be tailored to different user groups.
Examples include:
- Screenshot restrictions
- PIN enforcement
- Device security requirements
- User access controls
Note: Not every organisation applies the same policies to every user group. During onboarding, we will review your requirements and recommend the most appropriate configuration.
Key Considerations Before Onboarding
To ensure a smooth deployment, there are several decisions to consider before your onboarding session:
Identify the number of users who will require access to the platform, both for the initial rollout and future deployment phases.
Decide whether users will be invited using corporate email addresses, personal email addresses, or a combination of both.
Consider how users should discover and communicate with one another. Some organisations prefer an open directory where all users are visible, while others require controlled visibility between teams, departments, or operational groups.
Determine whether broadcast channels are required to distribute information quickly across the organisation or to specific groups of users.
Consider any security requirements that may need to be applied, such as screenshot restrictions, PIN enforcement, or different policy settings for specific user groups
Note: Our team will work through each of these areas during the onboarding session and help recommend the most appropriate configuration for your organisation.
Need Further Clarification?
Have a question about any section of this page? Select the relevant section from the dropdown below and we’ll be happy to help.
Who Should Read This Document
This document is intended for individuals responsible for implementing, managing, securing or overseeing the Salt Communications platform within their organisation. Such as:
- System Administrators
- Risk Managers
- Chief Information Security Officers
- Risk Team Coordinators