Auto-Restrict Access for Sensitive Deals
High-value or confidential opportunities shouldn't be handled by everyone. Notis automatically restricts repository access to only the assigned team when sensitive opportunities are created—keeping deals contained and secure.
Trigger
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
Action
Add team access restrictions
Overwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.
Why this helps
Sensitive or high-value deals have no code-level security controls, leaving proprietary logic exposed to teams not involved in the deal.
- Implement deal-level security without manual permission tweaking
- Restrict code access to only the assigned team for high-value opportunities
- Keep proprietary logic protected during sensitive negotiations
- Automate compliance for confidential client work
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub to Notis
- 2Ask Notis: 'When a high-value or confidential opportunity is created in Salesforce, restrict access to [repo-name] to only the deal team'
- 3Define which opportunities trigger restrictions (e.g., value > $500k, or specific fields marked sensitive)
- 4Specify the team to grant access
- 5Choose notification settings
- 6Test by creating a sensitive opportunity in Salesforce and verify access is restricted in GitHub
Questions about this workflow
How do I know which opportunities are sensitive?
You define it—value thresholds, specific account types, or a checkbox field in Salesforce.
What happens to the team when the deal closes?
Ask Notis to set up a follow-up automation that expands access when the opportunity is won or closes.
Can I restrict multiple repositories at once?
Yes. Ask Notis to apply restrictions across your entire org or specific repos related to the deal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Salesforce to GitHub. A trigger fires from one place; an action lands in another.
Salesforce triggers
GitHub actions
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Contact Updated
Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.
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.
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
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.
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
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.
Task Created or Completed
Triggers when a Task is created or when its status changes to Completed in Salesforce. Supports optional filtering by task Status or Subject.
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.
Not just Salesforce and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.