I have one login for my app for the level Lead Assess. It uses a specific fixed email address for that level. Filters are in place so they only see certain views. I need for that one login to be used by multiple people in separate locations at the same time. Each location needs security filters so that user only sees their records. I want each Lead Assess user to set their location when they first log in at a location and have that location stored somewhere so I can use the security filters as listed above. Other Lead Assessors will set other locations for the same email address login. Are the user settings stored at the user’s login level? Or in the device they are logged into? Other? I would rather not have to create a separate email address for each location’s login.
Hello @NCBOM,
While you can technically use a single AppSheet login across different locations, keep in mind that AppSheet allows one account to be active on up to five devices simultaneously. This is a great solution for shared hardware—like a tablet on a shop floor—but it does come with some trade-offs.
Since everyone shares the same identity, you won’t be able to tell who made specific changes in the audit logs.
You also run the risk of ‘last writer wins’ sync conflicts if two people edit the same record at once.
If your goal is individual accountability or personalized data views, the best approach is to assign unique logins to each user.
The same information has been shared on this post
Sounds like you’re trying to get per-user behavior without paying per user. There’s no secure way to accomplish that. You can approximate it, but it will never be secure. Also, it’s a violation of the terms of service.