Ladies and gentlemen, it's been a very long time since I last written a technical post, but I find it important needed to inform my friends and family here in #hive. I will make a similar post in #steem later so we can manage our authority efficiently.

# To check your existing authority
### https://hiveblocks.com/@username
![image.png](https://files.peakd.com/file/peakd-hive/davidke20/DHyH4Ltz-image.png)
Firstly, you need to find out if your account connected to which dApp previously from the old chain. Do take note that the entire account has been copied one to one from the past, so you really need to be extremely careful of what you have authorized. As far as I know @minnowbooster is no longer active. It's better to take it off. Some of the dApps like @wherein-io are stuck with previous front end due to the firewall in their home country. Not that they do not want to migrate over, it's just because the front end is not ready, so we'll have to do manual authorized it, manually changed the server to point at witnesses who runs HF23 in order to send and receive from #HIVE. So, let's get on with simple technical workaround.

# To revoke authority
### https://hivesigner.com/revoke/appnamehere
![image.png](https://files.peakd.com/file/peakd-hive/davidke20/MEUB7H9M-image.png)
So this is it. Follow the link above, replace the app name at the back for whichever app you wish to revoke authority and you're all set. Very easy. Repeat the same for all the dApp you wish to remove authority by simply changing the app name everytime. @thecryptodrive hope you don't mind I use @minnowbooster as a sample. If it really bothers, do let me know I will take it down.

# To authorize
### https://hivesigner.com/authorize/appnamehere
![image.png](https://files.peakd.com/file/peakd-hive/davidke20/pbHZLsXr-image.png)
This is totally irrelevant if your app has a local sign in. This applicable to dApps that has no direct sign in authority with hivesigner only. By using the above URL command, change the app name you wish to authorize at the back, and then you're all set to go. You can use the same way to authorize as long as you know the app is safe to use your posting authority.

## Things that is good to know
To take note of all the above actions, authorizing authority is relatively safe because hivesigner does not store your key. However, giving authority is equally dangerous as allowing another party to post on your behalf. If your dApp does not operate hivesigner, please consult with the operator as in why they don't, or better yet consult any technical experts here just to be sure. And if it must be manually authorize, please consult the dApp operator and confirm the operating account, check and recheck to be safe. Some operator does not use the same account for posting authority, #partiko for example, their rewarding account, posting account, promotion account, staff payout account, comment reply account are all seperated. So, just be very careful of what you authorized. On the other hand, revoking authority can cause trouble as well. Like the other day I have removed 3speak from my authority, but forgot to reauthorized and made a post on their landing page, it didn't get sync over to the blockchain because it doesn't have the authority. I manually made a post about it, but later after I reauthorized the 3speak, immediately it fired up a "new" old post to my account and causes double posting, all by my silly mistake. Practice your regular review and understand your authority is essential. Its safe, but it also cause possible misused without verification.