Keep team access matched to how your product runs
When ownership changes, your repository permissions should not require a separate memory jog.
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 permissions can remain overly broad or become too restrictive as services and responsibilities evolve.
- Aligns access with current ownership
- Flags permission drift
- Reduces manual admin reviews
Setup
Build it in a few focused steps.
- 1Connect Datadog and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: On the recurring schedule, compare Datadog service ownership context with GitHub team permissions for the listed repositories and report differences.
- 4Pick a cron trigger, choose the run-report channel, and test with one team and repository.
Questions about this workflow
Does this update permissions automatically?
This workflow is for review and reporting; add a separate instruction only if an update is intended.
Can it review inherited permissions?
GitHub returns team permission details including permissions inherited from parent teams.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Datadog to GitHub. A trigger fires from one place; an action lands in another.
Datadog 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.
Datadog 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.