Help Center

Explore the common questions we receive below related to how ZenHub connects with GitHub.


Why can't I see my organization on the ZenHub Dashboard?

If the organization's owner turns on third-party application access restrictions without whitelisting or granting ZenHub access, grant ZenHub access by performing these steps: 


  1. Revoke your ZenHub token by going to github.com/settings/applications and clicking Revoke.Revoke 
  2. Go to your ZenHub Dashboard, sign out, then back in again. You should see the following:Authorize 
  3. If you are an admin, you should see Grant Access if not, you will see Request Access. Click on whichever of the two options you see. If you clicked Grant Access there are no further actions needed to get access to ZenHub. 
  4. If you clicked Request Access you will see that access request is pending: Request pending 
  5. Please ask the organization's owner to do to the organization's Settings page, click Third-party application access policy, head to ZenHub and click review, then grant access as displayed in the screenshots below.Review requestGrant access 
  6. Once access is granted, the organization's admin should see the following: Access granted 
  7. Finally head back to your ZenHub Dashboard and sign out, then in again, and you should see your organizations!
How secure is my data in ZenHub?
We take security very seriously and commit to doing everything in our power to keep your data safe and private. We use industry-standard encryption and integrate with GitHub's own Open Authentication (OAUTH) system. At no point do we have access to your GitHub credentials, and at no point do we ever read any of your code, your branches, or the contents of your issues or Pull Requests. Please refer to our Terms of Service and Privacy Policy for more details.
What are the details of ZenHub's GitHub access permissions?
ZenHub is committed to keeping your code and information safe, including full AES 256-bit encryption. For more, please see our Terms of Service and Privacy Policy. If you have further questions, email us at support@zenhub.com.
How do ZenHub permissions work?
The ZenHub Board for a given repository can be viewed by anyone with Read/Pull access to that repository. Any GitHub user who can view and clone the repository will be able to view the Board.ZenHub Board issue manipulation/reprioritization can be performed by anyone with Write and Admin access to the repository. Any GitHub user who can push to the repository will be able to edit a ZenHub Board for that repository.
Why is ZenHub asking for code access in my repo?
Currently, ZenHub authenticates at the user level using GitHub oAuth. The oAuth processes via GitHub means that once connected, ZenHub can be accessed across the organizations (and repos within that org) and personal repos that the user has access to where third party restrictions aren't preventing the organization from being accessed. While the oAuth model requests access to authenticate with the same permission set the user has (including Issue access, repo access, code access etc., at no point do we have access to your GitHub credentials, and at no point do we ever read any of your code, your branches, or the contents of your issues or Pull Requests, across any organization. The only exception is to render the service, for example injecting Issue templates into new issues created in ZenHub (as Issue templates are code in the repo). Because we're only able to ask for full read/write access at this time in the oAuth model, and not narrow permissions down, we've taken a number of contractual, administrative, technical, and physical steps to ensure the complete privacy of our user's data and information. Review our privacy policy here for more details: https://www.zenhub.io/privacy

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.