New features this week

We have two new features for you this week. They've been a month in the making and we hope you enjoy them. Organization Permissions Paying Flipper Cloud customers now have a little more control over which organization members have access to which features. Organization members can be assigned a role…

Environment Owners

Flipper Cloud now supports restricting who can enable, disable, or roll back feature flags in shared environments. That way nobody accidentally enables a flag in production prematurely.…

Organization Permissions

Flipper Cloud customers now have a little more control over which organization members have access to which features. Organization members can be assigned a role of administrator, member, or billing. And even better, there's no charge for billing-only team members.…

Read-only API Tokens

We're working on providing more control over who can manage features and in which environments. Now you can choose to make API tokens read-only. 0:00/1× Toggling a feature with a read-only token via the API or Flipper gem will result in an error: $ curl -H "Flipper-Cloud-Token: $FLIPPER_CLOUD_…

Feature Creators & Owners

Knowing is half the battle, and sometimes the only way to know is to talk to the right person. You can see who originally created a feature flag with Flipper Cloud's audit history, but digging back into the past can be tedious. Moreover, the person who originally created a feature…