Keep repository permissions aligned with role changes
When a job change affects code access, make the GitHub permission update part of the same review routine.
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
A role change can alter what someone needs to do, while team repository permissions stay untouched in a separate admin task.
- Surfaces access changes tied to employee role updates
- Applies permission levels your team has specified
- Makes permission changes easier to review
Setup
Build it in a few focused steps.
- 1Connect BambooHR and GitHub once in the Notis portal.
- 2Create a named automation from Automations, New Automation.
- 3Describe which BambooHR job changes qualify, the GitHub team and repository, and the permission level to apply.
- 4Pick a recurring schedule, choose where run reports go, and save the automation.
- 5Test with one real role change and review the permission update.
Questions about this workflow
Can BambooHR determine the correct GitHub permission level?
Only when your prompt supplies explicit rules connecting a role change to a permission level.
Which permission levels can the GitHub action set?
The listed action supports read, write, or admin for a team's repository permission.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bamboohr to GitHub. A trigger fires from one place; an action lands in another.
Bamboohr 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.
Bamboohr 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.