Skip to main content
ConfigView reads your GrowthBook organization through GrowthBook’s REST API, using a Secret Key that an admin creates for ConfigView. A Secret Key belongs to the organization, not to a person, so it keeps working when whoever set it up leaves. You will end up with 1 secret in ConfigView (GROWTHBOOK_API_KEY), plus a second (GROWTHBOOK_API_URL) only if you host GrowthBook yourself.
Scope of this integration today. ConfigView reads who is a member of GrowthBook and with what role (including who is an admin and who holds project roles), teams, projects and environments, every feature flag with its owner, project, tags, rule counts and the environments it is switched on in, SDK connections and their settings, experiments and their status and dates, data sources, saved groups and custom validation hooks. ConfigView only reads. It never creates, edits, publishes, archives or deletes anything, and it never stores flag values, rule conditions, SDK client keys, encryption keys, data source SQL or credentials, hook code, or the members of a saved group.

​
Step 1: Open the GrowthBook page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/growthbook

​
Step 2: Find your API address

For a self-hosted install, use the address of the API, not the dashboard. ConfigView adds the /api and /v1 parts itself, so either https://gb-api.example.com or https://gb-api.example.com/api works. The address must be reachable from ConfigView. If you need to enter it, paste it into GROWTHBOOK_API_URL under Credentials and click the save icon.

​
Step 3: Create a Secret Key for ConfigView

You need permission to manage API keys in GrowthBook (an admin).
  1. In GrowthBook open Settings → API Keys and choose Create New Secret Key
  2. Name it ConfigView
  3. Give it the Read Only role. This is enough to read feature flags, experiments, projects, environments, SDK connections, data sources and saved groups, and it cannot change anything
  4. Copy the key (it starts with secret_) into GROWTHBOOK_API_KEY under Credentials and click the save icon. GrowthBook shows the key once; if you lose it, create a new one
Members and teams need more than Read Only. GrowthBook only returns the member list to a key that can manage the team (the Admin role) or manage projects (Project Admin). A Read Only key gets a 403 on that list. ConfigView handles this without failing: the Members and Teams collectors are skipped with a note, and everything else still works. If you want to see who has access to GrowthBook, you have two choices:
  • Create the key with the Admin role. That key can change things in GrowthBook even though ConfigView only reads, so use it only if your policy allows, and keep the key short-lived
  • Or keep Read Only and accept that the people questions (who is an admin, who has not signed in) are unavailable
If your GrowthBook plan has custom roles, a custom role that can view members and nothing else is the least privilege for this. If your organization requires keys to expire, ConfigView reads the expiry from GrowthBook and its health check warns you 14 days before the key stops working.

​
Step 4: Connect and verify

  1. Back on https://{companyname}.configview.com/admin/integrations/growthbook, confirm the credentials show as saved
  2. Click Connect. ConfigView creates its tables and schedules every collector at your default run time. Stop any you don’t want under Collectors:
  1. Click Verify now. The health check confirms the key works, then reads one page from each kind of data.
If a check fails:
  • “GrowthBook API key” fails with 401. The key is wrong, was deleted or has expired. Create a new key and update GROWTHBOOK_API_KEY.
  • The key check fails to connect (self-hosted). GROWTHBOOK_API_URL must be the API address (your API_HOST), reachable from ConfigView, not the dashboard address.
  • “Members” or “Teams” is skipped. The key’s role cannot list members. See Step 3. Nothing fails; those tables stay empty.
  • “Custom hooks” or “Data sources” is skipped. Custom hooks are an Enterprise feature, and the key’s role may not be able to view data sources. The table stays empty and nothing fails.
  • Any other check fails with 403. The key’s role cannot read that data. Use Read Only or a role with the matching View permission.

​
Data Tables

Once the scripts run, these tables are created in your database. Each includes a run_at column and keeps only the newest run.

​
Things worth knowing

GrowthBook’s API allows 60 calls a minute. ConfigView sends one request at a time and keeps to 45 a minute. A full run takes a minute or two; an organization with thousands of feature flags or experiments takes a little longer because lists are read 100 at a time. A self-hosted server may set its own limit. “Stale” is measured at the time of the latest collection. A feature flag counts as stale when it was last changed more than 180 days before ConfigView’s latest run, so the answer does not drift while the data sits unchanged. Environment names are yours. Questions about production match any environment whose name contains prod (production, eu-production, prod). If you name it differently, tell us. Owners are display names. GrowthBook stores a feature flag’s owner as a name, not an email, so the owner of a flag is matched to a member by name. Audit history is not available. GrowthBook’s REST API does not expose its audit log or the list of API keys, so ConfigView cannot show who created keys or a history of admin changes. Feature flag revisions record who published the latest one, which ConfigView keeps.

​
What isn’t collected

  • The Secret Key, and any other API key or Personal Access Token
  • SDK client keys, payload encryption keys and proxy signing keys
  • Feature flag values, rule conditions and the compiled flag definitions
  • Data source connection details and assignment-query SQL
  • Custom hook code
  • The values or conditions of saved groups (only how many values a list holds)
  • Experiment hypotheses, results, metrics and screenshots