You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have about 15 internal service desks. I have 1 external user that needs to see 1 of those service desks.
I've turned on "Allow portal-only accounts to be created for new customers accessing the help center" and added their domain to "Only allow account creation for customers with specific email domains". In doing so this 1 user can see all 15 service desks because I have "Anyone allowed on the customer access settings", but If I change this to "Customers added to this service project only by agents and admins" I have to add all my internal users to the 15 service desks, and add any new employee that is onboard to those servers. That doesn't seem right am I missing something? This can't be how this works.
Hi Graham,
Permissions can get quite confusing, I hear you! You're right that switching to 'customers added to this service project only by agents and admins' is what you need. That does mean your internal users will have to be added to the other 15 service desks, but you can use customer organisations to make this easier.
1) Add all internal users to a customer organisation and then add that organisation to each of the 15 service desks. Organisations can be used across multiple projects, so you'll only need to add the users into the organisation once and they'll gain permission for every service desk that the organisation is added to.
2) There's not yet a way to automatically add newly created users to an organisation, but this soon-to-be-released feature is worth watching as it may add this capability: Email domain organization association
As a temporary workaround, you can:
It's not a perfect solution, but it'll work while we wait for the new feature linked above.
Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.