Jan 3rd, 2015, 11:05 AM
I know this thread is old (2013), but wanted to comment that the "Editor Client" ability would be fantastic to have.
For a current Form Tool project, there will be an initial 50 clients, with a potential for quite a few to be added later. None of those clients will be given the ability to edit or change their core client data themselves. As the developer, I don't want to spend my time adding/editing etc. all those client accounts. My thought was to create a Super User account who has the ability to add/edit/delete other (non-Administrator) client accounts, but I don't want that user to have full Administrator ability. The idea of the "Editor Client" as described in this thread would be a good solution.
The hack described above in this thread will have to suffice for now, even tho' it gives more permission to my Super User than I would like.
For a current Form Tool project, there will be an initial 50 clients, with a potential for quite a few to be added later. None of those clients will be given the ability to edit or change their core client data themselves. As the developer, I don't want to spend my time adding/editing etc. all those client accounts. My thought was to create a Super User account who has the ability to add/edit/delete other (non-Administrator) client accounts, but I don't want that user to have full Administrator ability. The idea of the "Editor Client" as described in this thread would be a good solution.
The hack described above in this thread will have to suffice for now, even tho' it gives more permission to my Super User than I would like.