Share
Report adding new user to dynamics gp
*This post is locked for comments
You’re offline. This is a read only version of the page.
99
*This post is locked for comments
To add to what has already been stated:
The SecurityPlanning.pdf file, in the Documents directory where your Dynamics GP application is installed, goes over giving users permissions to do these type of things if you want GP users other than sa or DYNSA to be able to create and modify users.
Chapter 7 in this guide goes over 'Core application security tasks' which include:
• Creating user records
• Deleting user records
• Granting user access
For example, under 'Creating user records', it gives the following options:
1. Login to Dynamics GP as 'sa'.
2. Assign the GP login the SysAdmin fixed SQL Server role (the equivalent of the sa login) and also the DYNGRP role under the DYNAMICS/system database.
3. Login to Dynamics GP as 'DYNSA', the database owner, which should be assigned the SecurityAdmin fixed SQL role.
4. Assign the GP user to the SecurityAdmin fixed SQL Server role and also the DB_Owner database role for the DYNAMICS system database. (DYNSA must be the db owner for all GP databases).
5. Assign the GP user the SecurityAdmin fixed SQL Server role as well as the DB_AccessAdmin and DB_SecurityAdmin database roles for the DYNAMICS system database. (DYNSA must be the db owner for all GP databases.)
As a test, I went into SQL Server Mgmt Studio, in the properties of my new PowerUser user I created in GP, under 'Server Roles' I marked 'SecurityAdmin', then under 'User Mapping', I highlighted the DYNAMICS system database and marked the DB_AccessAdmin and DB_SecurityAdmin database roles, clicking OK to save changes.
Back in Dynamics GP, the User Setup window now has the Password and Confirm Password fields enabled.
Thank you
Hi,
As Jeffrey stated, you need a user with SQL Admin rights. I have had a scenario with a client where they did not want anyone to use the sa and DYNSA account to do day to day GP admin work. They wanted a proper named user for that. They had to create a user in the steps as mentioned by Jeffery then had to go to SQL Management Studio and then assign Admin rights to the SQL user that was created from within GP.
Don't worry about SQL security because the SQL user who is created from GP will not be able to login to SQL via Management Studio because GP encrypts the password before saving it to SQL.
Hi Terry
You will need either the 'sa', DYNSA or a user account that has SQL admin rights to do this.
With Dynamics GP, click on Microsoft Dynamics GP > tools > setup > system > user
Fill in the information and click on save
Next go to Microsoft Dynamics GP > tools > setup > system > User Access
Assign the user to the companies that they should have access to.
One final step, go to, Microsoft Dynamics GP > tools > setup > system >User Security
Select the user and a company. Mark the boxes next to the role(s) that the user should have.
If the user has the same roles in multiple companies, click on Copy on the top menu and mark the companies to give the user the same security rights in those companies.
#1
Almas Mahfooz
3
User Group Leader
All responses (
Answers (
