Check GitHub team access against Baserow records
Have Notis check what access a GitHub team has for each repository in your Baserow review list.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check team permissions for a repository
Checks a team's permissions for a specific repository within an organization, including permissions inherited from parent teams.
Why this helps
Team and repository access is hard to audit when the expected access lives in a separate record from the actual GitHub permissions.
- Compare recorded expectations with GitHub team permissions.
- Review multiple team and repository pairs on a schedule.
- Surface access that needs a closer look.
Setup
Build it in a few focused steps.
- 1Connect Baserow and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to check each team and repository in the Baserow review list and report the permission level returned by GitHub.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real team and repository pair.
Questions about this workflow
Which permissions can this check report?
The action checks a team's permissions for a repository, including permissions inherited from parent teams.
Does this workflow change permissions?
No. It checks access and reports what GitHub returns.
What must the Baserow records identify?
They need to identify the organization, team, and repository for each permission check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Baserow to GitHub. A trigger fires from one place; an action lands in another.
Baserow triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Baserow and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.