[bug]: Google OAuth toggle in god-mode won't enable - missing IS_GOOGLE_ENABLED row in instance_configurations

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

On a fresh Plane Community Edition 1.2.2 self-hosted instance:

1. Go to /god-mode > Authentication > Google
2. Enter valid Google OAuth Client ID and Client Secret
3. Click Save — UI says "configuration saved"
4. The toggle to enable Google authentication does not flip to enabled. It remains disabled even after saving and refreshing.

Root cause

The instance_configurations table (or equivalent) is initialized with IS_GOOGLE_ENABLED missing entirely. Other providers like GitHub, GitLab, and Gitea all have their IS_*_ENABLED rows created during instance initialization, but Google does not.

Evidence from the /api/instances/configurations/ endpoint (authenticated as instance admin):

• GOOGLE_CLIENT_ID — present and saved correctly
• GOOGLE_CLIENT_SECRET — present and saved correctly
• IS_GOOGLE_ENABLED — missing (no row exists)

Attempting to PATCH the configurations endpoint with IS_GOOGLE_ENABLED returns a 500 Internal Server Error, presumably because it tries to update a row that doesn't exist.

The /api/instances/ public endpoint confirms "is_google_enabled": false even after saving valid credentials through god-mode.

Expected behavior

The IS_GOOGLE_ENABLED row should be created during instance initialization (alongside the other IS_*_ENABLED rows), and the god-mode toggle should successfully enable Google OAuth after credentials are saved.

Workaround

Manually insert the missing row into the database:

INSERT INTO <config_table> (id, key, value, category, is_encrypted, created_at, updated_at)
VALUES (gen_random_uuid(), 'IS_GOOGLE_ENABLED', '1', 'GOOGLE', false, now(), now());

Version

• Plane Community Edition v1.2.2
• Self-hosted via Docker Compose
• Ubuntu 24.04

Browser

Google Chrome