Issue Summary

If a user is already part of the site and joins another product via the settings defined in the "user access settings" then an email notification is triggered to the org admin stating <username> has just joined https://<site-name>.atlassian.net in <org-name>. They have access to the following products:

• Product A
• Product B
• Product C

The above notification is confusing because if the user has joined the site previously and joins another product then the email notification trigger should not state "user has joined the site"

The correct statement should be "user has joined the below products" 

Email notifications triggered are also inconsistent. Please refer examples as below:

Let's say we have the below access configured under an approved domain in user access settings with the option to "notify org admin" checked whenever the user joins the product

User- Group-ProductAccess Mapping:

Email notification examples sent to org admin:

Example 1:testuser1@approved-domain.com:

• The above user did not have any existing product access
• User logs in the id.atlassian.com
• In the browser user hits the URL: https://xyz.atlassian.net/
• User joins the product

Email Notification:

Subject: testuser1 has joined <org-name>

Body:
testuser1 has joined <org-name>

Hi <org-admin>,

testuser1 (testuser1@approved-domain.com) has just joined https://xyz.atlassian.net in <org-name>. They have access to the following products:

• Jira Software
• Jira Service Management
• Jira Work Management
• Confluence

Observation:

The above email notification delivers the correct message because the user has not joined the site yet. It therefore makes sense to have statement "<user> has just joined the <site>"

The issue observed in the above Example:

• Atlas was added to the site xyz.atlassian.net and is configured under user access settings but we don't see Atlas product added to the list of products in the email notification sent

Example 2:testuser2@approved-domain.com:

• The above user has access to Confluence user role
• User logs in the id.atlassian.com
• In the browser user hits the URL: https://xyz.atlassian.net/
• User joins the product

Email Notification Triggered:

Subject: testuser2 has joined <org-name>

Body:
testuser2 has joined <org-name>

Hi <org-admin>,

testuser1 (testuser1@approved-domain.com) has just joined https://xyz.atlassian.net in <org-name>. They have access to the following products:

• Jira Software
• Jira Service Management
• Jira Work Management

Observation:

The above email notification delivers the incorrect message because the user already has joined the site. It therefore does not make sense to have the statement "<user> has just joined the <site>". 

The issue observed in the above Example:

• Atlas is not seen in the list of products
• Incorrect email notification

Example 3:testuser3@approved-domain.com:

• The above user has access to Jira user role
• User logs in the id.atlassian.com
• In the browser user hits the URL: https://xyz.atlassian.net/wiki
• User joins the product

Email Notification Triggered:

Subject: testuser3 has joined your Confluence

Body:

testuser3 has joined Confluence
Hi <org-admin>,

testuser3 (testuser3@approveddomain.com) has just joined Confluence (https://xyz.atlassian.net) in <org-name>.

 
Observation:
The above email notification delivers the correct message because the user already already has access to the site. It therefore delivers the correct message. However, as compared to Example 2 the email message is inconsistent

The issue in the above Example:

• Atlas is not seen in the list of products
• Inconsistency in email message when compared to Example 2

Issues observed:

• Atlas products should be visible in the list of products
• If the user has already joined the site then the org admins should not be sent email message stating "user has just joined the site"
• To maintain consistency with different email messages. (Compare Example 2 and Example 3)

Customers Concerns:

• Current notification is misinformative and incorrect. For example: the information which indicates user has just joined ** even when the user already exists is quite clearly wrong.
• When notifying admins of product access, we shouldn't be misinformed about what access the user has at that point in time, we are told only half the story which is a security concern

Steps to Reproduce

1. Add Atlas, Jira Software, Jira Service Management, Jira Work Management and Confluence to your site
2. Configure user access settings and provide access to users when they join the site/product. Check the option to notify the org admin
3. Provision 3 users and assign no group to user1, Jira access group to user2 and Confluence user access to user3
4. Login with user1, user2 and user3 one by one and join the site. When the site is joined observe the email notification triggered.

Expected Results

• Correct email notification message with the correct list of products to be sent to the org admin.
• Atlas product to be added to the list of products

Actual Results

• Inconsistent email notification message stating "user has just joined the site"
• Atlas product not added to the list of products

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available