Settings and service profiles
Keep Editor preferences, Core settings and project configuration separate.
AlphaStreaming Hub separates settings by ownership and scope. Check the scope before entering a credential or expecting a setting to travel with a project.
Setting scopes
| Scope | Examples | Travels with a project? |
|---|---|---|
| Editor preferences | Theme, UI language, local hotkeys, panel layout | No |
| Core local settings | Autosave, startup, default project directory, live-state source | No |
| Local service profile | Integration endpoints, account credentials, AI connections and profiles | No, unless a supported explicit protected transfer is selected |
| Project / plugin project state | Automations, selected profiles, OBS entities, configured Stream Deck zones | Included according to the transfer selection |
Workspace preferences adjust the local Editor layout. They do not change the project's automation definitions.
Service profiles
Select the intended service profile before changing a connection. A project's preferred profile can select local configuration, but the project does not normally carry that profile's credentials.
Configure and authorize services in the Editor. Core Settings can reconnect saved plugin connections without opening OAuth or editing parameters.
Local storage
In an ordinary Per-user Editor, non-secret preferences and themes use the Windows Documents Streaming Hub folder. Portable and explicitly isolated Editor data stays within its selected data root. The default project directory does not control the preferences or themes location.
Changing a theme or panel layout does not change the project revision or mark the project dirty. Changes to Core settings and plugin resources have their own validation/version checks.
See Basic settings and Projects.