I'm hoping this is just a misunderstanding. EOTI is a user that essentially opens up your application to anyone with the link to it. Typically, builders will also create a role labeled EOTI for clarity and assign this to the EOTI user, giving anyone the permissions assigned to that role. I understand the frustration that comes from needing to use EOTI, but also needing to control access for your users in a specific way, but EOTI is exactly what it says - Everyone. It is an extremely powerful tool that must be used with great care and requires the app-builder to very carefully consider their setup. Unfortunately, there is no way to remove a licensed user from the EOTI setup. Thankfully, though, this question is nearly 3 years old and there have been a number of updates since then to make this easier.
If you have questions about setting up an EOTI app, please post those and I'm sure the community would be able to help.
------------------------------
Blake Harrison
bharrison@datablender.ioDataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------
Original Message:
Sent: 01-13-2021 09:07
From: Jon Doe
Subject: Everyone on the Internet
What a bizarre response. You act like it was snobby or something for the OP to ask or make her remarks. It is a crappy design -- I can understand why it is and even it being a default, but not having the ability to remove users from the EOTI role and only have their originally assigned is a bad design.
So you got the rule for the roles, but what about if it needs to be dependent on other fields as well? Can't have both. Garbage design made worse by a garbage response to a customer.
Original Message:
Sent: 06-20-2018 19:04
From: QuickBaseCoach Dev./Training
Subject: Everyone on the Internet
Yep, there are say a few billion people on the planet with access to the internet and among the "great unwashed' are your star employees. So yes, they are part of everyone on the internet.
You will need to write your rule to include the roles you want the rule to apply to, for example
any of
the user is in the role employee
the user is in the role administrator
the user is in the role viewer.
or else the opposite, the user is not in any of those roles.