Larry buttons' description

Created by Daniil Stasiuk, Modified on Wed, 1 Jun, 2022 at 11:37 AM by Daniil Stasiuk

1. "Schedule Updates" -> Schedule and check IQ update (Only available for CLay support)
2. "Group" -> Add certain IQs to a group, then schedule IQ update on batch (Only available for Clay support, I think)
3. "Enable digital key" -> If the app user is not seeing the mobile key button, then after click this button, the user is able to see the mobile key after logout and login
4. "Sync digital key" If the IQ states mobile key is not synced, then the mobile key users will have problems with the locks attached under this IQ. Sync mobile key will copy the mobile key info from another IQ from this site which has the mobile key synced. And there is one button on collection level, which can sync for all IQs, without going to each IQ. 

5. "Sync Tenant certificate"  Salto KS is multi tenant system, in practical example, Salto KS (app.saltoks.com) has its own tenant, ACA has its own tenant, Prosegur (mainly used in Spain & Portugal) has its own tenant. Tenant certificate is used for digital key functionality, each IQ needs to have the correct tenant certificate for the use of digital key, which was a big topic when the old platform migrated into the current one, hence this button. If an app user has this error with the app "An authentication error has occurred between the mobile phone", please click the button for the IQ in question.

6. "Sync LAM LAM stands for Local Access management, that is the access info stored in the IQ, when you are managing the access with the website, the backend of KS is forwarding the access to the IQ. This button is used when you see the locks under the IQ is not working with the access schedules, then press the button will force the backend to send the latest LAM to the IQ, then you can ask the user to try to access again.





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article