{"id":"salto.getting-started","app":"salto","title":"Connect Salto KS and complete onboarding","summary":"Configure the Salto connection, delivery channels and unit mappings.","url":"https://www.simultem-apps.com/wiki/salto#getting-started","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/salto.getting-started","resourceUri":"wiki://salto/getting-started","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02","keywords":["setup","credentials","admin","webhooks","permissions","existing codes","safe setup","migration","nykyiset koodit","käyttöönotto"],"sections":[{"title":"Setup order","steps":["Open Salto and follow Onboarding when required settings are missing; reopen it later to review setup.","Connect with a dedicated Salto KS admin user and review the connection status.","Before assigning live users to access categories, review Automatic and the PIN replacement settings in the onboarding PIN rules step or the account-level Rules view. If existing codes must stay unchanged during setup, save Automatic off for the categories being configured.","Configure email sender settings or the required SMS provider settings for PIN delivery.","Pull sites/users and map the intended Apaleo properties and units.","Check the saved mappings and real property layout before marking mappings ready. Test the intended reservation workflow before turning Automatic on."],"notes":["Salto KS remains the system for lock hardware, site users and physical access configuration. Required sites must already exist there.","Mappings ready is a setup status, not an automation switch. Reservation events can be processed as soon as a user is mapped to an automatic category; leaving onboarding unfinished does not pause PIN changes."]},{"title":"Preserve existing codes during setup","steps":["Connecting credentials and pulling sites/users do not change guest keypad PINs. Reuse the intended existing users and check their current Salto access groups.","Keep Automatic off while checking live mappings if the existing codes must remain unchanged. The default Accommodation unit rule is already automatic and can generate or replace PINs.","Use read-only PIN and guest-page checks to inspect recorded access. Use Generate PIN or Set custom only when you intend to change the real user PIN.","Review IQ activation separately from PIN automation. IQ setup uses its own credentials; the final IQ enable operation changes the app’s remote-opening policy.","Verify the actual property’s users, door grants, schedules and IQ state before enabling remote opening or reservation automation."],"notes":["The wiki and support helper describe the product; they cannot confirm a property’s live Salto configuration or whether its existing PIN records match the locks."]},{"title":"Access contexts","steps":["Open from a reservation for that reservation’s PIN and guest access.","Use a permitted property context for property-scoped workflows.","Use an authorized account context for settings that affect several properties, API credentials and guest-access setup.","If a control is read-only, follow its account-context or administrator guidance."],"notes":[]}],"text":"# Salto: Connect Salto KS and complete onboarding\n\nConfigure the Salto connection, delivery channels and unit mappings.\n\n## Setup order\n\n1. Open Salto and follow Onboarding when required settings are missing; reopen it later to review setup.\n\n2. Connect with a dedicated Salto KS admin user and review the connection status.\n\n3. Before assigning live users to access categories, review Automatic and the PIN replacement settings in the onboarding PIN rules step or the account-level Rules view. If existing codes must stay unchanged during setup, save Automatic off for the categories being configured.\n\n4. Configure email sender settings or the required SMS provider settings for PIN delivery.\n\n5. Pull sites/users and map the intended Apaleo properties and units.\n\n6. Check the saved mappings and real property layout before marking mappings ready. Test the intended reservation workflow before turning Automatic on.\n\nNote: Salto KS remains the system for lock hardware, site users and physical access configuration. Required sites must already exist there.\n\nNote: Mappings ready is a setup status, not an automation switch. Reservation events can be processed as soon as a user is mapped to an automatic category; leaving onboarding unfinished does not pause PIN changes.\n\n## Preserve existing codes during setup\n\n1. Connecting credentials and pulling sites/users do not change guest keypad PINs. Reuse the intended existing users and check their current Salto access groups.\n\n2. Keep Automatic off while checking live mappings if the existing codes must remain unchanged. The default Accommodation unit rule is already automatic and can generate or replace PINs.\n\n3. Use read-only PIN and guest-page checks to inspect recorded access. Use Generate PIN or Set custom only when you intend to change the real user PIN.\n\n4. Review IQ activation separately from PIN automation. IQ setup uses its own credentials; the final IQ enable operation changes the app’s remote-opening policy.\n\n5. Verify the actual property’s users, door grants, schedules and IQ state before enabling remote opening or reservation automation.\n\nNote: The wiki and support helper describe the product; they cannot confirm a property’s live Salto configuration or whether its existing PIN records match the locks.\n\n## Access contexts\n\n1. Open from a reservation for that reservation’s PIN and guest access.\n\n2. Use a permitted property context for property-scoped workflows.\n\n3. Use an authorized account context for settings that affect several properties, API credentials and guest-access setup.\n\n4. If a control is read-only, follow its account-context or administrator guidance.","related":[{"id":"salto.rules","app":"salto","title":"PIN categories and automatic access rules","summary":"Choose when each category assigns, rotates and releases access.","url":"https://www.simultem-apps.com/wiki/salto#rules","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/salto.rules","resourceUri":"wiki://salto/rules","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"salto.mapping","app":"salto","title":"Map Apaleo units to Salto users","summary":"Match the exact assigned unit with the correct site, access user and category.","url":"https://www.simultem-apps.com/wiki/salto#mapping","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/salto.mapping","resourceUri":"wiki://salto/mapping","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"salto.iq-remote-opening","app":"salto","title":"Activate and manage IQ remote opening","summary":"Follow the IQ selection, setup PIN, activation and review flow.","url":"https://www.simultem-apps.com/wiki/salto#iq-remote-opening","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/salto.iq-remote-opening","resourceUri":"wiki://salto/iq-remote-opening","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"platform.access","app":"platform","title":"Install, authorize and open an app","summary":"Choose the correct account/property context and complete authorization.","url":"https://www.simultem-apps.com/wiki/platform#access","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/platform.access","resourceUri":"wiki://platform/access","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"}]}