Keep access aligned as your team changes
A small recurring check can prevent a big access surprise later.
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
Permission drift accumulates quietly as collaborators, teams, and repositories evolve.
- Makes access reviews easier to remember
- Surfaces unexpected permission states
- Supports lightweight security governance
Setup
Build it in a few focused steps.
- 1Connect Doppler and GitHub to Notis once through the portal.
- 2Create an automation asking Notis to check the specified team’s permissions for critical repositories and report mismatches.
- 3Choose a recurring schedule and the channel for run reports.
- 4Test with one repository and confirm the permission result is understandable.
Questions about this workflow
What does the workflow change?
It checks the team’s repository permissions and reports the result; it does not silently alter access.
How often should it run?
Weekly or monthly works well, depending on how frequently collaborators and repositories change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Doppler to GitHub. A trigger fires from one place; an action lands in another.
Doppler triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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 Doppler 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.