Resourcely Documentation
LoginSign Up
  • Get Started
    • 🎱What is Resourcely?
    • πŸ‘‹Why Resourcely
    • πŸƒQuickstart
      • Terraform policies integrated into CI
      • Remediate policy violations in existing infrastructure
      • Templates for generating Terraform
      • Glossary
  • Concepts
    • Foundry
      • Create Blueprints with Foundry
      • Creating Guardrails with Foundry
      • lmport Terraform Modules
    • Guardrails
      • Writing your own Guardrails
      • Editing Guardrails
      • Releasing Guardrails
      • Enabling Inactive Guardrails
      • Guardrails in Action
        • 🐱GitHub Actions
        • 🦊GitLab Pipelines
    • Campaigns
      • Get started with Campaigns
      • Creating Campaigns
      • Remediate Resources
      • Campaign Agent
        • State File Support
          • Amazon Simple Storage Service (S3)
          • Google Cloud Storage (GCS)
          • HCP Terraform
          • Spacelift
        • Running Campaigns with GitHub Actions and a Repo-Hosted State File
        • Running Campaigns Locally
    • Blueprints
      • Authoring Your Own Blueprints
      • Using Built-in Resourcely Blueprints
      • Configuring Global Contexts
      • Deep Linking
    • Resources
      • Provisioning Infrastructure
      • Editing Infrastructure
      • Shopping Cart
      • Config Roots and Environments
    • Other Features and Settings
      • Global Values
      • Global Context
      • Metrics
      • Resourcely-cli
      • Resourcely.yaml
      • VCS Proxy
      • Settings
        • User management
        • Company Information
        • Notification Settings
        • Change Management
          • 🐱Connect to GitHub
          • 🦊Connect to Gitlab
        • Generate API Token
    • ✨Production Setup
      • Single Sign-On (SSO)
        • Auth0
        • AWS Single Sign-On
        • Azure AD
        • Google Workspace
        • JumpCloud
        • Okta
        • Omnissa Workspace ONE (formerly VMware)
        • OneLogin
        • Ping Identity
        • Other SAML / OIDC Providers
      • Source Code Management
        • Page
        • 🐱GitHub
        • 🦊GitLab
        • Atlassian Bitbucket
        • Azure Repos
  • Tutorials and guides
    • Remediation Use Cases
      • Apply tags to resources for automating backups
      • Implement centralized logging
    • Blueprints Use Cases
      • Automate Data Pipeline Creation
      • Encryption for GCP
      • AWS Account Factory
      • Streamline and govern AI
      • IAM Factory
      • Cost optimization for FinOps
      • Guardrails for Terraform Modules
    • Using the Resourcely Terraform Provider
      • Setup Resourcely Provider
      • Blueprints
      • Guardrails
      • Global Context
  • Integrate
    • CI/CD & Terraform Runners
      • Atlantis
      • 🐟AWS CodeBuild
      • Azure Pipelines
      • Buildkite
      • CircleCI
      • CloudBees CI
      • Codefresh
      • Digger
      • Env0
      • 🎏GitHub Actions
        • 🐱Local Plan
          • 🐹AWS with OpenID Connect
        • 🐢Terraform Cloud Integration
      • 🦊GitLab Pipelines
      • Harness
      • πŸ—»HashiCorp Cloud Platform (formerly Terraform Cloud)
      • Jenkins
      • Octopus Deploy
      • Scalr
      • 🌌Spacelift
      • Terramate
      • 🌎Terrateam
    • Cloud Providers
      • 🌨️Amazon Web Services (AWS)
      • πŸ€“Google Cloud Platform (GCP)
        • Guardrail Gaunlet at Google Cloud Next 2025
      • πŸ’ΎMicrosoft Azure
      • Alibaba Cloud
      • Huawei Cloud
      • IBM Cloud
      • Oracle Cloud Infrastructure (OCI)
      • Tencent Cloud
      • VMware vSphere
    • Developer Portals
      • Atlassian Compass
      • Backstage
      • Cortex
      • Harness IDP
      • Home grown internal developer portals
      • OpsLevel
      • Port
      • Roadie
    • ITSM
      • Atlassian Jira
      • FreshWorks
      • ServiceNow ITSM
      • ZenDesk
    • CSPM
      • Wiz
    • More Terraform Provider Integrations
      • πŸš‚ConductorOne Provider
      • Databricks Provider
      • Kubernetes Provider
      • πŸ•Datadog Provider
      • ❄️Snowflake Provider
Powered by GitBook
On this page
  • Contact Group
  • Reviewer
  • Manage your notification settings
  • Defining the Notification Groups
  • Assigning Reviewer(s) to Group(s)
  1. Concepts
  2. Other Features and Settings
  3. Settings

Notification Settings

This page explores adding group notification settings to loop in reviewer during Resourcely guardrails violations.

PreviousCompany InformationNextChange Management

Last updated 8 months ago

Contact Group

A Group is a set of stakeholders for guardrails that can be looped in during changes. Groups contain the following fields:

  • Name

  • Contact Info (Email)

  • List of Reviewers (Github, Gitlab)

Reviewer

A reviewer is a person or team who will be set to review a Pull Request (PR). Resourcely automatically assigns a reviewer defined in a group to review an infrastructure resource before it is provisioned.

Manage your notification settings

Let’s get started with configuring your notification settings within Resourcely. This step entails:

Defining the Notification Groups

Now let's create a Group notification settings within our tenant. You can create a notification settings by pressing the Add notification group button. Here you will need to provide the name of your Group (Example: Security, Development, Compliance, etc.). You can provide a name and email for your group.

Note: To begin onboarding, only one group is essential. However, you have the flexibility to add more groups later.

Assigning Reviewer(s) to Group(s)

Next, you must add a Reviewer to the group. You can add a reviewer by pressing the Add reviewer button. You must then select a provider (GitHub or GitLab) and type in the Reviewer's username.

If using GitHub as a provider, you must add a GitHub team as a reviewer instead of individual users. For GitLab, you must add the exact username.

Note: Only one reviewer is required to onboard. You can add more later as needed.

Once reviewers have been assigned to a group you, you can choose to set the group as default reviewer when a guardrail violation is triggered from change management. Now you can press the Save notification group button

You can create more Group notification settings if needed. Next is to configure .

Source Code Management integrations
Defining the Notification Groups
Assigning Reviewers to Group(s)
Adding Source Control Reviewers