Hi there,
I’m trying to add a new user in my app, and in doing so assigning this user the same “Role”. (Pro App, using Roles).
But Glide doesn’t allow me to do this. I’m 99.99% sure this worked a week ago, so maybe they’ve changed something?
I’m aware of what they describe here, regarding roles: Roles
but how do I then assign the same role to my new user, if my current approach isn’t doing the trick?
Thanks guys!
Yeah, I can replicate this. Glide allows the role to be initially set, but it doesn’t stick.
Just to double-confirm: the signed in user already has the role that you are trying to assign, yes?
(for what it’s worth, I generally use Make for assigning roles)
Yes, I can confirm that.
And my apps are acting weird right now: I wonder if they have changed something relative to how Roles work.
What do you mean by “…use Make”?
And here’s what I’ve also begun experiencing:
I pull in the same table in a “Public App” where I’m NOT using Roles, but rather email addresses from another column as Row Owners. Here I can suddenly no longer list rows created from my other app (Where I use the roles).
update: This is only the case sometimes… It seems a bit erratic / random… Trying to identify a pattern in this. Would be great with better documentation on how Roles work. Also across apps.
Make, otherwise known as Integromat. Send a webhook with the Users RowID and the name of the role, and then push it back in via the API. With this method, any user can set any role.
Yes, I’ve also noticed some dodgy behaviour in the past few days. I reported a role-related bug last week where Glide was only recognising the first role in an array of roles (array created in an attached Google Sheet).
It should be App specific, even with shared user profile tables.
Thanks Darren,
I hope this is something they’re looking into. It’s rather critical for me at least, if I can’t “trust” the behaviour of Roles.
@Darren_Murphy did you manage to find a solution outside of Make for this bug? Thought I was going mad for a minute today 
Seems like writing to a column that’s assigned as Role initially works, but the data doesn’t stick.
That’s actually separate to the bug I was referring to in my post above (which was fixed).
The behaviour that you are seeing is correct and expected. You cannot change a users Role via the front end. Well, you can - but Glide will change it back, as you’ve discovered.
The only way to do it is either manually in the Data Editor, or via the API.
This is actually documented behaviour.
Hi
I am trying to set up a Make scenario to be able to change roles in my app. I am doing as you suggest but still having an issue in the Make HTTP Request - I am getting an “Authentication” error.
Could you point me where to look for my mistake? Appreciate
After “Bearer” in the Authorization header, you should add your authorization key.
In addition to what Thinh said, you’re also missing the second header item for contentType.
Also, which HTTP module are you using?
I always use this one for Glide API calls 
Thank you both
I have my authorization key after Bearer (just redacted)
In terms of the second header for content type? I am not sure how to specify that?
I thought content type was specified in the Content Type field below Body Type? If not how do I specify in the Header Section please.
And yes I am using Make a request in the HTTP module
You’ll see it if you look at the curl example in “Show API usage”
Here is how that should look in the Make module:
Thank you I managed to get it working!
Quick question - I was initially using a Glide Action as the opening module in Make - I have changed to a Webhook.
It appeared to me that a Glide Action should be appropriate to change a Role column in the users table - why would it not be? Appreciate.
I’ve never used the Glide Make module. I always use a Custom Webhook.
If you’re talking about the Glide module in Make, I think it serves the same purpose as the webhook.
Thank you - I suspected so - but could not get it to work - the Make Custom Webhook did however and I end up using that option.
Thank you
Hi everybody!
I had some workaround with set User role thru API.
