chromium/components/policy/resources/templates/policy_definitions/Miscellaneous/ManagedBookmarks.yaml

caption: Managed Bookmarks
desc: |-
  Setting the policy sets up a list of bookmarks where each one is a dictionary with the keys "<ph name="NAME">name</ph>" and "<ph name="URL_LABEL">url</ph>". These keys hold the bookmark's name and target. Admins can set up a subfolder by defining a bookmark without a "<ph name="URL_LABEL">url</ph>" key, but with an additional "<ph name="CHILDREN">children</ph>" key. This key also has a list of bookmarks, some of which can also be folders. Chrome amends incomplete URLs as if they were submitted through the address bar. For example, "<ph name="GOOGLE_COM">google.com</ph>" becomes "<ph name="HTTPS_GOOGLE_COM">https://google.com/</ph>".

        Users can't change the folders the bookmarks are placed in (though they can hide it from the bookmark bar). The default folder name for managed bookmarks is "Managed bookmarks" but it can be changed by adding a new sub-dictionary to the policy with a single key named "<ph name="TOPLEVEL_NAME">toplevel_name</ph>" with the desired folder name as its value. Managed bookmarks are not synced to the user account and extensions can't modify them.
example_value:
- toplevel_name: My managed bookmarks folder
- name: Google
  url: google.com
- name: Youtube
  url: youtube.com
- children:
  - name: Chromium
    url: chromium.org
  - name: Chromium Developers
    url: dev.chromium.org
  name: Chrome links
features:
  dynamic_refresh: true
  per_profile: true
future_on:
- fuchsia
owners:
- file://components/policy/OWNERS
- [email protected]
schema:
  items:
    $ref: BookmarkType
  type: array
supported_on:
- android:30-
- chrome.*:37-
- chrome_os:37-
- ios:88-
tags: []
type: dict