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,559,241
Community Members
 
Community Events
184
Community Groups

Okta/Atlassian Access - Hide app from select users

We have a fully working Atlassian Access/Okta integration at this time.  The one downfall we're facing is that we have significantly fewer Confluence users as we do Jira users.  In the pre-built integration, you can show or hide Jira and Confluence for all users.  There is no way to hide the tile for users that aren't assigned an actual license (that I'm aware of).

Is there an SP-initiated login URL I could use as a Bookmark-app and hide Confluence from the default integration?  The number of access requests we're seeing is a bit ridiculous.  Or perhaps a 'Generic' configuration that I could use to separate the tiles? 

1 answer

1 accepted

0 votes
Answer accepted
Dave Meyer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 08, 2019

Hey Neil,

This might be a better suggestion for Okta, as they control the behavior of the Atlassian application on the Okta dashboard. We have raised the limitations of the current Atlassian tile with them but don’t have a timeline on a potential solution.

The best solution today is to set up a bookmark app for that points to id.atlassian.com, this will redirect users to start.atlassian.com post-SAML handshake. From there they can select any of the apps they have access to on the Atlassian (or jump straight to a page or issue!)

Regards,

Dave

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events