Scheduled Team Repository Permission Sync
Every week, Notis updates your teams' GitHub repository permissions based on your organizational rules. No manual permission updates needed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Your team structure changes (new people join, old people leave, roles shift), but GitHub repository permissions don't automatically update. Access creep and confusion builds.
- Keep permissions in sync with org changes
- Reduce manual permission management
- Prevent access creep over time
- Maintain consistent permission hierarchy
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create a cron automation: "Every Friday at 6pm, update team repository permissions. If a team has 3+ new members, grant them [push] access. If someone left, remove them from [repository]."
- 3Define your permission rules (by team, repository, tenure, role, etc.).
- 4Notis will enforce those rules every week.
Questions about this workflow
What if my org structure is complex, with nested teams?
Notis handles nested teams and inheritance automatically.
Can I review changes before Notis applies them?
Yes, you can set Notis to send you a report for approval before updating permissions.
Does Notis handle leave-of-absence or on-boarding workflows?
You can tell Notis to adjust permissions based on time (e.g., 'new team members get read-only for first 2 weeks').
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gmail to GitHub. A trigger fires from one place; an action lands in another.
Gmail triggers
GitHub actions
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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.
Not just Gmail and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.