Keep hotel operations team access aligned
A scheduled review can help keep repository permissions aligned with the people supporting hotel operations.
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
Repository access can drift as responsibilities change, leaving support teams without the access they need or with outdated permissions.
- Review operational access on a predictable cadence
- Set an existing team's permission on an organization repository
- Keep access decisions tied to current support responsibilities
Setup
Build it in a few focused steps.
- 1Connect Apaleo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis how to assess operational needs and identify the existing organization team, repository, and permission level to apply.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real access review and confirm the team and repository.
Questions about this workflow
Can this create a GitHub team or repository?
No. The action updates permission for an existing team on a repository within an organization. The team must already belong to that organization.
What data does the review use?
Notis can analyze returned Apaleo data, but any access policy or team-to-repository relationship that is not present in that data must be supplied in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apaleo to GitHub. A trigger fires from one place; an action lands in another.
Apaleo 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.
Apaleo 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.