Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,170
Community Members
 
Community Events
184
Community Groups

Recommended Directory / Group / Permission for Super Admins in an Atlassian Suite

Hello,

 

I have setup Crowd, and have integrated this with Stash. I will be deploying and integrating Crowd with the other apps in the Atlassian Suite as well (Crucible, Jira, Confluence, Bamboo, a few custom apps, etc). Crowd will be used for SSO, 2FA, and to simplify managing users across the suite of apps.

 

I think it is relatively clear how to setup users/groups/permissions for the regular users.. I am planning on a Directory for all company users, and groups to delegate permissions for authenticating with each app.

 

Here is where I get less certain, and where I would appreciate insights from your experience: What is a recommended setup for managing administrative access to each of these apps?

 

1) Should I ensure a Super Admin User exists in each app's Internal User Directory, and use this to configure the app if Crowd is unavailable?

 

2) How would I delegate administrative permissions (over each app, not Crowd) to Users in the Crowd User Directory?

 

 

Thanks!

1 answer

1 accepted

0 votes
Answer accepted
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 30, 2015

Should I ensure a Super Admin User exists in each app's Internal User Directory, and use this to configure the app if Crowd is unavailable?

Yes. If you don't have this, when Crowd dies, you'll have a mess on your hands.

How would I delegate administrative permissions (over each app, not Crowd) to Users in the Crowd User Directory?

Crowd will sycn the users to each of the application. Users and groups in the app will be show with the label of "Crowd User". They are just like any any app user and group where you can use them in schemes.

If I have a user defined in an App's Internal User Directory, and another User with the same name in the Crowd directory, is there a _first match wins_ I need to be aware of?

On the second question, I'm not sure the answer provided is sufficiently clear, though I am having a difficult time coming up with a more nuanced version of the question. I will research some more first.

Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 30, 2015

bq. is there a _first match wins_ I need to be aware of? If there is a duplicate usernames, the order of your User Directory takes precedence.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events