Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I add an email Attribute to a second user account in Crowd which doesn't contain one? Edited

As administrators we are required to use an Elevated account, whereby we obtain a password from a vault to log into Crowd. However the elevated account that we use does not show the email address when creating that user in Crowd and as such we do not receive email notifications when tasks in Jira have comments added or are transitioned through a workflow. I was told I could use some Attributes to populate the email address, but this doesn't work either. I've used the 'otherMails' and the'mails' attribute but am still unable to receive email notifications.


1 answer

0 votes
Bruno Vincent Community Leader Apr 25, 2020

Hi @CostaM 

Why doesn't the elevated account have an email address?

You mentioned the 'otherMails' attribute which is not a Crowd attribute but an Azure AD one so my assumption is that you connected Crowd to Azure AD and that the elevated account is actually an Azure AD account. That would explain why your elevated account does not have an email address. As a matter of fact only Azure AD users with an Exchange Online mailbox have a 'mail' attribute (which is mapped to the 'email' attribute in Crowd).

If my assumption above is true then you should create the elevated account in a Crowd internal directory, not in Azure AD. The elevated account would actually have an email address because it is a mandatory attribute for users in Crowd internal directories.

Hi @Bruno Vincent 

thanks very much for your reply, I will take this back to the team and see if we can apply it.

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

108 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you