Set AutoFilter on for new projects
| Registry value | set autofilter on for new projects |
| Group Policy | Set AutoFilter on for new projects |
| German version | AutoFilter bei neuen Projekten aktivieren |
| Intune settings catalog | Set AutoFilter on for new projects (User) |
| Scope | User · HKCU |
| ADMX | proj16.admx · L_PjSetAutoFilter |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\ms project\options\general | |
| set autofilter on for new projects | Enabled = 1 · Disabled = 0 |
Not configured = the value does not exist – the application default applies and users may change the setting.
PowerShell
Check the current value (read-only)
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\general"
foreach ($name in @('set autofilter on for new projects')) {
try { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
catch { '{0}: not configured' -f $name }
}Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.
Enable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\general"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'set autofilter on for new projects' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # Enabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Disable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\general"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'set autofilter on for new projects' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # Disabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Reset to Not configured
# --- Settings --- $root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>' $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\general" Remove-ItemProperty -Path $key -Name 'set autofilter on for new projects' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Set AutoFilter on for new projects (User)
Settings catalog → Add settings → search for the name above.
Intune Settings Catalog Viewer ↗
Alternative: custom profile (OMA-URI)
| OMA-URI | ./User/Vendor/MSFT/Policy/Config/proj16v2~Policy~L_Proj~L_ProjectOptions~L_PjGeneral~L_PjGeneralProjOptions/L_PjSetAutoFilter |
| Data type | String |
| Value | <enabled/> · <disabled/> |
Cloud Policy
Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Set AutoFilter on for new projects. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting turns on AutoFilter automatically when the user creates a new project.
If you enable or do not configure this policy setting, AutoFilter is automatically turned on when users create a new project.
If you disable this policy setting, AutoFilter is not automatically turned on when users create a new project.
Same category: Microsoft Project 2016 › Project Options › General › General options for Microsoft Project
- Open last file on startupstart with last file
- Prompt for project info for new projectsask for summary info at new
- Number of projects in the Recent Projects listmax display
- Number of folders in the Recent Folders listmax display
All policies in this category · All 140 policies of proj16.admx