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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Each user need to Authorise Power Ups individually

Hi, I've noticed that some of the Power-Ups used in my company's workspace (! Amazing Fields !, Clockify,...) will ask for each one of the users to individually authorize it.

This is not user friendly since a lot of the users are not heavy computer users like me and others, so they will get confused and the team will be asked several times why they can't use the powerup, and sometimes they even don't realize that there is an important feature being provided by an important Power Up.

Is there any way I can solve this?

1 answer

0 votes
Garrett Atlassian Team Dec 27, 2021

Hi @Ramoses Hofmeister Ferreira 

I understand not wanting each user to have to follow those steps, but I'm afraid there's not a way to avoid that.

Some Power-Ups and integrations require certain access in order to function, and that access can only be granted by the account owner, through the authorization steps.

Without that authorization, the integration can't function. You wouldn't be able to authorize on behalf of the user since you wouldn't be the owner of the account. On the other hand, an integration can't automatically be authorized, since that would be superseding the permissions of the user.

Hopefully that helps clarify!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events