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
  • Community
  • Products
  • Crowd
  • Questions
  • Can *JIRA* administrators add users to Crowd and add them to a *Confluence* group? Or do you have to be a Crowd administrator to do that?

Can *JIRA* administrators add users to Crowd and add them to a *Confluence* group? Or do you have to be a Crowd administrator to do that?

Following scenario: One Crowd server, three JIRA servers connected to it and six Confluence instances. If you are an administrator on ANY of those connected applications, it would appear that you can a) add new users to Crowd and b) add them to groups that have NOTHING to do with the application that you are an administrator for.

1 answer

1 accepted

Yes, so long as the default directory they are creating a user in is connected to all of those instances. All groups are pulled in directly from Crowd across all instances because they don't know what's restricted to them.

If you'd like to limit this, you could add a new directory. Additionally, you should be able to limit the LDAP filter for each instance it touches to help refine as well: https://confluence.atlassian.com/display/CROWD/Restricting+LDAP+Scope+for+User+and+Group+Search

Thanks for your response but the bit I dont understand is the level of permission you require to add yourself to a group.
I would have thought that you neede Crowd admin permissions to add a new user in Crowd, not just a Jira admin.

Essentially what Crowd-administrator does is lets you modify/access the Crowd Administration console directly. I can see why you would feel like its sort of backwards, but the way that the Crowd directories work is that if you connect it to JIRA or Confluence, and you are a in the jira-administrator role, you should be able to create the same way as you would have. It all depends on the directory configuration.

There are ways to break this, which you can search for, but I wouldn't suggest it if you're trying to lock it down that way.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

181 views 6 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