Settings

Overview

Settings control defaults and behavior at the Account, Organization, or Project level.

Key Concepts

• Account settings: affect every Organization and Project
• Organization settings: affect the Organization and Projects inside it
• Project settings: affect a single Project
• Default: starting value applied to new items

How It’s Used

Use Settings during rollout and when governance changes. Use Account settings for shared fields and controls. Use Project settings for delivery-team workflow defaults.

Benefits

• More consistent workflows across Projects
• Cleaner reporting through standardized fields
• Reduced access drift through scoped configuration

Setup Steps

1

Open settings at the required scope

Open settings from Account, Organization, or Project navigation.

2

Apply changes with governance in mind

Prefer Account-level settings for shared fields. Use Project settings for initiative-specific workflows.

Best Practices

• Document field meanings and status definitions in a shared SOP.
• Duplicate shared configurations before major changes.
• Review settings quarterly to remove unused fields and templates.

Summary

Settings control defaults and behavior by scope.

Account settings standardize shared fields.

Project settings shape delivery workflows.

Related:

• Account Configuration
• Project Settings and Configuration