Check team access when a strategy review flags a repository
When an incoming request points to a team and repository, Notis can check the team's effective permission and return a concise result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A team access question can stall a review while someone tracks down the organization, team slug, and repository details.
- Start an access check from an HTTP request.
- Check effective team permissions for the specified repository.
- Keep the result with the review run report.
Setup
Build it in a few focused steps.
- 1Connect BSC Designer and GitHub once in Notis.
- 2Create an automation in any channel or in Automations, New Automation.
- 3Explain how the webhook identifies the organization, team, and repository, then ask Notis to check team permissions.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real organization, team, and repository request.
Questions about this workflow
What must the incoming request identify?
It must provide enough context to identify the GitHub organization, team, and repository to check.
Can this grant or revoke access?
No. It checks a team's permissions and reports the result.
Are inherited permissions included?
Yes. The action checks team permissions, including those inherited from parent teams.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BSC Designer to GitHub. A trigger fires from one place; an action lands in another.
BSC Designer 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.
BSC Designer 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.