On this page:
Overview
Now is the time to plan your security setup for Microsoft Dynamics GP 10.0! There are several changes to security setup in Microsoft Dynamics GP 10.0 that you need to take into account when planning security setup for your company. Please review the information below to become familiar with the security changes in Microsoft Dynamics GP 10.0.
Top
New Features in Release 10.0 Security
1.Security for new users is moving from optimistic to pessimistic. This means all new users created in Release 10.0 will not have access to anything in the system. Security access will need to be granted.
2.Security will be role based and consist of Security Operations, Tasks, and Roles.
Security Operations: A base level element of security, such as window, report, table, posting permission, document access, customization tools, letters, SmartList queries, etc.
Security Tasks: A group of operations (from many dictionaries) that are needed to accomplish a business task (Examples: Enter Customers, View Customers, Enter Sales Transactions, etc.)
Security Roles: A group of tasks that define a particular job in a company. Multiple roles can be assigned to a user to define what a particular user actually has access to in the application. Therefore, assigning a user to one role can grant access to thousands of security operations across many dictionaries.
3.Approximately 400 tasks and approximately 36 default roles will be shipped with Release 10.0.
4. When a new user is granted access to a company, they are granted the needed access to login to the company without error. The new user is also automatically assigned to the DEFAULT USER task to grant access to those items all users typically have. This task can be changed at any time.
5. A POWERUSER role is created to have the ability to access everything in the system.
6. Security for alternate/modified forms and reports will be in a separate location. When assigning users a role, you will also be required to assign an alternate/modified forms and reports ID to that user. This will allow them to open up windows in Microsoft Dynamics GP. A DEFAULTUSER ID for alternate/modified forms and reports is available to give users access to the alternate/modified forms and reports needed for the Microsoft Dynamics GP and all sub-features installed. If an integrating product alters a window, this area can be used to grant users access to that alternate/modified form. If you want all users to see the same alternate/modified forms and reports, it is recommended to setup one ID and assign that ID to each user.
7. Security reporting has been improved. You can easily run a report to show what users have access to. Here are list of reports available:
a. Security Task Setup
b. Security Role Setup
c. Security Role Assignment
d. Security Task Assignment
e. User Security
f. Unassigned Security Operations
g. Advanced Financial Report Security
h. Alternate/Modified Forms and Reports Setup
8. The security API is available for ISV's to integrate.
Top
Discontinued Security Components
1. The existing Security Setup window (Tools | Setup | System | Security) and Advanced Security setup window (Tools | Setup | System | Advanced Security) no longer exist.
2. The existing User Class setup window (Tools | Setup | System | User Class) will remain, however, the security setup in that window no longer exists.
3. The existing SmartList Security setup window (Tools | Setup | System | SmartList Security) no longer exists.
4. The Security Restrictions Table (SY02000) and the Class Restrictions Table (SY40300) no longer exist in the DYNAMICS database.
Top
Security Conversion
1. A window will be added to Release 10.0 Utilities to accommodate the security conversion. This is an optional conversion. If you choose not to convert your existing security, users will NOT have access to anything in Release 10.0.
2. All security setup from Release 8.0 and Release 9.0 will be converted during the update to Release 10.0 as long as ALL of the dictionaries are present in the Dynamics.set file at the prior release. For example, if you use Human Resources and Manufacturing and are updating from Release 9.0, those products must be installed at the 9.0 level prior to updating to Release 10.0.
2. For any dictionaries that are missing, you will be informed and can either continue or exit the update. If you choose to continue with missing dictionaries, the security for those dictionaries will NOT be converted and users will have access to NOTHING in those dictionaries by default.
3. For every user/company combination the security conversion will:
a. Create a task containing all of the security setup for that user/company. For example, Task ID = "LESSONUSER1TWO"
b. Create a role with the same name and assign the above task to it. For example, Role ID = 'LESSONUSER1TWO"
c. Assign this role to the user in this company.
d. The same process will happen for all modified forms and reports.
4. Users should be able to use Release 10.0 immediately after the update. The administrator can change the security setup in Release 10.0 following the update or at their own pace.
Top
Support Information
For technical support questions, log on to Microsoft Business Solutions Support and enter a New Support Request. Please choose SYSTEM MANAGER-SQL as the subcategory selection.
You can also contact InterDyn Business Microvar Technical Support by phone at 651-639-0575 or 1-866-264-3249.
Top |
