Thanks Jim, for the database I’m working on I might be able to get by with a couple of checkboxes that represent groups and not really have a groups table. I’m planning to have all of the database users in a users table and to authenticate against that and to also verify that there is a matching 4D user in the structure and to automatically create one if necessary. BTW: the main benefits of having the users in the table is that I need to record a user ID to certain records that have been created and I need user initials and when new structure is delivered the credentials are all in place. Oh, and if I decide to implement SSO I already have a Windows_ID field ready to go. So, I’m trying to keep it simple. I’ve never tried to do to this way, I call it a hybrid approach since it uses table and structure based resources. Any ideas on ways to keep it simple are appreciated.
Robert > On Nov 14, 2018, at 3:39 PM, Jim Labos - infobase via 4D_Tech > <[email protected]> wrote: > > We roll our own mostly. Using a list of available "action". Each user then > either has or has not permission for the "action". ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
