Cloud-managed SALTO access for organizations that want remote administration and connected smart-lock workflows without hosting local access-control software.
What this product family does
SALTO KS should be evaluated by site count, doors, gateways, mobile/physical credential mix, real-time event expectations, integration/API requirements and subscription ownership. Cloud management does not remove opening-level decisions about lock type, door preparation, egress, batteries and wireless coverage.
Products and decisions
| Product area | What it includes | Selection guidance |
|---|---|---|
| Cloud management | Remote user, access and event administration | Define roles, MFA, offboarding and installer support access |
| Connected locks | Supported SALTO wireless/electronic hardware | Survey RF topology, battery service and offline behavior |
| Credentials | Mobile and physical access methods on supported products | Provide fallback access and phone-loss procedures |
| Integrations | Supported ecosystem/API connections | Confirm exact partner, version, data owner and failure handling |
Questions to answer before quoting
- Recurring service and account ownership
- Internet and gateway resilience
- Mobile adoption and physical-credential fallback
- Migration from existing SALTO or third-party hardware
- Who owns administration, backups, updates and recurring services?
- What must continue working during network, internet or power failure?
- Which opening, egress, accessibility and life-safety requirements apply?
- What training, documentation and preventive maintenance are required?
Request a product-specific site survey
Boston High Tech serves projects from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
Capabilities and product families were checked against the manufacturer links below.
How to compare and specify this product family
For SALTO KS Cloud Access Control, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Practical questions about running SALTO KS from the cloud while still specifying locks, gateways and credentials.
If SALTO KS is cloud managed, do we still have to specify lock hardware?
Yes. Cloud management moves administration off a local server, and it does not remove the opening-level decisions about lock type, door preparation, egress, batteries and wireless coverage. Each door is still surveyed for hardware, cable path, power and network, and the bill of materials comes out of that record rather than out of the platform choice.
What happens when an employee loses the phone holding their credential?
Access for that person is removed through cloud management, which covers remote user, access and event administration, and the employee is issued the physical fallback the credential mix already allowed for. Phone-loss procedures are called out as a design item for this reason, so the replacement path exists on paper before the first phone goes missing.
How do gateways affect where connected locks can be installed?
Gateways set the coverage boundary, since a connected lock has to reach one. RF topology is surveyed before locks are placed on the drawing, and a door at the end of a long corridor or behind a stair core can need a gateway of its own. Internet and gateway resilience gets scoped in the same exercise.
Who takes care of lock batteries after the system is live?
Battery service belongs in the preventive maintenance scope, and it is surveyed door by door alongside RF topology and offline behavior, because a lock on a busy entrance is serviced on a different rhythm than a storeroom. Agree whether the customer’s facilities staff or the integrator performs that work at the same time as training and documentation.
Will SALTO KS connect to the systems we already run?
That depends on whether each one is among the supported ecosystem/API connections, and the checking method is specific: exact partner, version, data owner and failure handling. Settle failure handling early, since a link that quietly stops passing users becomes an access problem for staff long before anybody notices the connection itself has stopped.
Does older SALTO hardware carry over to KS?
Some of it can, which is why migration from existing SALTO or third-party hardware is listed as a decision to make before ordering. Inventory each opening with the hardware installed today, then test that model against what the KS design needs, since a door that keeps its lock body may still need new electronics. Product availability and supported integrations are confirmed for the project before procurement.
SALTO owner, administrator and buyer resources
Discuss SALTO installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official SALTO software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.