Project-aware routing · revit tool palette

Send every active document to the right tool palette.

Palette Delegation evaluates the active Revit document, filename, path, and Autodesk user, then loads the designated palette automatically — on startup, document open, document creation, and live document-tab activation.

Open · Create · Switch Filename · Path · User Live palette reconciliation
See delegation behavior ↓ View lifecycle cases
D-A-L-resized-20260504010629-07b70e.png
Delegation Runtime

The active Revit document controls the palette.

When Palette Delegation is enabled, Tool Palette treats the active document as the source of truth. It reconciles visible palettes against the delegation rules, unloads palettes that no longer apply, and loads the palette designated for the current document/user match.

Rules are evaluated in priority order against the active Revit document and the current Autodesk user. Matching can be based on file name, file path, username, or an all-documents fallback. If a more specific rule matches first, that palette wins before any broader fallback rule.

When Delegation Evaluates

Revit cold restartStartup restores the delegated palette for the active/opened document.
Document opened or createdRules run immediately and load the matching palette.
Switch document tabsActivating another already-open document triggers live switch/reconcile.
Close one file, open anotherNext document open re-evaluates and updates the visible palette.
Settings savedDelegation changes refresh the current session against the active document.

Rule Criteria Fields & Operators

Criteria fieldsFile Name · File Path · Username
Operatorscontains · equals · starts_with · ends_with · regex
Priority modelTop rule wins; fallback should sit last.
FallbackAll Documents · All Users
Live Delegation Flow
▶
Revit starts or a model opens
Active document is read: title, file name, full path, and user.
↓ evaluate rules in priority order
▶
Matching rule designates a palette
Example: File Path contains “Healthcare” + Username is a coordinator.
↓ reconcile visible palettes
▶
Unload palettes that no longer apply
A palette from the previous document is hidden if it is not valid for the new active document.
↓ show the current match
▶
User activates another document tab
Delegation runs again and switches to that document’s palette live.
↓ current document owns the UI
✓ Correct delegated palette is loaded for the active document
Startup Palette vs Delegation Rule

Two loading modes — one source of truth.

Startup Palette and Delegation Rule are either/or functions. Startup Palette is the simple default startup loader. Delegation Rule is the project-aware routing system. When Delegation Rule is ON, Startup Palette is ignored for palette loading.

Startup Palette

Use it whenOne default palette should load at Revit startup
Decision sourceManual Startup Palette list
Document matchingNone
User matchingNone
Best forSmall teams · single standard · one office palette

Delegation Rule

Use it whenPalette depends on project, path, filename, or user
Decision sourceDelegation Rule list
Document matchingFile Name · File Path · active document
User matchingWindows username rules
Best forMulti-project · multi-discipline · multi-office teams
Either / Or Logic
A
Delegation Rule OFF
Startup Palette decides what loads when Revit starts. The selection is a fixed startup list, not a document/user test.
or
B
Delegation Rule ON
Delegation rules fully control palette loading. Startup Palette remains saved in settings but is not used while delegation is active.
✓ Exactly one loading mode is active at a time
Delegation Editor Tools

Build, test, and reuse rules before rollout.

Admins can validate rule behavior from the editor instead of opening projects one by one. Use testing and copy tools to keep large rule sets consistent.

🧪

Test Delegation Rule

Run a selected rule against sample document information to confirm which palette would load before publishing the settings to the team.

Preview match result
⧉

Copy rules from

Reuse criteria from an existing palette/rule source, then adjust only the fields that need to change. This is useful when multiple palettes share the same project path, naming convention, or user group.

Reuse known-good rules
🎯

Priority and fallback rules

Put specific rules above broad rules. Use a universal or office-wide fallback rule when a document does not match a project-specific designation.

Specific before general
🔄

Save and refresh live

When delegation settings are saved, the current Revit session can reconcile shown palettes so the loaded UI reflects the latest rule mode and criteria.

No restart for rule edits
Lifecycle Behavior

What happens in real Revit sessions.

Delegation is not just a startup setting. It is a live routing layer that responds to document lifecycle events and active document changes.

🚀

Revit cold restart

On a fresh Revit launch, Tool Palette restores delegated startup palettes after Revit has an active document context. The palette shown is based on the document/user rule match, not a manually remembered palette.

Startup restore
📂

Opening or creating a document

When a model opens or a new document is created, delegation evaluates that document immediately and loads the palette assigned by the highest-priority matching rule.

DocumentOpened · DocumentCreated
🗂️

Multiple documents open

When the user activates another already-open document tab, Tool Palette checks whether the active document changed. If it did, it unloads palettes from the previous document and loads the palette designated for the newly active document.

Live document switch
👁️

Same document, different view

Switching between views inside the same Revit document does not need a full palette swap. The active-document guard prevents unnecessary unload/reload churn.

Document-key guard
⚙️

Delegation settings saved

When rules or startup/toolpalette-delegation settings are saved, the current Revit session refreshes and reconciles the shown palettes against the active document.

Live settings refresh
🛟

Fallback safety

A final all-documents rule gives users a safe default palette when no project-specific file path, file name, or username rule matches.

All documents fallback
Delegation FAQ

Common setup questions.

Use these rules of thumb when deciding between Startup Palette and Delegation Rule, testing a configuration, or supporting teams with several open Revit documents.

What is the main difference between Startup Palette and Delegation Rule?▼
Startup Palette is a fixed startup list. Delegation Rule is conditional routing. Startup Palette asks, “what should open by default?” Delegation Rule asks, “which palette matches this active document and user?”
Can Startup Palette and Delegation Rule both control loading at the same time?▼
No. They are either/or. When Delegation Rule is ON, Startup Palette is ignored for palette loading. When Delegation Rule is OFF, Startup Palette can decide what loads at Revit startup.
When should I use Startup Palette?▼
Use Startup Palette when the same palette should open for everyone regardless of project, file path, filename, or Windows username. It is the simplest setup for one default office standard.
When should I use Delegation Rule?▼
Use Delegation Rule when different projects, disciplines, offices, or users need different palettes. Rules can target File Name, File Path, Username, or a universal fallback.
What happens when several Revit documents are open?▼
The active document owns the palette context. When the user activates another already-open document tab, delegation reevaluates that document and switches to the palette that matches its rule designation.
Does changing views inside the same document switch palettes?▼
No. View changes inside the same document should not cause a delegation switch. The switch is tied to active document changes, document open/create events, and saved delegation setting changes.
How do I test a rule before rolling it out?▼
Use Test Delegation Rule in the editor. Test the expected filename, path, and username conditions, then confirm the result before saving the configuration for other users.
How do I avoid rebuilding similar rules?▼
Use Copy rules from to clone criteria from an existing rule source. After copying, change only the palette target or the few fields that differ for the new project, office, or user group.