Clarkes.Team Portal is a GitHub App made by Clarkes.Team. It lets your client portal report on the development work done in your repositories — what was merged, updated, released, deployed and fixed.
Every permission it has is read-only. It cannot push code, open or merge pull requests, change settings, or write anything at all to GitHub. It checks for new activity on a schedule, about once an hour, and receives nothing from GitHub in between.
There is no install button on this page. The App is installed from a link tied to one GitHub account, which we send to an owner of your organization.
Read-only
Access
About hourly
Checks for new activity
An org owner
Installed by
Any time
Removable
It depends on one thing only: whose GitHub organization your code lives in.
Then yes, the App is needed.
Installing it is the only way the portal can see the work done in repositories you own. An owner of your GitHub organization installs it, choosing which repositories it may see.
If you are a member of the organization but not an owner, GitHub lets you request the install from the same screen, and an owner then approves it.
Then no, there is nothing for you to install.
Where we build and hold the repositories ourselves, we connect them from our side. You do not need to do anything, and nothing is asked of your GitHub account.
Not sure which of the two applies to you? Ask, and we will tell you which repositories are where.
Five monthly figures on your application’s page, counted from the activity in the repositories you connect.
Development work merged by the Clarkes.Team team.
Library and package updates reviewed and merged by the Clarkes.Team team.
The releases published from the repositories we work on.
How many times the application was deployed.
Security alerts GitHub has marked as fixed.
This is the whole list. It is what GitHub will show you on the install screen, and there is nothing else behind it.
| GitHub permission | Access | Why it’s needed |
|---|---|---|
| Metadata | Read-only | Required by GitHub for every App. Repository names, default branch, and whether a repo is private or archived. |
| Pull requests | Read-only | To count merged pull requests: their number, title, author, who merged them, branch names and dates. |
| Dependabot alerts | Read-only | To count security alerts resolved: the affected package, severity, advisory ID and dates. |
| Contents | Read-only | GitHub puts Releases under this permission. The portal uses it only to read release tags and dates. |
| Actions | Read-only | To count deployments and spot failing builds. The portal reads the list of workflow runs and their jobs only, never build logs or build files. |
| Code scanning alerts | Read-only | To include code-level security findings in your security summary, where GitHub code scanning is switched on. The portal records the type of finding, its severity and dates, never the file or line it points to. |
On GitHub, Contents is the permission that could technically read the files in a repository. It is on the list for one reason: GitHub files Releases under it, and there is no narrower permission that covers a release tag.
The portal only ever makes a fixed set of requests — pull requests, security alerts, releases. It never requests file contents, code, diffs or downloads. The permission GitHub grants is broader than the use we make of it; the use is not.
Actions is the same shape of answer. On GitHub it could technically read your build logs and download the files a build produces.
The portal only ever requests the list of workflow runs and their jobs — enough to count deployments and see that a build failed. It never requests a log and never downloads a build file.
None of the following is requested from GitHub, and none of it is kept anywhere.
Three steps, and the only one on your side is the approval.
Clarkes.Team sends an owner of your GitHub organization a personal install link. It is tied to their GitHub account, which is why there is no install button on this page.
GitHub shows the App’s name and its exact read-only permissions, and asks which repositories it may see. The owner chooses the repositories and approves.
GitHub returns the owner to the Clarkes.Team portal, which confirms the connection. We then link the repositories to the right application in your portal.
At that second step GitHub asks the owner to choose between “All repositories” and “Only select repositories”.
We recommend “Only select repositories”, choosing the ones Clarkes.Team works on. The selection can be changed at any time in GitHub, so starting narrow costs you nothing.
Nothing about this is a one-way door, and none of it goes through us.
In GitHub, at any time: your organization’s Settings → GitHub Apps → Clarkes.Team Portal → Configure. From there an owner can change which repositories it sees, suspend it, or uninstall it.
After uninstalling or suspending, the portal stops reading anything from your organization straight away. Monthly summaries already approved stay in the portal as the record of work done.
No. Every permission the App has is read-only. It cannot push code, open or merge pull requests, change settings, or write anything at all to GitHub. There is no permission in its list that would let it.
No. It never requests file contents, code, diffs or downloads, and it does not read commit messages, pull request descriptions or comments, release notes, issues, secrets, settings, build logs or build files. Two permissions in its list look broader than they are: “Contents” is there because GitHub files Releases under it, and “Actions” because that is where the list of workflow runs lives. The portal uses them only to read release tags and dates, and to count deployments and failed builds.
Yes, and we recommend it. When installing, GitHub asks whether the App may see all repositories or only selected ones. Choose “Only select repositories” and pick the ones Clarkes.Team works on. The selection can be changed at any time in GitHub.
An owner of your GitHub organization. If you are a member but not an owner, GitHub lets you request the install and an owner then approves it. You only need it at all if your code lives in your own GitHub organization — where it is in a Clarkes.Team organization, we connect it ourselves and there is nothing for you to install.
The portal stops reading anything from your organization straight away. Monthly summaries that have already been approved stay in the portal as the record of work done. Uninstalling and suspending are both done from GitHub, in your organization’s Settings → GitHub Apps → Clarkes.Team Portal → Configure.
Something not covered here? Ask an engineer
Ask whatever is left — which repositories we would want to see, who in your organization has to approve it, or anything on this page you would like in writing before you decide.
After hours. We're still monitoring.
