I was looking at the api endpoints documentation, but could not find it:
I’d like to deactivate users via the api. This way, I can deactivate their access to a portal based on various conditions in my database.
I was looking at the api endpoints documentation, but could not find it:
I’d like to deactivate users via the api. This way, I can deactivate their access to a portal based on various conditions in my database.
Don’t have it yet, my friend.
I’ve suggested it to the team to see if we can get something in the future. You could also try to turn off your caching so changes made in your DB reflect instantly? This could slow your application though.
I’m aware it’s not there yet, that’s why I raised this feature request to check if there’s more demand for this from the community
I’m afraid I don’t understand completely what you mean by turning of the cache in this context? I’d would like to keep formerly active users in my AT database, but not counting as as an active Softr user. I can do this manually, but was looking for an automated solution via a possible api endpoint.
@stenkate did you consider changing user group defining attributes putting them into limited group instead ?
Thanks for thinking along
I did and use a specific group defining attribute to limit options for them in the automation backend and Softr portal. But for this specific group I’d like to keep the data in the database, but just deactivate them for the portal so they also don’t count within the plan’s user limit.