Beta

HashiCorp : Terraform Cloud

Terraform Cloud Team

Lab Solution Teams

Welcome back! In this lab, you’ll learn how to implement role-based access control (RBAC) using Terraform Cloud Teams. By the end of this walkthrough, you will be able to:

  • Upgrade your Terraform Cloud plan to Team & Governance
  • Create and configure teams (org_admins, app_developers, managers)
  • Invite users and assign them to the correct teams
  • Grant workspace permissions across development, staging, and production

Let’s dive in.

1. Upgrade to Team & Governance Plan

Terraform Cloud’s free tier does not support teams. To enable Teams & Governance features:

  1. Go to your Terraform Cloud organization.
  2. Navigate to Organization Settings > Plan & billing.
  3. Select Team & Governance and click Start free trial.

The image shows a KodeKloud lab interface for Terraform Cloud Teams, with instructions on activating the "Team and Governance" plan and a file explorer on the right.

The image shows a pricing plan page for a software service, detailing different subscription options including Free, Trial, Team, and Team & Governance plans. The sidebar highlights the "Plan & billing" section, and there's an arrow pointing to a "Free Trial Available" upgrade option.

Note

HashiCorp offers a 30-day trial for Team & Governance. Once activated, you can create and manage teams under Organization Settings > Teams.

2. Create Your Teams

Terraform Cloud ships with a default owners team. We’ll add three more:

TeamOrg-Level AccessPurpose
org_adminsFull (policies, workspaces, VCS, SSO, billing)Organization administrators
app_developersNoneApplication development
managersNoneOversight and read-only review

Steps to Add Teams

  1. In Terraform Cloud, go to Organization Settings > Teams.
    The image shows a settings page for a team named "owners" in a cloud management interface, with options for visibility, API token creation, and adding new team members. The sidebar includes navigation options like Workspaces, Organization Settings, and Security.

  2. Click New Team, name it org_admins, and grant the permissions shown here:
    The image shows a "Team Management" interface in a software application, where a new team named "org_admins" is being created. The sidebar includes options like Workspaces, Organization Settings, and Integrations.

  3. Under Organization Access, enable all checkboxes for policies, workspaces, VCS, SSO, and billing:
    The image shows a user interface for managing organization access settings, with options to manage policies, workspaces, VCS settings, and more. The left sidebar includes navigation options like Workspaces, Teams, and Users.

  4. Repeat to create:

    • app_developers (no org-level access)
    • managers (no org-level access)
      The image shows a user interface for managing teams in an application, with options to create a new team and a list of existing teams such as "app_developers," "managers," "org_admins," and "owners." The sidebar includes navigation options like "Workspaces," "Users," and "Integrations."

Your organization now has four teams: owners, org_admins, app_developers, and managers.

3. Invite Users

Add teammates by sending invites via email:

  1. Go to Organization Settings > Users and click Invite users.

  2. Enter the email (e.g., [email protected]) and assign the app_developers team.
    The image shows a user management interface for "Mastering-Terraform-Cloud," displaying one active user with options to search, invite, and manage users. The sidebar includes navigation options like Workspaces, Organization Settings, and Security.

  3. After Bryan accepts the email invitation, he’ll select your organization:
    The image shows a Terraform Cloud interface where a user can choose an organization, with options to accept or decline an invitation to "Mastering-Terraform-Cloud" and access the organization "krausen."

  4. Confirm his membership under Users:
    The image shows a user management interface from a software application, listing active users and their associated teams. The sidebar includes options for workspaces, organization settings, integrations, and security.

4. Configure Workspace Permissions

We’ll set up three workspaces—MyAppDev, MyAppStaging, and MyAppProd—with different roles for each team.

4.1. Development Workspace

  1. Open MyAppDev > Settings > Team Access.
    The image shows a KodeKloud lab interface for Terraform Cloud Teams, with instructions on assigning teams to a workspace with permissions. On the right, there's a terminal window displaying a file explorer and command line.

  2. Assign:

    • app_developers: plan (read + run)
    • managers: read
      The image shows a user interface for managing team access permissions in a workspace, with options for reading, planning, and writing permissions. The sidebar includes various workspace settings like general, locking, notifications, and version control.

  3. Verify both teams appear with the correct roles:
    The image shows a "Team Access" page from a Terraform Cloud workspace, displaying team names and their access privileges. It includes a sidebar with various workspace settings options.

4.2. Staging Workspace

Repeat the same steps for MyAppStaging:

  • app_developers: plan
  • managers: read

4.3. Production Workspace

For MyAppProd, assign read-only access to both teams:

  1. app_developers: read

  2. managers: read
    The image shows a user interface for adding team permissions in a workspace, with options to assign permissions to managers and a list of baseline permissions for reading a workspace.

  3. Confirm on the Team Access page:
    The image shows a Terraform Cloud workspace interface with a focus on "Team Access" settings, listing teams and their access privileges. The sidebar includes options like General, Locking, Notifications, and more.

Workspace Permissions Overview

Workspaceapp_developersmanagers
Developmentplanread
Stagingplanread
Productionreadread

Warning

Ensure you save permissions after each change. Unsaved changes will not apply to runs.

5. Verify as a Team Member

When Bryan logs in:

  • MyAppDev: he can view state, variables, settings, and queue new plans.
  • MyAppStaging: same plan/run capabilities.
  • MyAppProd: only read access—no Queue plan or settings controls.

The image shows a Terraform Cloud workspace dashboard for "devops-aws-myapp-dev," displaying details of the latest run, including resources, metrics, and settings options.

This confirms our RBAC setup is working as intended.

Summary

In this lab, you have:

  • Upgraded to the Team & Governance plan
  • Created org_admins, app_developers, and managers teams
  • Invited users and assigned them to the correct teams
  • Set workspace-level permissions for development, staging, and production

Your Terraform Cloud organization now follows a secure, role-based access model.

References

Watch Video

Watch video content

Practice Lab

Practice lab

Previous
Terraform Cloud Team
Next
Lab Solution Migration to Terraform Cloud