Forum Discussion
It would use the original HTTP API, with the most applicable being API_UserRoles. It returns the full list of users in their roles for that particular app. I was incorrect though, I thought it captured their status but doesn't. You could set this to target users with a role of 'none' and remove them using API_RemoveUser.
All of the above could be done with Pipelines using the Quickbase / Request Channel where you invoke a QB specific API call, the rationale is that they will convert their own XML into JSON format to use. If you have access to it - you could also consider syncing the QB realm information and for any denied user in the user sync table just remove their access the same way with a pipeline search and remove user api call.
------------------------------
Chayce Duncan
------------------------------
Hey Chayce,
Do you have documentation for the api_removeUser? I searched and only found api's which remove users from groups, or change a user's role. I didn't find anything on removing a user from an Application however
------------------------------
QuickBase Administrator2
------------------------------
- ChayceDuncan3 months agoQrew Captain
That's my bad - responding without actually looking up the right name. The actual API call is API_RemoveUserFromRole
------------------------------
Chayce Duncan
------------------------------- ShaneMiller13 months agoQrew Cadet
Just read that doc, really cool! I'll be playing with this. Thank you
------------------------------
Shane Miller
------------------------------