DynaSys users

Different users have accesses to DynaSys, below is a global overview of the main roles.

Each GBU may have different roles. More details are available in the Wiki DynaSys GBU Corner pages :

User creation in DynaSys

• User scope and role

A User will have a Role and a Scope :

• the Role depends on his fonction and define which workspaces he can access
• the Scope defines which DF/data he has access to

Each user will have :

• one (or many) role(s)
• one (or many) scope(s)
• one profile (viewer, global planner…)

Each role/scope will be defined through a User Group.

The steps to create a new user are :

• Create User

Note : Avoid to re-use an old user for traceability/connection dashboard

• Create scope User group(s) 

Note : Don't duplicate User group to avoid to security

• Define security for the scope User group(s)
• Assign User group(s) to the new user

Each role is linked to :

• Workspaces,
• Shortcuts,
• Calculations
• Write/Read on models

The Security is set-up in the Workspace and the Forecast models.

The User group to assign a role to a user are generally defined during the project phase. No new user group for a role should be defined for a new user creation.

• User and type of access per GBU

When receiving a request for an access, the first step is to collect all required information :

• User Name
• Windows ID
• GBU
• Role (refer to list below)
• Scope (refer to list below)

A form needs to be completed by the user to collect all the information :

• User creation

User naming should follow the rule below :

GBU - User role / Name

Examples :

List of the GBU code is available here

The email of the user should also be registered in the External user name :

The available user types for the GBU users are :

• Global Planner for Demand /S&OP Planners
• Collaborator for Sales Manager
• Viewer for users who just need view access

Note : Do not give "Administrator" to GBU users, they would be able to get connected during the import processes

Administrator and Super user are for SBS users for system maintenance

• User deletion

When a user is obsolete :

• Rename the user with zzz before the user name
• Deactivate it

• User DynaSys server access

• The Server access is only required for Remote access.For Web access, no remote access is required.
• If a user needs a server access, send an email to : DynaSys.Interface.Team@solvay.com with the User Windows ID

• User Group mailing

New users should also be added in the corresponding Google group :

$DynasysUsersDP

$DynasysUsersDP2

$DynasysUsersDP3

If users are Key Users (=Demand planners), they should be also added in the following Google group :

$DynasysDP-KeyUsers

$DynasysDP2-KeyUsers

$DynasysDP3-KeyUsers

Switch user feature

This feature allows a user to switch to an other scope.

For example for a Sales Manager who is also a Global Key Account or a S&OP Planner who have different roles in the process.

• Switch user feature for user

On the opening page, the user is able to go on the shortcut session in order to change his role. You may not have the authorization to use this shortcut they are only for some users.

The option is also available on the Web portal :

• Switch user feature set-up

Macros/Shortcut are available to manage the different cases : 

The extension to be added to the user is defined in the macro :

When launching the macro, the macro will look for the user with the extension :

Note : For the Switch to Back-up, the user will be the user to switch to with the extension

To activate the feature for a new user  :

1) Create a new user (as deactivated) with the corresponding extension

For the Switch to Back-up, the new user should be the back-up user.

Note : if USER1 needs to access to USER2 for back-up, the user to be created is : USER2_BACKUP, then USER1 will have to enter "USER2" when switching to back-up to access USER2 profile

2) Update the User group of the new user to reflect the new scope(s)/role(s) he will have access when switching

For the Switch to Back-up, the new user should have the same User groups as the bakc-up user.

(USER2_BACKUP should have the same User groups as USER2)

3) Check that the user who need to have acces to the Switch user have access to the corresponding shortcut

DynaSys users

Silica 

• Demand Planner AP / EU / NA / LA

• Create the user :

  • Login : Windows ID

  • Description : SI - DP / First and last Name

  • External user name : eMail

• Assign the following user groups : 

  • dp - SILICA - EU (or AP, NA, LA)

  • SILICA - GBU

• Customer Service Rep. CSR 

• Create the user :

  • Login : Windows ID

  • Description : SI - CSR  / First and last Name

  • External user name : eMail

• Assign the user to following Role user groups 

  • SILICA - GBU

  • SILICA - Role CSR (for EU, AP, LA)

  • SILICA - Role CSR NA ( for NA)

• Create the Scope user group (DO NOT DUPLICATE AN EXISTING ONE)

  • Name : SI - CSR  / First and last Name

  • Assign to this user group the user created

  • Delete any other existing assignments copied from duplicata

• Create condition : 

  • Under table CSR

  • Name : SI - CSR  / First and last Name

  • Type : Filter applied to record codes

  • Selection mask : code of the CSR (Search in CSR table the name of the CSR you want to create, use his code in this field)

    • Add ^ at the beginning of the code 

      • add $ at the end of the code

    >>> this step should be done during a release.

• Update the security of master tables: “ CSR”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

• • Repeat this step for all master tables which are parents of “CSR” table (the most important one is : Material:Shipto@DC table)

Sales Rep. SREP

• Create the user :

• Login : Windows ID

• Description : SI - SREP  / First and last Name

• Assign the user to following user groups:

• SILICA - GBU

• SILICA - Role Sales Rep (for EU, AP, LA)

• SILICA - Role Sales Rep NA ( for NA)

• Create the user Group :

• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)

• Name : sr - LOGIN

• Assign to this user group the user created

• Delete any other existing assignments copied from duplicata

• Create condition : 

• Under table Sales Rep.

• Name : sr - LOGIN

• Type : Filter applied to record codes

• Selection mask : code of the SREP (Search in Sales Rep. table the name of the SREP you want to create, use his code in this field)

  • Add ^ at the beginning of the code

  • add $ at the end of the code

    >>> this step should be done during a release.

• Update the security of master tables: “ Sales Rep.”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

  • Repeat this step for all master tables which are parents of “Sales Rep.” table (the most important one is : Material:Shipto@DC table)

Global Shipto Key Account SHKA

• A user who is CSR or SREP can be also a SHKA (he will not be able to modify the SHKA scope)

• Create the user Group :

• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)

• Name : SHKA - ShiptoKAName

• Assign the user to the user group created

• Delete any other existing assignments copied from duplicata

• Create condition : 

• Under table Shipto KA 

• Name : SHKA - ShiptoKACode

• Type : Filter applied to record codes

• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code

  • add $ at the end of the code

  >>> this step should be done during a release.

• Update the security of only master table “Material:Shipto@DC ” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

For Modification Condition put Modify None

2.PEROX

Perox - Demand Planner AP / EU

• Create the user :
• Login : Windows ID
• Description : PE - DP / First and last Name
• Assign the following user groups : 
• DP - PEROX - EU (or AP)
• PEROX - GBU
• PEROX - Role Account Manager

Perox - Demand Planner NA

• Create the user :
• Login : Windows ID
• Description : PE - Demand Planner / First and last Name
• Assign the following user groups : 
• DP - PEROX - NA
• PEROX - GBU

Perox - Account Manager

• Create the user :
• Login : Windows ID
• Description : PE - Account Manager  / First and last Name
• Assign the user to following user groups:
• PEROX - GBU
• PEROX - Role Account Manager (for EU and AP)
• PEROX - Role Account Manager NA ( for NA)
• Create the user Group :
• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
• Name : PE - am - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Account Manager
• Name : PE - am - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the account manager (Search in Account manager table the name of the account manager you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

• Update the security of master tables: “Account Manager” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

Repeat this step for all master tables which are parents of “Account Manager” table (the most important one is : Material:Shipto@DC table)

Perox - Global Key Account Manager

• A user who is Account Manager can be also a GKAM of a specific zone 
• Create the user Group :
• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
• Name : GKAM - GBUShip-toGroupName - Zone
• Assign the user to the user group created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table GBU Ship-to Group 
• Name : GKAM - GBUShip-toGroupCode
• Type : Filter applied to record codes
• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

• Create condition : 
  • Condition GKAM - GBUShip-toGroupCode
  • AND
  • Condition Zone
• Under table Ship-to@BU 
• Name : GKAMxZONE - GBUShip-toGroupName Zone
• Type : Combined Condition 

>>> this step should be done during a release.

• Update the security of master tables: “Ship-to@BU” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before : GKAMxZONE - GBUShip-toGroupName Zone)
• Repeat this step for all master tables which are parents of “Ship-to@BU” table (the most important one is : Material:Shipto@DC table)

3.AROMA 

Demand Planner AP / EU / NA / LA

• Create the user :
• Login : Windows ID
• Description : PA - Demand Planner / First and last Name

• Assign the following user groups : 
• AROMA - Role Demand - Scope EU (or AP, NA, LA)
• AROMA - GBU

Sales Rep. SREP

• Create the user :
• Login : Windows ID
• Description : PA - SREP  / First and last Name
• Assign the user to following user groups:
• AROMA - GBU
• AROMA - Role Sales Rep
• Create the user Group :
• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
• Name : sr - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Sales Rep.
• Name : sr - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the SREP (Search in Sales Rep. table the name of the SREP you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

Update the security of master tables: “ Sales Rep.”  > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “Sales Rep.” table (the most important one is : Material:Shipto@DC table)

Global Key Account Manager GKAM

• A user who is SREP can be also a GKAM
• Create the user Group :
• Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
• Name : GKAM - GBUShip-toGroupCode
• Delete any other existing assignments copied from duplicata
• Assign the user to:
• the user group created
• AROMA - Role GKAM

• Create condition : 
• Under table GBU Ship-to Group 
• Name : GKAM - GBUShip-toGroupCode
• Type : Filter applied to record codes
• Selection mask : code of the GBU Ship-to Group (Ask the requester for the code)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code

>>> this step should be done during a release.

Update the security of master tables: “Material:Shipto@DC” > Right click > Security > Advanced security > go to user group line (created step before) and put the condition (created before : GKAM - GBUShip-toGroupCode)

• For Modification Condition put Modify None

4.SPECIAL CHEM

Sales Employee

• Create the user:
  • Name: Windows ID
  • Description : CH - DP / First & Last Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Employee

• Create the user Group :
  • Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name : CH – SE - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Complete the Sales Employee ID table * :
  • Under table Sales Employee ID
  • Records > Lock Data
  • Add a line:
    • Code: Solvay address mail
    • Name: First & Last Name
    • Short name: Windows ID

• Create condition* :
  • Under table Sales Employee ID
  • Name: SM – SE - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Solvay address mail

*This step should be done during a release

• Linking the Sales Employee to the Sales Employee ID
  • Under table Sales Employee
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her email address in all the lines of the "Sales Employee ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC table” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

Sales Assistant

• Create the user:
  • Name: Windows ID
  • Description : CH - SA / First & Last Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Assistant

• Create the user Group :
  • Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name : CH – SA - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Complete the Sales Assistant ID table* :
  • Under table Sales Assistant ID
  • Records > Lock Data
  • Add a line:
    • Code: Windows ID
    • Name: First & Last Name

• Create condition* :
  • Under table Sales Assistant ID
  • Name: SA – CH - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Windows ID

*This step should be done during a release

• Linking the Sales Assistant to the Sales Assistant ID
  • Under table Sales Assistant
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her Windows ID in all the lines of the "Sales Assistant ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

Global Key Account Manager (GKAM)

A user who is SREP can be also a GKAM

• Create the user:
  • Name: Windows ID
  • Description : CH - SE / First & Last Name

• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Assign the following user groups: 
  • CH – GBU
  • CH – Sales Employee

• Create the user group:
  • Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name: CH - GKAM - Name of GKAM Dimension
  • Delete any other existing assignments copied from duplicata
  • Duplicate an existing one, example : CH – SE - DCANGIAN
  • Name : CH – SE - Windows ID
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Assign the user to:

• The user group created CH - GKAM - Name of GKAM Dimension
• The user group created CH - SE - Windows ID

==> PART 1 : Sales Employee 

• Complete the Sales Employee ID table * :
  • Under table Sales Employee ID
  • Records > Lock Data
  • Add a line:
    • Code: Solvay address mail
    • Name: First & Last Name
    • Short name: Windows ID

• Create condition* :
  • Under table Sales Employee ID
  • Name: SM – SE - Windows ID
  • Condition type : Filter applied to record codes
  • Selection mask : Solvay address mail

*This step should be done during a release

• Linking the Sales Employee to the Sales Employee ID
  • Under table Sales Employee
  • Search for our user's lines
  • Records > Lock Data
    • Add his or her email address in all the lines of the "Sales Employee ID" section.

• Update the security of master tables:
  • “Material:Shipto@DC table” > Right click > Security > Advanced security
  • Go to user group line (created step before) and put the condition (created before)

==> Part 2 : GKAM

• Create condition* :
  
  • Under the table of GKAM Dimension example : Enterprise Customer Group, Enterprise Material Group …
  • Name: CH - GKAM - Name of GKAM Dimension
  • Condition type : Filter applied to record codes 
    • Update the security of master tables:
      
      • Right click > Security > Advanced security >
      • Go to user group line (created step before)
      • Put the condition (created before : CH - GKAM - Name of GKAM Dimension

*This step should be done during a release

Demand Planner

xxx

4.TECHNOLOGY SOLUTIONS

Sales Rep. SREP

• Create the user:
  • Name: Windows ID
  • Description : TS - SREP - Country code / Last & First Name
• User Properties:
  • Check “Collaborator”
  • Check “Account Enabled”

• Create the user Group :
  • Create the user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name : TS – SREP – Country Code / LAST & First Name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Under table Sales Employee ID
  • Name: TS - Country Code / LAST & First Name
  • Condition Type: Filter applied to record codes 
  • Selection mask : input the user's email address
  • Parent master table: Sales Employee ID

>>> This step should be done during a release... (Exclusive access needed!)

• Update the Sales Employee ID table, add the user's email address into the table and tick the related condition you just created in the previous step

• Update the security of master tables: “ Sales Employee”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)
• Repeat this step for all master tables which are parents of “Sales Employee” table (the most important one is : Material:Shipto@DC table)

RSD

xxx

PRICING TEAM

• Create the user :

• Login : Windows ID

• Description : TS - DP / First and last Name

• Assign the following user groups : 

• TS - Princing Team

DEMAND PLANNER

• Create the user :

• Login : Windows ID

• Description : TS - DP / First and last Name

• Assign the following user groups : 

• TS - DP- ...

PRODUCT MANAGER

5.NOVECARE

Sales Employee

• Create the user:

• Login: Windows ID

• Description: NOVECARE - SREP - Country Code / LAST and first name

• Assign the user to the following user groups:
  • NOVECARE - Sales rep (KG)
    
    

• Create the user group:

  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)

  • Name: NOV - SREP - Country Code / LAST and first name

  • Assign to this user group the user created

  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 

Under table Sales Employee ID

• • Name: NOV - SREP - Country Code / LAST and first name
  • Type: Filter applied to record codes
  • Selection mask: User email address (Search in Sales Employee table the name of the Sales Employee you want to create, use the email address in the corresponding field)

>>> This step should be done during a release.

• Update the security of master tables: “Sales Employee ID”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “Sales Employee ID” table (the most important one is : Material:Shipto@DC table)

Customer Service Rep. CSR

• Create the user:

• Login: Windows ID

• Description: NOVECARE - CSR - LAST and first name

• Assign the user to the following user groups:
  • NOVECARE - CSR

• Create the user group:

  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)

  • Name: NOV - CSR - LAST and first name

  • Assign to this user group the user created

  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 
  • Under table CSR
  • Name: NOV - CSR - LAST and first name
  • Type: Filter applied to record codes
  • Selection mask: code of the CSR (Search in CSR table the name of the CSR you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables: “CSR  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “CSR table (the most important one is : Material:Shipto@DC table)

S&OP Planner

• Create the user:

• Login: Windows ID

• Description: NOVECARE - S&OP Manager - Country Code / First and last name

• Assign the user to following user groups:

  • NOVECARE - S&OP Planner

• Create the user Group:
  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name: NOV - S&OP Manager - Country Code / First and last name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Add ^ at the beginning of the code 
  • Add $ at the end of the code
• Under table S&OP Planner
• Name: NOV - S&OP - Country Code / First and last name
• Type: Filter applied to record codes
• Selection mask: code of the S&OP Planner (Search in S&OP Planner table the name of the S&OP planner you want to create, use his code in this field)

>>> This step should be done during a release.

• Update the security of master tables: “S&OP Planner”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “S&OP Planner” table (the most important one is : Material:Shipto@DC table)

+ Link between S&OP Leader and S&OP Planner: Update the S&OP Planner table and assign the correct S&OP Leader to the correct S&OP Planner, depending on the zone.

S&OP Leader

• Create the user:
  • Login: Windows ID
  • Description: NOVECARE - S&OP Leader Mini Zone - Country Code / First and last name
  • Assign the user to following user groups:
    • NOVECARE - S&OP Planner

• Create the user Group:
  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name: NOV - S&OP Leader - Mini Zone / First and last name
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata

• Create condition: 
  • Under table S&OP Leader
  • Name: NOV - S&OP Leader - Mini Zone - First and last name
  • Type: Filter applied to record codes
  • Selection mask: code of the S&OP Leader (Search in S&OP Leader table the name of the S&OP planner you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables: “S&OP Leader”  > Right click > Security > Advanced security > Go to user group line (created step before) and put the condition (created before)

• Repeat this step for all master tables which are parents of “S&OP Leader” table (the most important one is : Material:Shipto@DC table)

Global Key Account Manager (GKAM) / Regional Key Account Manager (RKAM)

A user who is SREP can be also a GKAM 

• Create the user group:
  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name: GKAM - ShiptoKAName
  • Assign the user to the user group created
  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 

• Under table Shipto KA 

• Name: GKAM - ShiptoKACode

• Type: Filter applied to record codes

• Selection mask: code of the GBU Ship-to Group (ask the requester for the code)

  • Add ^ at the beginning of the code

  • Add $ at the end of the code

>>> This step should be done during a release.

• Create combined condition:
• Under table ShiptoKA
• Name: SHKA x Zone - ShiptoKAName Zone

exemple: SHKA x Zone - BERCEN NA

• Condition type: Combined condition
• Left operand: Add condition previously created
• Right operand: Zone Shipto - Zone

>>> This step should be done during a release.

• Update the security of the 3 master tables Material:Shipto/ Material:Shipto@BU / Material: Shipto@DC:

For each master table: 

• •  Right click > Security > Advanced security 
  • Go to user group line (created step before)
  • Put the condition 

>>> This step should be done during a release.

Regional Market Director (RMD) / Business Development Manager (BDM)

A user who is SREP or BDM can also be a RMD

• Create the user:
  • Login: Windows ID
  • Description: NOVECARE - BDM Market Name x Mini Zone First and last name
  • Assign the user to following user groups:
    • NOVECARE - RMD (KG)
    • NOVECARE - BDM (KG)

• Create the user Group:
  • Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)
  • Name: NOV - RMD Market Market Name - Mini Zone
  • Assign to this user group the user created
  • Delete any other existing assignments copied from duplicata
    
    

• Create condition: 
  • Under table XXX
  • Name: XXX
  • Type: Filter applied to record codes
  • Selection mask: code of the XXX (Search in XXX table the name of the XXX you want to create, use his code in this field)
    • Add ^ at the beginning of the code 
    • Add $ at the end of the code

>>> This step should be done during a release.

• Update the security of master tables:
  • “Material:Shipto@DC” > Right click > Security > Advanced security 
  • Go to user group line (created step before)
  • Put the condition 

>>> This step should be done during a release.

6.SA&D

Account Manager

• Create the user :
• Login : Windows ID
• Description : SD - Account Manager  / First and last Name
• Assign the user to following user groups:
• SA&D - GBU
• SA&D - Role Account Manager (Except NA, LA)
• SA&D - Role Account Manager (LA)
• SA&D - Role Account Manager (NA)
• Create the user Group :
• Create a new user group (DO NOT DUPLICATE AN EXISTING ONE)
• Name : SD - AM - LOGIN
• Assign to this user group the user created
• Delete any other existing assignments copied from duplicata

• Create condition : 
• Under table Account Manager
• Name : SD - AM - LOGIN
• Type : Filter applied to record codes
• Selection mask : code of the account manager (Search in Account manager table the name of the account manager you want to create, use his code in this field)

  • Add ^ at the beginning of the code 

  • add $ at the end of the code