Table: heroku_team_member - Query Heroku Team Members using SQL

Heroku Team Members are individual user accounts associated with a particular team within the Heroku platform. Each team member has a defined role that determines their permissions and access levels within the team. These roles include admin, member, and owner, each with varying levels of control over team resources and settings.

Table Usage Guide

The heroku_team_member table provides insights into user roles within Heroku teams. As a team manager or DevOps engineer, explore user-specific details through this table, including roles, permissions, and associated metadata. Utilize it to uncover information about team members, such as those with admin permissions, the roles distribution within the team, and the verification of access controls.

Important Notes

List queries require an team_name.
Pagination is not currently supported for this resource type in the SDK.

Examples

List all team members

Explore which roles are assigned to each team member and when they were added to the team. This can help in understanding the team's composition and its evolution over time.

select
  email,
  role,
  created_at
from
  heroku_team_member;

select
  email,
  role,
  created_at
from
  heroku_team_member;

List all federated team members

Explore which team members have federated roles in Heroku. This can be useful for understanding the distribution of roles and identifying potential security implications.

select
  email,
  role,
  created_at,
  is_federated
from
  heroku_team_member
where
  is_federated;

select
  email,
  role,
  created_at,
  is_federated
from
  heroku_team_member
where
  is_federated = 1;

List all team members who haven't enabled two-factor authentication

Explore which team members have not yet activated two-factor authentication. This is useful for identifying potential security risks within your team and ensuring all members are adhering to best practices for account security.

select
  email,
  role,
  created_at,
  two_factor_authentication
from
  heroku_team_member
where
  not two_factor_authentication;

select
  email,
  role,
  created_at,
  two_factor_authentication
from
  heroku_team_member
where
  not two_factor_authentication;

Schema for heroku_team_member

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
account_id	text	=, !=, ~~, ~~, !~~, !~~	Unique identifier of an account.
created_at	timestamp with time zone		When the team was created.
email	text		Email address of the team member.
id	text		Unique identifier of the team member.
identity_provider	jsonb		Identity Provider information the member is federated with.
is_federated	boolean		Whether the user is federated and belongs to an Identity Provider.
role	text		Role in the team.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
team_name	text	=	Role in the team.
two_factor_authentication	boolean		Whether the enterprise team member has two factor authentication.
updated_at	timestamp with time zone		When the membership record was updated.
user	jsonb		User information for the membership.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- heroku

You can pass the configuration to the command with the --config argument:

steampipe_export_heroku --config '<your_config>' heroku_team_member