Forum Discussion
AustinK
3 years agoQrew Commander
@Evan Martinez Do you have any insight here? I am starting to think this may be something for the user voice/feedback channel instead although that would be very disappointing.
Is there any workaround for this to prevent users from changing their own email? Name change is not a big deal but an email change can cause issues.
Is there any workaround for this to prevent users from changing their own email? Name change is not a big deal but an email change can cause issues.
- EvanMartinez3 years agoQuickbase StaffHi Austin,
Typically the way companies handle this is to transition to using SSO for their login so that their IT controls the service which their users authenticate from. Then they store their credentials and control email address, name, etc. SSO usually also offers a company other benefits as well for user management, tracking, etc.
Since a non SSO user can exist in multiple QB accounts and they control their user when it isn't tied to the corporate accounts like that we don't have a feature to prevent email changes on a user managed on the QB side and that would be something that would need to go into feedback.
------------------------------
Evan Martinez
------------------------------- AustinK3 years agoQrew CommanderThe emails they use and change are corporate emails not their own. The accounts are controlled by us and not owned by them and only exist within this realm. Maybe there is some issue in the way this is currently set up then.
- EvanMartinez3 years agoQuickbase StaffHi Austin,
If you have your users using corporate emails and you maintain a directory on your end you may be interested in implementing SAML to get single sign on in Quickbase. That would give you more control over your users and it might not be something you have set up today. It does take set up and some maintenance but a lot of companies find value in the insight/control it offers.
------------------------------
Evan Martinez
------------------------------