I understand that when we setup a new user, they are added to primary company database, such as "TWO", and they are put into the correct group with the appropriate rights, such as the DYNGRP.
But, we have another database on the server that holds some functionality, such as stored procedures and tables, that are used for some integration and extensions within the GP company database. I have the DYNGRP role inside this second db (we will call it "THREE"), and have set all the appropriate rights in the "THREE" db for the role DYNGRP.
What I would like to be able to do is either automatically assign the users rights to this second, non-company db, when a new user is added or give an option in the setup screens for the new user. Right now in the setup we only see the single company database, "TWO".
One option that I am entertaining is adding a SQL step to the job "Remove Posted PJOURNALs From All Companies", that will query "TWO" database and compare users to what is in the "THREE" database, and sync up users that may be missing.
What I don't want to do is require IT intervention when a new user is added to GP. Assume that we cannot integrate the "THREE" database into the GP "TWO" database.
I am open to some other options.
Thanks,
Jeff