When VUD is enabled the access on company/company group level is delegated to VUD; the rest of the settings (access groups, access group member, layout groups, layout groups member and modules) also delegated to VUD during Export to VUD. We can add role/module assignment from Visma.net to Visma User Directory once Visma.net connection is established.
Visma Business
You can assign/remove the modules to the user according to the license
Visma User Directory
VUD just a gateway to Visma Business and Visma.net. Assign/remove modules not handled in VUD.
Visma.net
Visma Business
Same function as before.
Visma User Directory
You can create/edit/delete access group. You can assign/remove the access group to a user/user group.
Visma.net
Visma Business
You can create/assign/remove the layout group to the user
Visma User Directory
VUD just a gateway to Visma Business and Visma.net. Assign/remove layout group not handled in VUD.
Visma.net
A role shared by multiple application types in Visma User Directory will be split into corresponding roles for each application type. In order to preserve the uniqueness of the name, the new roles' names will be prefixed with the application type name. For example: Accountant that previously was enabled for Visma Reporting, Visma Business and Visma Document Center will now be split into 3 "Organisation roles". These three roles will have new VudStaticIds. The new VudStaticIds will be updated in Visma Business when upgrading Visma Business.You can see this difference in VUD management console under company group , tab roles.
A new column has been add in Layout group table to get VUD static ids from Visma User Directory. You can see this in VUD management console under application instance/server roles.
The connection to Visma.net is also stopped during this upgrade. Koble til Visma.net need to be established again.