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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Crowd: User invite/onboarding flow with other products (Jira, Confluence, Bitbucket)

Hi,

we have a full Atlassian stack (Jira, Confluence, Bamboo etc) and user management is done via Crowd.

I would like to know what the supposed/designed workflow is if we want to onboard a new user which should only use some of the products but not Crowd itself.

What we are currently doing:
1) Create the user in crowd with all necessary details and a temporary password
2) Add the new user to all desired groups
3) Click the password reset page, which will send a password change link to the user via mail
4) The user gets to a password change dialog and changes the password (up until here this is fine)
5) (The problem) After successfully changing the password, the User is directed to the Crowd login page, where he has no access (we obviously do not allow all users Crowd access) so if the user now tries to input their new credentials they will fail and with a "username/password wrong" error message

Now, while this is all clear and expected from a technical perspective, it is quite bad UX and has lead to confusion ("I changed my password but now I can not log in!") in the past, So I would be interested if we are missing a "right" way.. If we would only use Jira without Crowd I believe there is a proper invitation workflow? Also, we have users which are allowed to f.e. Bamboo for deployments but not into Jira, so having a password change option in Crowd is great, it's just that everything after is very confusing?

1 answer

How exactly do you prevent users from Crowd access?

Is there a group-based restriction in "Directories & Groups" on your main user directory mapping in Crowd applications set on Crowd Console itself?

Is there actually any reason to prevent users from Crowd access? After all unless they are admins in Crowd they only get a very basic profile-like portal that would allow them to view their own info, change password etc.?

Suggest an answer

Log in or Sign up to answer
TAGS
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...

78 views 0 4
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