# Automating Orb Publishing **URL:** \ **Category:** Orbs\ **Created:** [November 30, 2018, 5:57pm UTC](https://discuss.circleci.com/t/automating-orb-publishing/26870 "2018-11-30T17:57:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![hutson](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/hutson/32/19875_2.png) [@hutson](https://discuss.circleci.com/u/hutson)\ **Post date:** [December 4, 2018, 6:29pm UTC](https://discuss.circleci.com/t/automating-orb-publishing/26870/3 "2018-12-04T18:29:55Z")
> [@eddiewebb](#): > > To help users solve similar deployment problems elsewhere, Github suggests the creation of a [“Machine User”](https://developer.github.com/v3/guides/managing-deploy-keys/#machine-users) that has the rights required. Our organization created a bot account several months ago to facilitate the creation of GitHub Releases (You can see how we use Circle CI to manage that job in my [`semantic-delivery`](https://discuss.circleci.com/t/orbs-sneak-peaks-share-your-orbs-in-progress/26008/3) Orb example). > [@eddiewebb](#): > > This should address your two primary concerns by moving the ownership to a single protected non-human account with org level permissions. Agreed! It seems like a like-for-like trade-off in that, though we end up with a _machine user_ that has owner access to our organization, the account, _technically_, has no more permissions than my own. It would be really nice, though, if some day we can migrate away from _machine users_ with _owner_ permissions, as they still introduce a significant single point of risk. --- _[View the full topic](https://discuss.circleci.com/t/automating-orb-publishing/26870)._