> ## Documentation Index
> Fetch the complete documentation index at: https://help.draftable.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuring Redline profiles within Group Policy
> This article is for system administrators who are interested in using Group Policy specifically to configure Redline comparison profiles settings for their users using Draftable Legal. This article will show the additional steps required in addition to Group Policy configuration in order to get this setting configured properly.
## Setting up
Ensure you have already followed the [Draftable Group Policy guide](/hc/en-us/articles/18763487262105-Configuring-settings-with-Group-Policy-Draftable-Legal) in respect to adding the templates for the group policy.
Open the Group Policy Editor (via Control Panel)
After installing the group policy template you should see following policies in the **Draftable Legal** section:
## Getting the profile JSON ready
To pre-configure the Redline settings profiles within group policy, you must already have the JSON for profile ready to be added into the group policy setting. To get this, see the process below:
Go to the **Redline** section within the settings menu
Select **Add profile,** then give the profile a name and click **OK**
Start building the profile as required for your user by selecting the settings desired. Then once you have finished building the profile, export it by clicking on the option icon, and then selecting **export**
A new window will appear to save the profile to your desired location. Do so and select **save**
Navigate to where the JSON has been saved and access the file
This is your profile JSON data, and is required for your group policy Redline profile settings. When required, copy the entire JSON string and save it into your group policy, which is outlined in the next step.
## Configuring Redline profiles within group policy
There are a few components to the Redline profiles configuration in group policy. Configuring Redline profiles to be loaded for the user, team allocation for what profiles users can see and setting the default Redline profile used.
### Configuring the team name for user
As an administrator, you can allocate a user to a *team* as a way to further distinguish what profiles they can use from the Redline settings configured by group policy. Mutliple team names can exist, which has the benefit of easily allocating which profiles are loaded for different groups of users.
**Note:** This step is entirely optional, and only required if you wish for certain users to only use certain Redline profiles.
Using the Group policy editor of choice, navigate to the **Draftable Legal** policy templates
Double click on **User Team Name**
Enable the policy and set a string based name for the user in the **Set team name for the user** field. Alternatively, putting a wildcard **\*** for the user, will allow them to see all profiles from all teams.
Click **Apply** and then **OK** for the policy to take effect.
The user now has a team name allocated to their account via group policy.
### Configuring the Redline profiles
You can configure up to 10 Redline profiles that can be automatically loaded into your user machines. Here is how you configure the Redline profiles:
Using the Group policy editor of choice, navigate to the **Draftable Desktop Pro** policy templates
Double click on the Redline setting profile you wish to configure
Enable the policy and paste the Redline profile JSON (that we created using the processed outlined earlier in this article) into the **Paste Redline Profile JSON here** field.
*Optionally:* you can enter the team name of the Redline setting profile, so that only users with that team name can see that profile. If you would like to do this, add the team name in the **Team name** field.
Click **Apply** and then **OK** for the policy to take effect.
Next time your user loads Draftable Legal, the Redline profiles configured in group policy will be loaded for the user to utilize.
### Setting the default profile
You can select the default Redline profile that is used when a user loads Draftable Legal. To do this follow the procedure below:
Using the Group policy editor of choice, navigate to the **Draftable Desktop Pro** policy templates
!\[]
Double click on the **Redline Default Profile Name** policy
Enable the policy and enter the name of the profile you wish to load as default into the **Set default Redline Profile name** field.
**Note:** This is the name of profile you saved it as, not the name of the policy.
Click **Apply** and then **OK** for the policy to take effect.
Next time your user loads Draftable Legal, the selected default Redline profile policy will be loaded.
## Configuring locking specific settings across all Profiles
From v2.15.300, Draftable Legal allows administrators to override any Profile setting using a "Redline Settings Base Profile" in Group Policy. This is designed to allow some Profile settings (e.g. author of changes) to be kept consistent across all profiles while still allowing administrators and end user to create custom profiles by changes other 'unlocked' settings. This section outlines how administrators can lock specific Profile settings across all Profiles with this functionality.
Locking in Draftable Legal is deliberately **per setting, not per profile**. You nominate the individual settings that must stay consistent for everyone, and every setting you do not nominate remains available to the user. This lets you fix the things that matter to the firm, such as the author applied to changes or the redline markup colours, without forcing users to build a profile from scratch when they need to adjust something for the document in front of them.
**Which policy should you use?** A numbered **Admin Redline Profile** governs only itself. Settings in a profile you deploy that way always take precedence over changes a user makes to it, and are restored whenever profiles are reloaded, but they do not carry across to profiles the user creates themselves.
To apply a setting across **every** profile, including profiles users create, put the JSON in the **Redline Settings Base Profile** policy and list the setting in its `Enforced` array. Enforced values are re-applied from the base profile each time profiles are loaded, so a change a user makes to an enforced setting does not persist.
### Configuring and locking specific settings across all Profiles
The "Redline Settings Base Profile" policy looks the same as all other Redline profiles group policy items, but it has the additional configurable property called "Enforced" that can be added to the JSON string.
Administrators can nominate keys (i.e. Redline settings) that are to be "Enforced" at the end of the profile JSON by listing them. This configures the setting using the key in the Redline profile value and locks this setting from end user configuration. Below is an example of the Redline profile JSON showing the **Enforced** key added for locking down settings.
```json expandable theme={null}
{
"Name": "My Profile",
"Version": 1,
"Created": "2024-05-27T11:46:13.6253904Z",
"Updated": "2024-05-27T11:46:13.6253904Z",
"CompareHeadersAndFooters": null,
"CompareBulletsAndNumberings": true,
"CompareTables": false,
"CompareImages": false,
"CompareTextBoxes": true,
"CompareHeaders": true,
"CompareFooters": true,
"CompareCoverPage": true,
"CompareHiddenText": false,
"CompareTablesOfContents": true,
"CompareWatermarks": true,
"CompareFootnotesAndEndnotes": true,
"StyleChangesEnabled": true,
"StyleChangeConfig": 3,
"CommentOption": 0,
"SmallChangesLevel": 0,
"CaseSensitivity": 0,
"DefaultAuthorOption": 1,
"DefaultAuthorCustomOptionValue": "Draftable",
"DefaultAuthorLauncherDropdownVisible": false,
"DefaultSummaryPagePosition": 0,
"DefaultTrackChangesBehaviour": 0,
"MovesEnabled": true,
"RedlineMarkupScheme": {
"TextDeletion": {
"Underline": 0,
"Strikethrough": 1,
"HighlightColour": null,
"TextColor": "181, 8, 46",
"WordApiTextDecoration": 4,
"WordApiTextColor": 6
},
"TextInsertion": {
"Underline": 1,
"Strikethrough": 0,
"HighlightColour": null,
"TextColor": "55, 110, 150",
"WordApiTextDecoration": 3,
"WordApiTextColor": 9
},
"TextMoveFrom": {
"Underline": 0,
"Strikethrough": 2,
"HighlightColour": null,
"TextColor": "44, 98, 52",
"WordApiTextDecoration": 6,
"WordApiTextColor": 11
},
"TextMoveTo": {
"Underline": 2,
"Strikethrough": 0,
"HighlightColour": null,
"TextColor": "44, 98, 52",
"WordApiTextDecoration": 5,
"WordApiTextColor": 11
},
"CellDelete": {
"HighlightColor": "252, 230, 244",
"WordApiCellColour": 0
},
"CellInsert": {
"HighlightColor": "225, 242, 250",
"WordApiCellColour": 2
},
"CellMerge": {
"HighlightColor": "252, 227, 208",
"WordApiCellColour": 4
},
"CellSplit": {
"HighlightColor": "254, 244, 222",
"WordApiCellColour": 1
},
"RevisedLine": {
"Mark": 0
}
},
"FilenameOutputFormat": "",
"Enforced": [
"RedlineMarkupScheme",
"CommentOption"
]
}
```
As you can see above, the keys "CommentOption" and "RedlineMarkupScheme" are now enforced.
Names in the `Enforced` array are **case sensitive** and must be spelled exactly as shown below. An entry that does not match is ignored silently, so the setting stays unlocked with no warning. Check your spelling and capitalisation carefully after editing the array.
`Enforced` takes **setting names**, which are not always identical to the JSON keys used elsewhere in the same profile. The comparison resolution setting is the one to watch: the value is stored under `ComparisonResolution` in current profiles (and under `SmallChangesLevel` in much older version 1 profiles), but the name you must list in `Enforced` is always `ComparisonResolution`.
For reference, the following settings can be listed as enforced.
**What to compare**
```json expandable theme={null}
"CompareBulletsAndNumberings"
"CompareTables"
"CompareImages"
"CompareTextBoxes"
"CompareHeaders"
"CompareFooters"
"CompareCoverPage"
"CompareHiddenText"
"CompareTablesOfContents"
"CompareWatermarks"
"CompareMathEquations"
"CompareFootnotesAndEndnotes"
"CompareFootnoteNumbering"
```
**Comparison behaviour**
```json expandable theme={null}
"ComparisonResolution"
"CaseSensitivity"
"MovesEnabled"
"DetectMovesIntoLargerEdits"
"FlattenDynamicContent"
"IgnoreChangesToQuotationMarks"
"IgnoreWhitespaceChanges"
"IgnoreRunnersInChangedPagesOnly"
"DeduplicateHeaderFooterChanges"
"ShowChangesReport"
```
**Formatting, style and comments**
```json expandable theme={null}
"StyleChangesEnabled"
"StyleChangeConfig"
"CommentOption"
"PreserveAcceptedComments"
```
**Author of changes**
```json expandable theme={null}
"DefaultAuthorOption"
"DefaultAuthorCustomOptionValue"
"DefaultAuthorLauncherDropdownVisible"
"DefaultTrackChangesBehaviour"
```
**Whole setting groups**
Listing one of these names enforces every setting inside that group as a block. You cannot enforce an individual setting from within a group.
```json expandable theme={null}
"RedlineMarkupScheme"
"PowerPointRedlineSettings"
"ExcelRedlineSettings"
```
**Names that no longer work.** Earlier revisions of this article listed the following. They are ignored if you list them today, so remove them from any existing base profile.
| Name | Why it no longer applies | What to do instead |
| - | - | - |
| `CompareHeadersAndFooters` | Split into two separate settings. Only ever applied to version 1 profiles. | List `CompareHeaders` and `CompareFooters`. |
| `SmallChangesLevel` | This is a stored value name, not a setting name. | List `ComparisonResolution`. |
| `DefaultSummaryPagePosition` | Became a global setting in 26.6.0. | Configure the `SummaryPagePosition` registry value. |
| `FilenameOutputFormat` | Became a global setting in 26.6.0. | Configure the `OutputFilenamePatternGlobal` registry value. |
`DefaultViewMode`, `ThreePaneShowComments` and `StripPdfLineNumbers` also became global settings in 26.6.0 and cannot be enforced through a profile. See [Most common Draftable Legal registry configurations](/hc/en-us/articles/24732245077401-Most-common-Draftable-Legal-registry-configurations) for the global registry values that replaced them.
Using the information above, you can prepare your base profile JSON, and once you have your JSON profile ready, go to the Group Policy Editor and find the "Redline Settings Base Profile" item.
Within this policy, paste the entire JSON profile as a string, to use as a base template to add ***enforced*** Redline settings (i.e. to configure and lock the specific Redline setting across all profiles)
**Note:** Enforcing does not allow for a setting to be locked, while still being configurable across different profiles. The enforced setting will be the same for all Profiles and will be based on the "Redline Settings Base Profile" entered in the above policy.
### How enforced settings appear to your users
An enforced setting is applied from your base profile every time profiles are loaded, so a change a user makes to one will not persist.
**Known display issue in 26.6.0 and later.** In the settings interface introduced in 26.6.0, enforced settings are not greyed out and do not show the "Set by your organisation" label. The setting is still enforced and the user's change will not be kept, but the interface does not signal the lock in advance. We are addressing this.
If you are rolling out enforced settings, it is worth telling your users which settings are firm managed rather than relying on the interface to show them.
Rather than writing the JSON by hand, build and export a profile as described in [Getting the profile JSON ready](#getting-the-profile-json-ready) above, then add the `Enforced` array to the exported file.
Exporting also keeps you on the current profile format. The example above is an older version 1 profile, kept because it still loads correctly. Profiles exported from 26.6.0 and later are version 3, and both formats accept the `Enforced` array in the same way.
### Disabling the Draftable Default profile
Administrators can disable the Draftable Default profile by using the policy 'Admin Base Profiles Only' policy.
Open the Group Policy editor
Find the Admin Base Profiles Only policy
Set to **enabled** to remove the Draftable Default profile. Users will still be able to create new profiles but these will be based on the Admin profiles created, and they cannot import any user profiles.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.