Security Settings and Other Considerations
The IndyGo kiosk/mobile application follows rules similar to the main IndySoft client and lets you set security items per profile.
Security settings
These security items affect the mobile/kiosk application:
- Block User From Modifying Equipment Image
- Allow Users to Pair RFID Tags
- Allow Users to Unpair RFID Tags
- Block User from IndyData REST API
A key behavioral difference: the kiosk/mobile application user can only have one profile active at login, and all default companies come from the DEFAULT user/location for that user.
There is no way in the IndyGo mobile application to change the user/location. Only the base profile determines the security settings for the user.
In this example, user ANGELENA's base profile is System Administrator. All security settings applicable to the mobile application are inherited from that base profile, even when dealing with ABC Scale - Greenville Scale Division's equipment.
Angelena — System Administrator base profile
"No Access" base profile
A No Access base profile is the exception to the rule above. No Access has no security items at the database level — it's primarily used to restrict the user to seeing equipment only for companies with explicit exceptions. To support this, a No Access user inherits security items only when their employee company matches a company exception with a valid profile.
In the example below, user GABRIEL has a base profile of No Access and is in employee company MJCS. Because there is also a company exception that matches MJCS, the related security profile of Standard User is used to inform security items for that user.
Gabriel — No Access base profile with MJCS exception
Users with a base profile of No Access cannot log in unless the system-wide option in Workflow Configuration is enabled.
Default company lookups for event/action fields
In the main client, if no default company is specified for a field in user/location settings, the company currently exposed on the equipment view dictates company-based lists.
IndyGo functions similarly, except it can't be guaranteed that the user has logged into the main client and selected a current company. If there's no default company for a list and no current equipment-view company, the employee company related to the logged-in user is used for any company-based list.