Keep team access reviews on a steady schedule
Ask Notis to revisit a team's repository permissions and report the access level when your review comes around.
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 access can drift while founders are focused on shipping, making periodic review easy to postpone.
- Make a repeatable access review easier to complete.
- See the team's permission level, including inherited permissions.
- Keep access review reports in a place you already check.
Setup
Build it in a few focused steps.
- 1Connect GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis the organization, team, and repository to check and how to summarize the result.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real team and repository and confirm the permission result.
Questions about this workflow
Does this change team permissions?
No. It checks a team's permissions for a repository and reports the details.
Does the check include inherited access?
Yes. The action description says it includes permissions inherited from parent teams.
Which details does the check need?
Specify the organization, team, and repository in the Notis instruction so it can run the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Alchemy to GitHub. A trigger fires from one place; an action lands in another.
Alchemy 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.
Alchemy 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.