Chrome Enterprise Bookmark Bar Settings (2026)

Last updated: April 17, 2026

The Chrome browser’s bookmark bar remains one of the most frequently accessed features for developers and power users who need quick access to documentation, repositories, and internal tools. For organizations deploying Chrome across multiple machines, understanding how to configure bookmark bar settings through enterprise policies becomes essential for maintaining consistency and productivity.

This guide covers the available Chrome enterprise policies related to bookmark bar configuration, practical implementation methods, and real-world examples for IT administrators and developers managing Chrome deployments.

Understanding Chrome Enterprise Policies for Bookmarks

Chrome Enterprise provides multiple policy options to control bookmark bar behavior across managed browsers. These policies live under the ChromeBrowserSettings policy namespace and can be deployed through Group Policy (Windows), configuration profiles (macOS), or JSON configuration files for Chrome Browser Cloud Management.

The primary policies you’ll work with include:

BookmarkBarEnabled. Controls whether the bookmarks bar displays
BookmarkBarLocation. Sets the bar’s position (never, top, or bottom)
ImportBookmarksFromFile. Pushes a predefined bookmarks file to users
SyncDisabled. Prevents bookmark sync when you need local-only bookmarks
ManagedBookmarks. Creates an immutable bookmarks folder that users cannot modify

Understanding when to use each policy requires knowing what problem you’re solving. A small development team standardizing their browser environment has different needs than a hospital network running shared kiosk terminals. The policies are designed to compose together, so most real deployments combine two or more settings.

Policy Delivery Methods

Before diving into specific policies, it’s worth understanding the delivery mechanisms available across platforms. The same JSON values work everywhere, but how you push them varies:

Platform	Primary Method	Secondary Method
Windows	Group Policy (GPO via ADMX templates)	Registry keys under `HKLM\Software\Policies\Google\Chrome`
macOS	Configuration Profile (.mobileconfig via MDM)	Managed Preferences plist at `/Library/Managed Preferences`
Linux	JSON file at `/etc/opt/chrome/policies/managed/`	N/A
ChromeOS	Google Admin console (Device Management)	N/A
Cloud-managed	Chrome Browser Cloud Management in Admin console	N/A

For Windows, Google provides ADMX template files on the Chrome for Enterprise download page. After importing them into your Group Policy Central Store, all Chrome policies become browsable in the Group Policy Editor under Computer Configuration > Administrative Templates > Google Chrome.

Configuring Bookmark Bar Visibility

The most basic enterprise control involves toggling the bookmark bar’s visibility. In Microsoft Windows environments using Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Google Chrome > Bookmark Bar and enable the appropriate policy setting.

For organizations using JSON-based deployment, the equivalent configuration looks like this:

{
 "BookmarkBarEnabled": true,
 "BookmarkBarLocation": "top"
}

Setting BookmarkBarLocation to "top" places the bar below the address bar, while "bottom" positions it above the browser tabs. Some organizations prefer "never" to completely hide the bar and encourage users to access bookmarks through the bookmarks manager instead.

One nuance worth noting: BookmarkBarEnabled and BookmarkBarLocation interact. If BookmarkBarEnabled is set to false, the location setting becomes irrelevant. If you set BookmarkBarLocation to "never", that effectively disables the bar regardless of the enabled setting. For clarity, explicitly set both values when hiding the bar.

Forcing vs. Recommending

Chrome enterprise policies support two modes: forced and recommended. A forced policy cannot be changed by the user. A recommended policy sets a default that users can override. The JSON key format differs:

{
 "policies": {
 "BookmarkBarEnabled": true
 },
 "recommended": {
 "BookmarkBarLocation": "top"
 }
}

For most IT environments, you’ll use forced policies for security-sensitive settings and recommended policies for convenience settings. The bookmark bar location is often a good candidate for a recommended policy. you can set the default to "top" without locking users out of personalizing their workspace.

Deploying Managed Bookmarks

The ManagedBookmarks policy creates a mandatory bookmarks folder that appears in every user’s bookmark bar. Users cannot delete, rename, or move these bookmarks, making this ideal for compliance requirements, safety links, or organization-wide resources.

Here’s an example JSON configuration for managed bookmarks:

{
 "ManagedBookmarks": [
 {
 "toplevel_name": "Corporate Resources"
 },
 {
 "name": "IT Help Desk",
 "url": "https://helpdesk.yourcompany.com"
 },
 {
 "name": "Internal Wiki",
 "url": "https://wiki.yourcompany.com"
 },
 {
 "children": [
 {
 "name": "Production API",
 "url": "https://api.yourcompany.com/v1"
 },
 {
 "name": "Staging API",
 "url": "https://staging-api.yourcompany.com/v1"
 }
 ],
 "name": "API Endpoints"
 }
 ]
}

This configuration creates a top-level folder called “Corporate Resources” containing direct bookmarks and a nested “API Endpoints” folder. The structure supports unlimited nesting depth, though keeping it shallow improves usability.

Naming the Top-Level Folder

The toplevel_name key sets what the managed folder is called in the bookmarks bar. This is separate from having a name key on the same object. only the first object in the array should use toplevel_name, and it acts as the container for all subsequent entries. If you omit toplevel_name, Chrome defaults to calling the folder “Managed bookmarks,” which looks informal in a professional setting.

Choose a name that clearly signals the folder’s purpose. “Corporate Resources” and “IT-Managed Links” work well. Avoid names like “Admin” or “Required” that might cause user anxiety.

Updating Managed Bookmarks

When you need to add or remove managed bookmarks, update the policy JSON and push it through your deployment mechanism. Chrome picks up policy changes on browser restart and during periodic policy refresh cycles (typically every 3 hours for domain-joined machines). Users don’t need to take any action.

A practical workflow: maintain a canonical managed-bookmarks.json file in your policy repository, run it through a JSON validator in your CI pipeline before pushing, and deploy through your MDM or GPO infrastructure. This prevents broken JSON from silently wiping managed bookmarks across the organization.

Importing Bookmarks at Scale

When migrating from another browser or standardizing across departments, the ImportBookmarksFromFile policy pushes a bookmarks HTML file to all managed browsers. The browser imports these bookmarks alongside existing user bookmarks unless you’ve disabled bookmark sync.

{
 "ImportBookmarksFromFile": "\\\\fileserver\\policies\\default-bookmarks.html"
}

Windows deployments typically use UNC paths, while macOS and Linux support both file paths and URLs pointing to downloadable bookmark files.

The bookmarks HTML format is the standard Netscape bookmark format, which all major browsers can export. Here’s a minimal example of what that file looks like:

<!DOCTYPE NETSCAPE-Bookmark-file-1>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<TITLE>Bookmarks</TITLE>
<H1>Bookmarks</H1>
<DL><p>
 <DT><H3>Company Tools</H3>
 <DL><p>
 <DT><A HREF="https://jira.yourcompany.com">Jira</A>
 <DT><A HREF="https://confluence.yourcompany.com">Confluence</A>
 </DL><p>
</DL>

An important distinction: ImportBookmarksFromFile runs once on browser startup and imports the bookmarks into the user’s personal bookmark collection. This means users can delete, edit, and move these bookmarks after import. If you need bookmarks to remain permanent and uneditable, use ManagedBookmarks instead. Use ImportBookmarksFromFile primarily for onboarding new users with a useful starting set.

Controlling Sync Behavior

Organizations with strict data governance policies often disable Chrome’s built-in sync to prevent bookmarks from flowing to Google’s servers. The SyncDisabled policy accomplishes this:

{
 "SyncDisabled": true
}

When sync is disabled, managed bookmarks still appear, but users lose the ability to synchronize their personal bookmarks across devices. Consider whether your organization actually needs to disable sync, many businesses benefit from allowing users to access their personal bookmarks while still providing managed corporate bookmarks.

A more surgical approach uses SyncTypesListDisabled to disable sync for specific data types without blocking everything:

{
 "SyncTypesListDisabled": ["bookmarks"]
}

This prevents bookmark sync while still allowing Chrome to sync extensions, history, and passwords. For environments where employees use both work and personal Google accounts in separate Chrome profiles, this approach gives better granularity than a blanket sync disable.

Practical Implementation Examples

Development Team Configuration

For development teams, you might combine multiple policies to create a standardized environment:

{
 "BookmarkBarEnabled": true,
 "BookmarkBarLocation": "top",
 "ManagedBookmarks": [
 {
 "toplevel_name": "Dev Resources"
 },
 {
 "name": "GitHub",
 "url": "https://github.com"
 },
 {
 "name": "Stack Overflow",
 "url": "https://stackoverflow.com"
 },
 {
 "children": [
 {
 "name": "Jira",
 "url": "https://yourcompany.atlassian.net"
 },
 {
 "name": "Confluence",
 "url": "https://yourcompany.atlassian.net/wiki"
 }
 ],
 "name": "Project Management"
 }
 ],
 "SyncDisabled": false
}

Development teams benefit from keeping sync enabled. engineers often switch between laptops and workstations and expect their bookmarks to follow them. The managed folder supplements rather than replaces their personal bookmarks.

Kiosk or Shared Device Configuration

For shared workstations where you want to prevent users from saving personal bookmarks:

{
 "BookmarkBarEnabled": true,
 "BookmarkBarLocation": "bottom",
 "ManagedBookmarks": [
 {
 "toplevel_name": "Allowed Sites"
 },
 {
 "name": "Company Portal",
 "url": "https://portal.yourcompany.com"
 }
 ],
 "SyncDisabled": true
}

On kiosk machines, placing the bar at the bottom makes sense if you’re also hiding the address bar using AddressBarEditingEnabled: false. Users see only the managed bookmarks, and nothing they do persists between sessions if you’re also using Chrome’s guest mode or profile reset policies.

Regulated Industry Configuration

Healthcare, finance, and legal environments often need tighter controls. A configuration for a regulated environment might look like:

{
 "BookmarkBarEnabled": true,
 "BookmarkBarLocation": "top",
 "ManagedBookmarks": [
 {
 "toplevel_name": "Approved Resources"
 },
 {
 "name": "Compliance Portal",
 "url": "https://compliance.yourcompany.com"
 },
 {
 "name": "Approved Vendor List",
 "url": "https://intranet.yourcompany.com/vendors"
 }
 ],
 "SyncDisabled": true,
 "SyncTypesListDisabled": ["bookmarks", "history"],
 "IncognitoModeAvailability": 1
}

Setting IncognitoModeAvailability to 1 disables incognito mode entirely, ensuring all browsing is logged and bookmarks remain within the managed environment.

Verification and Troubleshooting

After deploying policies, verify they’re applied correctly by navigating to chrome://policy in the browser. This page shows all active policies and their current values, along with status indicators showing whether each policy loaded successfully.

The policy page is your first stop for any policy issue. Each entry shows:

Policy name: Matches the JSON key exactly
Value: What Chrome read from the policy source
Status: “OK” for successful policies, or an error message
Source: Whether the policy came from cloud, machine, or user policy level
Level: Mandatory vs. recommended

Common issues include:

Policy not showing: Ensure the policy file is in the correct location and the browser has restarted after policy application. On Linux, the file must be owned by root and not writable by other users, or Chrome will reject it for security reasons.
Managed bookmarks not appearing: Check that the JSON syntax is valid, missing commas or incorrect bracket placement breaks the entire policy. Run your JSON through python3 -m json.tool policy.json before deploying to catch syntax errors.
User can still edit managed bookmarks: Verify you’re using the ManagedBookmarks policy rather than ImportBookmarksFromFile, which imports but doesn’t lock bookmarks.
Policy shows correct value but nothing changes: Some policies require a full browser restart, not just a tab reload. Quit Chrome completely and relaunch. On managed devices, run gpupdate /force on Windows or sudo profiles -I -F policy.mobileconfig on macOS to force policy re-application.
Policies applying to one user but not another on shared machine: Confirm whether you’ve placed the policy under Machine configuration or User configuration in GPO. Bookmark bar policies should typically live under Machine configuration to affect all users uniformly.

Additional Considerations

The bookmark bar policies work alongside other Chrome enterprise settings like HomepageLocation and NewTabPageLocation to create a cohesive browser experience. For highly regulated industries, combining bookmark policies with IncognitoModeAvailability and BackgroundModeEnabled provides tighter control over browser behavior.

Chrome checks for policy updates on browser startup and periodically while running. Users with administrator privileges can temporarily override some policies through the browser’s advanced settings, though managed bookmarks and explicitly-enabled policies remain enforced.

For Chrome Browser Cloud Management customers, these same policies apply but can be pushed through the Google Admin console interface rather than local policy files, a simpler approach for organizations without traditional Active Directory infrastructure. Cloud management also provides reporting that shows which policies are active across your fleet, which is useful for auditing compliance and troubleshooting outlier machines.

One final consideration for organizations rolling out bookmark policies for the first time: communicate the change to users before pushing it. Users who suddenly see a new “IT-Managed” folder in their bookmarks bar without explanation sometimes file help desk tickets or attempt workarounds. A brief email explaining what the folder is, why it’s there, and that it’s normal goes a long way toward reducing friction during rollout.

This took me 3 hours to figure out. I put it in a CLAUDE.md so I'd never figure it out again. Now Claude gets it right on the first try, every project. 16 framework templates. Next.js, FastAPI, Laravel, Rails, Go, Rust, Terraform, and 9 more. Each one 300+ lines of "here's exactly how this stack works." Copy into your project. Done. **[See the templates →](https://zovo.one/lifetime?utm_source=ccg&utm_medium=cta-config&utm_campaign=chrome-enterprise-bookmark-bar-settings)** $99 once. Yours forever. I keep adding templates monthly.