Is there a safe way to manage groups and users within a solution? I thought about accessing the repository as a dataprovider, but didn’t want to have anything conflict with servoy itself.
Basically, we’re creating an employee roster. The information (in a solution-based table) will be linked to the servoy repository user ID and name.
What we’d like is to be able to show all servoy users / all servoy groups / and permutations of each within a solution. These would all be READ ONLY from the repository (ie, method based for add / delete / add to group, etc, rather than type-in fields directly to the repository database)
I know that you can script adding users and managing groups, just not sure the safest way to display such from the repository.
Departments / workgroups would groups, so that more information on the group could be recorded. Also, if a user was added to a workgroup, they would be added to all parent groups above that - department, company, etc.
Should I just duplicate the user info in a solution based table, or is there some safe mechanism or technique to access the repository user / group tables within a solution?
Thanks for any insight or methods to use!
Nolan M.
FSCI
Hi Nolan,
You can easily read/write all the information about users and groups using methods (in the “Security” node in the left side tree in Tools → Editor).
Also, remember that users and groups are PER REPOSITORY and not PER SOLUTION.
If I’m going to have extensive privileges within my solution, then it’s easier to just have your own user/group tables. The built-in security is great for basic stuff, but I think you’ll find that you have a lot more control with your own tables.
As for reading stuff out of the repository directly - you CAN, but DO NOT write back to it - or you can REALLY mess things up in a hurry.
Hope this helps.
That’s what I wanted to know…so no fiddling with repository data outside of Servoy 
If creating our own tables and groups within the solution, then as I understand it we’d also have to recreate all the security features on our own. How is that easier? Maybe I just don’t see an easy way to do that down to the element level.
I think we’ll use the Servoy users and groups, and just have a User Info and Group Info tables (tied to servoy user id and group id’s) in the solution for extended information. That way we can use the built in servoy security, while using methods to talk back to the repository.
Now to go write the user / group manager form and script.
Nolan M.