Settings reference
All project configuration lives in the Dousen web management portal at /portal/ and is admin-only. The desktop app no longer carries admin settings — it is purely a client that reads whatever the portal publishes. This page is your reference for the project-level settings an admin edits there.
Where settings live
Each project in the portal holds several YAML documents plus a few scalar fields, all edited from the project view:
| Setting | What it controls |
|---|---|
| Pipeline settings | Export/import behavior, texture rules, custom validator paths, OCIO, Jira-on-submit. Covered on this page. |
| Naming conventions | Asset naming rules. See Naming conventions. |
| Validators | Pre-export and admin asset checks. See Asset validation. |
| Jira config | Base URL, project key, account email, API token. The token is write-only and shown masked once saved. |
| Perforce depot path | The depot path used to auto-create artist workspaces. See Perforce. |
Pipeline settings
Pipeline settings are a single YAML document per project. The recognized keys are below; unknown keys are ignored, so studio-specific notes can live alongside them.
| Key | Meaning |
|---|---|
| export_presets.<dcc>.<key> | Per-DCC export defaults. Supported DCCs: blender, maya, 3dsmax, houdini, substance_painter, substance_designer. |
| texture.allowed_formats | List of texture file formats artists may export, e.g. [png, tga, exr, tif]. |
| validators.extra_paths | Folders to load custom validators from. See Asset validation. |
| app_paths.<dcc>.startup_scripts | Studio scripts run after Dousen's own DCC initialization. See Loading studio tools. |
| jira.on_submit_transition | Jira transition applied when a changelist is submitted. See Jira tasks. |
| ocio.config_path | Shared OCIO config path. Blank means each DCC uses its own default. |
Export presets
Each preset is keyed by DCC, then by a leaf setting. Recognized leaf keys:
fbx_version— e.g.FBX202000,FBX201900,FBX201800axis_forward,axis_up,up_axis— export orientationalembic_format—OgawaorHDF5format— texture/render output format:tga,png,exr,tif,jpg
Texture rules
texture.allowed_formats restricts which file formats artists may export from texturing DCCs.
Texture size limits — texture.max_resolution and texture.resolution_power_of_2 — are validator rules set in the Validators tab, not pipeline settings. See Asset validation.
Custom validators
validators.extra_paths lists folders Dousen loads extra validators from. Each entry can be a Perforce path (//depot/...), a path relative to the source root, or an absolute path.
Startup scripts
app_paths.<dcc>.startup_scripts lists studio scripts that run after Dousen's own DCC init — use this to inject existing pipeline tools without disrupting the addon. Full guide: Loading studio tools.
Jira on submit
jira.on_submit_transition names the Jira transition applied automatically when a linked changelist is submitted. Matching is case-insensitive; leave it blank to disable. See Jira tasks and Perforce.
Color management
ocio.config_path points every DCC at a shared OCIO config. Blank means each DCC keeps its own default color setup.
Example
YAMLexport_presets:
blender:
fbx_version: FBX202000
axis_forward: -Z
axis_up: Y
maya:
fbx_version: FBX201900
up_axis: y
houdini:
alembic_format: Ogawa
texture:
allowed_formats: [png, tga, exr, tif]
validators:
extra_paths:
- //depot/pipeline/dousen/validators
- ./tools/validators
jira:
on_submit_transition: In Review
ocio:
config_path: //depot/color/aces/config.ocio
API endpoint
The portal reads and writes pipeline settings through:
| Method | Endpoint |
|---|---|
| GET | /api/projects/:id/settings |
| PUT | /api/projects/:id/settings |
The body is the settings YAML. Mutations are admin-only. Saved settings are distributed to clients with a short cache, so a change reaches artists within a few minutes without a restart.
Asset versioning (not a setting)
Dousen keeps immutable asset versions for published work — each version records the Perforce changelist, the Jira key, and who published it, along with the version's file representations and dependencies. This is read-only history available through the API; there is nothing to configure here.