Hi Gliders,
User A requested access to my App, and I granted them access. Now, another user B came and user B also requested access and now the user B access is request is sent to user A and me. why request of B is sent to A? The request should only come to me.
Can you reproduce that?
Reproduce what?
Reproduce the error that you mentioned in the post.
Unfortunately, I donât have a screenshot because it happened during the test. I will explain it once again: when we published the app, user A granted access to user B. Then, user C came into the picture and requested access to the app. At this time, both user A and user B received an email to grant access to user C
I understand the problem, I mean if you deliberately try to reproduce that with other emails you control now, does it happen again.
Before reproducing the error, I would like to inform you that no roles are assigned to any user. This might be causing the problem.
Are both users members of your glide team, or just user A?
Only user A and B are member of glide team
Given that, I believe the behaviour you see is correct.
Access requests are not sent to all Users in your Users table, but they are sent to all members of your Glide Team.
Just jumping in on the end of this @Darren_Murphy, as I have a related question.
Is there a way to allow my Client to get and approve the âAccess Requestâ emails, as well as me getting them? I donât want to add him to my glideapps team as he will be able to edit the app / data etc, and he is a non-technical, business owner.
Otherwise, I will need to auto-forward the âAccess Requestâ emails to him, and wait for his reply, before I approve them - this is workable, but would be more efficient if he can approve them himself.
Not that I am aware of. I think an auto-forwarder is your best option in this case.
You can setup rules for auto-forwarding, but then would he have the right to approve the user? Or does he still have to tell you to approve in the builder?
The issue I think lies here: your client should probably be owner of their own apps. If their app is in your Glide team, then âtheirâ app is actually your app. If that is the agreement you and your client have then that is the agreement, but it should be clear to all parties involved who actually has ownership, and therefore access, to what.
Thatâs a good point @nathanaelb . He owns the Business and is the owner of the app that Iâm building for him (and which he wants me to maintain after).
How do you all manage this when building for a non-technical client? Iâm just worried about the risk of data getting deleted by mistake or other issues if he goes in via the Editor.
I will be building Admin screens/functions for him to manage Users, Reports etc, but that will be via the app, not directly in the Editor.
Either clients come to me and they already have an account on Glide, or prospects contact me and I will build for them once they create an account on Glide and invite me as a member of the team.
I would not feel comfortable owning a clientâs application, just in principle. I donât want the responsibility. Also, I wouldnât want a client to feel locked.
The easiest (for me), the safest for them and most ethical setup (in my opinion) is that they have their own account, their own team. I have had non-technical clients tell me itâs okay if I own their accounts and I appreciate the trust, but I wonât do it.