Team & VCS Collaboration Workflow
When collaborating in a multi-developer studio using Version Control Systems (Git, SVN, or Unity Version Control / PlasticSCM), configure your project parameters to prevent API leaks and share layout standards.
1. Protecting API Keys
AI Scene Organizer stores all active API keys inside Unity’s machine-specific EditorPrefs registry rather than inside the Assets/ project folder.
- Why this is secure: Project settings and scenes can be checked into Git without exposing your personal Google, OpenAI, or OpenRouter keys.
- Rule for team members: Every designer should generate their own API keys from their personal accounts and input them locally. Do not share keys in plaintext files.
2. Standardizing Rules in Git
While API keys are stored locally, standard configuration parameters (e.g. naming casings, exclusion regex filters, active rules) are saved inside the project’s settings asset:
ProjectSettings/SceneOrganizerSettings.asset
- Recommendation: Commit this file to Git. This ensures that every developer on the team runs scans using the exact same casing rules and validation settings, guaranteeing asset consistency.
.gitignore recommended entries:
----------------------------------
# Keep local user layout configs out of VCS
UserSettings/
Temp/
Library/
# AI Scene Organizer settings (Enforces uniform standard - Keep committed)
!ProjectSettings/SceneOrganizerSettings.asset
3. Sharing Interactive Reports
The Report Exporters tab generates HTML files containing interactive dashboards.
- Save HTML outputs into a shared workspace (like Google Drive, Microsoft Teams, or Slack).
- Use these HTML dashboards during sprint planning or design audits to target layout improvements.
- You can automate report generation as part of a pre-build validation check in Unity.