You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the MOD permission has to be granted by SQL access to the FDB. This means only a DBA can grant MOD permission.
We could create a skill in Amilia called "RFID: MOD". When a user taps in the firmware gets their skill list from Amilia. It could pass skills to the FDB with the call to checkin/out and the FDB could update the MOD_Eligible flag in the clientInfo table.
With this change, any Amilia administrator with access to Skills could change the MOD permission.
(Additionally, we use the display_classes field in the FDB to decide how to decorate a person's div in the checkin screen - for example, "staff" results in a magenta border. We could use Amilia Skills to set this field too.)
The text was updated successfully, but these errors were encountered:
I wonder if too many admins have the ability to add skills for this to work. I wonder if we can somehow create a limited permission group in Amilia so that only the head MOD, the ED and perhaps one or two others could edit the MOD eligible list.
Today the MOD permission has to be granted by SQL access to the FDB. This means only a DBA can grant MOD permission.
We could create a skill in Amilia called "RFID: MOD". When a user taps in the firmware gets their skill list from Amilia. It could pass skills to the FDB with the call to checkin/out and the FDB could update the MOD_Eligible flag in the clientInfo table.
With this change, any Amilia administrator with access to Skills could change the MOD permission.
(Additionally, we use the display_classes field in the FDB to decide how to decorate a person's div in the checkin screen - for example, "staff" results in a magenta border. We could use Amilia Skills to set this field too.)
The text was updated successfully, but these errors were encountered: