goAML Duplicate User Profile: What Should a UAE Business Check Before Creating Another User?

A UAE business may need to add another employee or compliance team member to its existing goAML organization. Before creating a new user profile, however, it is important to check whether that person already has a goAML profile associated with the organization or a previous employer.

A goAML duplicate user profile can create confusion when an employee tries to register again using the same personal details, particularly after changing roles, employers, or responsibilities.

The UAE Financial Intelligence Unit (UAEFIU) distinguishes between organization registration and person registration. An organization is registered first, and additional internal users can subsequently register as a Person under the same Organization ID (Org ID). The organization's admin user, normally the MLRO/Compliance Officer, then reviews the additional-user request.

What Is a Duplicate User Profile in goAML?

A duplicate user profile generally refers to a situation where a person attempts to create another goAML user profile even though an existing profile or access record may already be associated with that individual.

This can happen when:

• An employee forgets that they already registered.
• A user changes their role within the same company.
• An employee moves from one UAE company to another.
• A previous employer has not deactivated the person's old access.
• A user attempts to register again instead of resolving an existing profile issue.
• An organization administrator assumes that every new employee requires a completely new organization registration.

These situations should be handled differently.

The important distinction is that adding another user to an existing organization is not the same as registering a new organization.

Organization Registration vs Person Registration

This is the first thing a UAE business should check.

The UAEFIU FAQ explains that the Register as an Organization option is used when an organization registers on goAML for the first time. After the organization is active, the reporting entity can allow internal users to register by selecting Register as a Person.

Therefore, if your company already has an active goAML organization, an employee who needs access should generally be considered as an additional user under the existing Organization ID rather than creating another organization profile.

The Org ID is assigned to the organization after successful registration and is included in the goAML approval information.

Why Should Businesses Check for an Existing User First?

Creating another profile without checking the person's existing access can make user administration more complicated.

Before starting another registration, the organization should establish:

1. Whether the person has previously registered on goAML.
2. Whether the person is already connected to the same organization.
3. Whether the person previously worked for another reporting entity.
4. Whether an old user account needs to be deactivated.
5. Whether the person actually needs a separate user profile.
6. Whether the organization's admin user has already received a pending request.

This is especially important when employees move between compliance roles or employers.

How Does an Additional User Registration Work?

According to the UAEFIU's current FAQ, adding an additional user under an existing entity involves several stages.

The new user first registers through the e-services portal (SACM) to obtain access to the network. After the regulator approves the SACM pre-registration, the user receives the necessary SACM credentials and security key.

The user can then access the network and goAML and register as a Person under the same Org ID.

The organization's admin user, normally the MLRO/Compliance Officer, then approves the new user request.

This means that a new employee does not simply create an independent organization profile for the company.

What Should You Check Before Creating Another User?

1. Check Whether the Person Already Has a goAML Profile

Ask the employee whether they have previously registered on goAML.

This is particularly relevant if they have worked for another reporting entity in the UAE.

If they already have a profile, creating another registration without resolving the previous access may not be the appropriate solution.

2. Confirm the Correct Organization ID

If the company already has an active goAML account, confirm the organization's Org ID before the person registers.

The additional user should register as a Person under the existing entity's Org ID.

Using the wrong Organization ID can lead to the request being associated with the wrong entity.

3. Check Whether the Employee Previously Worked for Another Employer

An employee may have previously used goAML with another company.

The UAEFIU FAQ specifically addresses users who have switched employers. In such cases, the previous access may need to be deactivated before the person can register again with the new employer.

Therefore, a previous employer relationship should be checked before assuming that the person simply needs a new profile.

4. Check for a Pending User Request

A duplicate-looking situation may actually be an existing registration request that has not yet been approved.

The UAEFIU states that when a person registers under an entity's Org ID, the organization's admin user—usually the MLRO/Compliance Officer—approves the additional-user request.

Before registering again, the organization should therefore check whether the original request is still pending.

5. Confirm Whether the User Really Needs Separate Access

Not every employee should automatically receive the same level of access.

The UAEFIU explains that goAML has predefined roles for the organization's admin user and organization users, and the organization's admin can assign roles and access rights.

The organization should therefore determine:

• Who needs goAML access?
• What responsibilities will the person have?
• Which role is appropriate?
• What information or reporting functions should the user access?

What If the User Already Worked for Another UAE Company?

This is one of the most important situations to review.

Suppose an employee previously worked as an AML professional at Company A and now joins Company B.

The employee may already have goAML-related access associated with the previous employer.

In this situation, the employee should not simply assume that registering repeatedly will solve the problem.

The UAEFIU FAQ advises users who have switched employers to contact the supervisory body to deactivate the previous access so that they can register again with the new employer.

The organization should therefore identify the previous access issue first.

What If the Person Is the New MLRO?

A new MLRO or Compliance Officer is handled differently from an ordinary additional-user request.

The UAEFIU explains that the organization should appoint the new MLRO/Compliance Officer/Contact Person and obtain the relevant regulator approval before the new person registers under the same Org ID.

The regulator then handles the required activation/deactivation process for the old and new MLRO access.

This is why businesses should not treat a new MLRO change as simply creating a second ordinary user profile.

What If the User Is Already Registered Under the Same Organization?

If the employee already has an active user profile under the same organization, creating another profile may be unnecessary.

Instead, the organization should first determine whether the existing user account can be used or whether the user's details or role need to be updated.

The UAEFIU FAQ states that users can update their own details through My goAML → My User Details, while organization details are managed separately through My Org Details.

This distinction helps prevent businesses from creating duplicate profiles simply because some information has changed.

Duplicate User Profile Checklist

Before creating another goAML user, a UAE business should review:

• Does the employee already have a goAML profile?
• Is the employee already registered under this organization?
• Does the company have an active Org ID?
• Is there already a pending Person registration request?
• Did the employee previously work for another reporting entity?
• Does the previous employer need to deactivate the old access?
• Is the employee joining as an additional user or as a new MLRO?
• Does the employee need separate goAML access?
• What role and access rights should the user receive?
• Has the organization admin reviewed the request?

Common Mistakes to Avoid

Creating a new organization instead of adding a user

An employee joining an existing reporting entity does not normally need to create a new organization registration.

Registering repeatedly when a request is pending

If the first Person registration is still awaiting admin approval, creating another request may not solve the underlying issue.

Ignoring previous employer access

A previous goAML profile can matter when an employee changes employers.

Giving every user the same access

The organization's admin can manage user roles and access rights, so businesses should assign access according to the person's responsibilities.

Treating an MLRO replacement as a normal user addition

The UAEFIU has a separate process for changing the MLRO/Compliance Officer, including regulator approval and deactivation/activation steps.

When Should a Business Seek Support?

If the organization cannot determine whether a person already has an active profile, has changed employers, or cannot proceed with a new Person registration because of an existing access record, it is better to resolve the existing profile situation rather than repeatedly submitting new registrations.

The business should keep the person's relevant registration information and organization details available when contacting the appropriate supervisory body or goAML support channel.

The UAEFIU provides official support and guidance for goAML registration and account-management issues, including additional-user registration and employer changes.

Frequently Asked Questions

Can a UAE company have multiple goAML users?

Yes. The UAEFIU provides a process for adding additional users under the same organization. Additional users register as Persons under the organization's existing Org ID, after which the organization admin reviews the request.

Should I create a new organization if another employee needs goAML access?

No. An existing reporting entity can add internal users under its existing organization. The UAEFIU distinguishes organization registration from Person registration for additional users.

What if the employee already used goAML for another company?

The previous access may need to be deactivated before the person registers with the new employer. The UAEFIU specifically advises users who have switched employers to contact their supervisory body regarding deactivation of previous access.

Who approves an additional goAML user?

The organization's admin user, normally the MLRO/Compliance Officer, approves additional-user requests under the organization's Org ID.

Can the organization control what an additional user can access?

Yes. The UAEFIU FAQ states that the organization's admin can assign user roles and access rights through the goAML user-role management functions.

Conclusion

A goAML duplicate user profile should not automatically be treated as a reason to submit another registration.

Before creating another user, a UAE business should check whether the employee already has a goAML profile, whether a previous employer still has active access associated with the person, whether a Person registration request is already pending, and whether the employee should be added under the company's existing Org ID.

For an ordinary additional user, the UAEFIU process is based on registering as a Person under the existing organization and obtaining approval from the organization's admin user. Different handling applies when the person is replacing an MLRO or moving from another employer.

A careful check before creating another profile can help the organization avoid unnecessary duplicate registrations and keep its goAML user administration organized.