WienerWiener
  • Introduction
  • Compatibility
  • Release Notes
  • Comparison
  • Pricing
  • FAQ
  • Use Cases
  • License
  • Unity Asset vs Standalone
  • Lightweight Obfuscation & Change Detection
  • Mismatch Detection & Debug
  • Localization
  • Versioning
  • Google Sheets Input
  • Excel
  • YAML
  • Settings
  • Data Format
  • ValueOnly Format
  • Startup
  • Samples
  • Converter
  • YAML Editor
  • Setting Editor
  • 日本語
  • English
  • Introduction
  • Compatibility
  • Release Notes
  • Comparison
  • Pricing
  • FAQ
  • Use Cases
  • License
  • Unity Asset vs Standalone
  • Lightweight Obfuscation & Change Detection
  • Mismatch Detection & Debug
  • Localization
  • Versioning
  • Google Sheets Input
  • Excel
  • YAML
  • Settings
  • Data Format
  • ValueOnly Format
  • Startup
  • Samples
  • Converter
  • YAML Editor
  • Setting Editor
  • 日本語
  • English
  • Startup

    • Unity Startup
    • Google Sheets Settings
    • Switching Language Settings

Google Sheets Settings

Follow these steps only when using Google Sheets.

First, open Google Sheets Input setup and complete the Google Cloud preparation.

The credential JSON is a secret

Anyone who obtains the private key in a service account JSON can authenticate as that service account.

  • Do not store it under the Unity project's Assets directory
  • Do not commit it to a Git repository
  • Do not attach it to chat, email, project archives, or support materials
  • Grant the service account only the minimum sharing permission required for the target spreadsheet
  • Disable and delete unused keys or any key that may have leaked in Google Cloud

Google recommends keeping service account keys out of source repositories. See Best practices for managing service account keys.

Recommended Storage

Store the credential JSON in an access-restricted user folder outside the Unity project and Git repository.

Example:

<user-private-folder>/Wiener/credentials.json

If team policy requires a project-local file, use a local settings area outside Assets, and confirm that Git ignores it.

<Project>/UserSettings/Wiener/credentials.json

Add at least the following patterns to the Unity project's .gitignore:

/UserSettings/Wiener/
**/wiener-service-account*.json

Dummy file in the distributed package

The Unity Asset version contains a dummy file at Assets/Wiener/Data/secrets/wiener-service-account.json. It is not a valid credential.

Do not overwrite the dummy with a real key. Register an external file and change credential_path to that path.

Register the File in Setting Editor

The settings YAML used by Converter must reference the external credential JSON.

  1. Open Tools > Wiener > Open Setting Editor
  2. Enable google_sheets
  3. Select the external JSON file for credential_path
  4. Save the settings YAML

The current Unity Setting Editor can select a JSON file outside the project and preserves its absolute path. If the settings YAML is shared by a team, keep the local credential path in a user-specific settings file because paths differ between machines.

Register the File in YamlEditor

When creating YAML from Google Sheets, select the same external JSON from Google Sheets Credential JSON in the YamlEditor header. Unity stores the absolute path in local Editor settings; it does not store the JSON contents there.

Unity Wiener menu with Open Yaml Editor selected

Yaml Editor Google Sheets Credential JSON file selector

Key Operations

  • Do not share the JSON file itself between users
  • When practical, separate service accounts or keys by purpose and user
  • Do not grant access beyond the target spreadsheets
  • Review and delete unused keys regularly
  • If a leak is suspected, removing the file in a new Git commit is not sufficient; immediately disable and delete the key in Google Cloud
Last Updated:: 8/9/26, 11:18 PM
Prev
Unity Startup
Next
Switching Language Settings