Keep team access aligned with real work
A recurring review catches permission drift before it becomes a blocker or a risk.
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
Teams evolve while repository permissions quietly remain unchanged.
- Catch permission drift
- Reduce access uncertainty
- Create a repeatable review
Setup
Build it in a few focused steps.
- 1Connect Blackbaud and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Instruct Notis to check team permissions for repositories supporting active Blackbaud projects and report unexpected access levels.
- 4Choose a recurring quarterly trigger and select the channel for run reports.
- 5Test with one active project repository.
Questions about this workflow
Does this change permissions?
No. It checks and reports the current permission level.
Can it focus on active projects only?
Yes. Define active projects in the plain-language prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blackbaud to GitHub. A trigger fires from one place; an action lands in another.
Blackbaud 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.
Blackbaud 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.