migration for user feature flags

_sql/migrations/2024-03-05-082026_alter_users_add_feature_flags/down.sql

@@ -0,0 +1,5 @@
+-- noinspection SqlDialectInspectionForFile
+-- noinspection SqlNoDataSourceInspectionForFile
+-- noinspection SqlResolveForFile
+
+ALTER TABLE users DROP COLUMN maybe_feature_flags;

_sql/migrations/2024-03-05-082026_alter_users_add_feature_flags/up.sql

@@ -0,0 +1,7 @@
+-- noinspection SqlDialectInspectionForFile
+-- noinspection SqlNoDataSourceInspectionForFile
+-- noinspection SqlResolveForFile
+
+ALTER TABLE users
+    ADD COLUMN maybe_feature_flags VARCHAR(255) DEFAULT NULL
+    AFTER user_role_slug;

_sql/migrations_squashed/user_tables/users.sql

@@ -22,6 +22,18 @@ CREATE TABLE users (
   -- The role assigned to the user confers permissions.
   user_role_slug VARCHAR(16) NOT NULL,
 
+  -- An optional comma separated list of flags for user accounts
+  -- If a user has a flag, then they're enabled for that given feature.
+  -- There are better ways to do this, but this hack will do for now.
+  -- This should replace `can_access_studio`.
+  --
+  -- Possible flag values (multiple is okay) :
+  --   - "explore_media"
+  --   - "studio"
+  maybe_feature_flags VARCHAR(255) DEFAULT NULL,
+
+  -- DEPRECATED
+  -- TODO(bt, 2024-03-05): Remove after new flags are in place.
   -- Rollout flag for Storyteller Studio
   -- Default to false until rollout is 100%, then remove the column.
   can_access_studio BOOLEAN NOT NULL DEFAULT false,