I have added a public HTML "start page" in a private application with multiple views and forms. The start page has logic to share certain views and forms based on the ZOHO account email of a signed-in user (the logic criteria references emails in a "roll list").
I have verified that the share operation not only places a user on the application's share context (for views/forms/etc) but also places the user into the "Account Settings/Manage Users". So it's true that sharing can quickly fill-up the available seats on whatever ZOHO Creator subscription plan you have. Why? Because the unshare operation does not remove the user from the Account Settings/Manage Users list, only from the application's share context. This defeats the whole idea of dynamic sharing for my customer's application. This is a matrix organization and roles change often. I wanted to grant users the ability to control these roles from within the application.
Share/unshare in its current implementation is half-baked
. If we can share users on the fly, why not unshare them with similar simplicity?
And what happens if all the account seats are filled and the code tries to add another shared user? You get:
PS: Note the spelling error in the error details above
John M. Whitney