
A git organization that I have access to and am an administrator of does not show up on my list of available organizations. How can I add it?
I’ve been assigned a new organization on my git account, how can I add it to Probo.CI
When you register your account with Probo.CI, you are presented with a screen to request permissions to organizations associated with your login. These are listed on the page asking for permission. You can grant or deny Probo.CI access to those organization specifically or in the case of contributor organizations, you can request access.
To change this, you will need to access the settings for your account authorize or de-authorize access to those organizations.
On GitHub, the permissions you grant to Probo.CI are managed through the Authorized OAuth Apps settings on your personal account. Even though the organization belongs to your git account, you control which organizations each application is allowed to see. Follow the steps below to grant Probo.CI access to an organization you already belong to.
Log in to GitHub with the same account you use to sign in to Probo.CI.
Click your profile photo in the top right corner and choose Settings from the drop-down menu.
In the left hand navigation, scroll down to the Integrations heading and click Applications.
On the Applications screen, click the Authorized OAuth Apps tab. This lists every application you have granted access to, including Probo.CI.
Click Probo.CI in the list to open its authorization details. Here you will see the list of organizations associated with your login along with the current access status of each one.
Find the organization you want to add. To the right of each organization you will see a Grant button, or, if the organization requires approval from an owner, a Request button.
Organizations that you own or administer can be granted access immediately. Organizations owned by someone else — where you are a contributor — may show a Request button instead. Clicking it sends a request to an organization owner, who must approve it before Probo.CI can access that organization.
Click Grant (or Request) next to the organization you want to add. If the organization enforces OAuth App access restrictions, you may be prompted to confirm the request.
Return to Probo.CI and synchronize your repositories. The newly authorized organization should now appear in your list of available organizations.
If the organization still does not appear after granting access, sign out of Probo.CI and sign back in.
On Bitbucket, applications are granted access on a per-workspace basis. When Probo.CI requests access, a workspace administrator must approve it for the workspace you want to build from. Follow the steps below to authorize Probo.CI for a workspace you already belong to.
Log in to Bitbucket with the same account you use to sign in to Probo.CI.
Click your profile avatar in the bottom left corner (or top right, depending on your layout) and choose Personal settings.
In the left hand navigation, under the Security heading, click App authorizations (labeled OAuth on some accounts). This lists every application you have granted access to, including Probo.CI.
Click Probo.CI in the list to open its authorization details. Here you will see the workspaces associated with your login along with the current access status of each one.
Find the workspace you want to add and grant Probo.CI access to it.
Access to a Bitbucket workspace must be approved by a workspace administrator. If you are the administrator of the workspace, you can approve the request yourself. If you are only a member, the request is sent to an administrator who must approve it before Probo.CI can access that workspace.
If Probo.CI is not yet listed, re-run the authorization from Probo.CI. When prompted by Bitbucket, review the requested permissions and click Grant access, selecting the workspace you want to authorize.
Return to Probo.CI and synchronize your repositories. The newly authorized workspace should now appear in your list of available organizations.
If the workspace still does not appear after granting access, sign out of Probo.CI and sign back in.
On GitLab, Probo.CI is authorized as an OAuth application against your account, and it can see any group in which your membership grants the appropriate access. Groups are GitLab’s equivalent of organizations. Follow the steps below to make sure Probo.CI can see a group you already belong to.
Log in to GitLab with the same account you use to sign in to Probo.CI.
Click your profile avatar in the top right corner and choose Preferences (or Edit profile).
In the left hand navigation, click Applications. Under Authorized applications you will see every application you have granted access to, including Probo.CI.
Confirm that Probo.CI is listed and that its scopes include read access to your repositories. If it is not listed, or the scopes look incomplete, re-run the authorization from Probo.CI and click Authorize when GitLab prompts you.
Unlike GitHub and Bitbucket, GitLab does not authorize applications per group. Probo.CI can see a group as soon as your account is a member of it with at least Developer access. If a group is missing, the most common cause is that your membership does not carry enough access, or the group’s owner has restricted which applications may access it.
Verify your role in the group you want to add. Open the group in GitLab, click Manage, then Members, and confirm you have at least Developer access. If you do not, ask a group owner to raise your access level.
Return to Probo.CI and synchronize your repositories. The newly available group should now appear in your list of available organizations.
If the group still does not appear after confirming your access, sign out of Probo.CI and sign back in.

When you sign up for a Probo.CI registration code, you will get a two week trial of the plan of your choosing. For more information on how to get started, click here .
LEARN MORE ABOUT PROBO.CI'S PRICING