AbduS.O00000bJ4Du.20260116013244 (Partner) asked a question.
In RSA G&L, what is the supported way to automatically handle username collisions for HR‑driven Joiner/JML provisioning into LDAP, similar in outcome to SailPoint’s Generator? Should Naming Policies, Account Templates, or Transforms be used?
I'm not familiar with how this is done in Sailpoint, but in RSA G&L, you can use the configurations you mentioned (Naming Policies, Account Templates and transforms) to automate the creation of new accounts in target systems.
In the application config you can define an account template.
The account template can be configured with a naming policy
A naming policy can be configured with a transform (if needed).
Once everything is configured, when you request access to this application for a user that doesn't has an account, the system will generate additional change item (in the change request) to create an account, and only then add the requested access to this account.