Skip to main content

Restrictions and Protection

  • 9 minutes to read

This topic describes how to prevent end users from document modification. The Rich Text Editor provides three ways to solve this task: protect the entire document from editing, restrict certain operations and prevent users from inserting unnecessary elements.

Restrict Document Modification

You can restrict document modification using the Document.Protect method. This method sets the password, and specifies actions allowed for the protected document (the DevExpress.XtraRichEdit.API.Native.DocumentProtectionType enumeration values). The Document.IsDocumentProtected property indicates whether content modification protection is enabled.

If you want to protect only parts of the document, separate the document into sections and protect specific sections. To do this, use the ProtectedForForms property. For more information on sections, refer to the following topic: Sections.

Use the Document.Unprotect method to disable protection. Note that it unlocks the document without a password request. To prompt the user to enter a password, execute the UnprotectDocumentCommand command.

You can also restrict document modification with Document Protection and Unprotect Document dialogs. For more information, refer to the following topic: Document Protection Dialogs.

Note

The protection mechanism described above affects only the document modification.

Open and Save Password-Encrypted Files

The DXRichEdit allows you to load and save password-encrypted files.

Open an Encrypted File

Specify the DXRichEditDocumentImportOptions.EncryptionPassword property to decrypt a loaded file. The table below lists a chain of events raised if the EncryptionPassword property is not specified or returns an invalid password.

Event Description
RichEditControl.EncryptedFilePasswordRequested Fires if the EncryptionPassword property is not specified or returns an invalid password. Use the EncryptedFilePasswordRequestedEventArgs.Password property to specify a new password.
RichEditControl.EncryptedFilePasswordCheckFailed Occurs if the EncryptedFilePasswordRequestedEventArgs.Password is set to an empty or invalid password. Handle this event to obtain the error that led to this event (Error) and determine whether to prompt a user for a password (TryAgain).
RichEditControl.DecryptionFailed Raised if the TryAgain property is not specified or set to false. This event also occurs if the RichEditControl fails to open an encrypted file. The Exception property indicates the exception that led to this event.

The code sample below shows how to handle the events mentioned above to prompt users to enter a password. If the user cancels the operation or exceeded the amount of attempts to enter the password, the RichEditControl loads an empty file.

View Example: Document Encryption (Simple Example)

int tryCount = 4;

private void RichEditControl1_EncryptedFilePasswordRequested(object sender, EncryptedFilePasswordRequestedEventArgs e)
{
    //Count the amount of attempts to enter the password
    if (tryCount > 0)
    {
        tryCount--;
    }
}

private void RichEditControl1_EncryptedFilePasswordCheckFailed(object sender, EncryptedFilePasswordCheckFailedEventArgs e)
{
    //Analyze the error led to this event
    switch (e.Error)
    {
        case RichEditDecryptionError.PasswordRequired:
            if (tryCount > 0)
            {
                e.TryAgain = true;
                e.Handled = true;
                System.Windows.Forms.MessageBox.Show("You did not enter the password!", String.Format("{0} attempts left", tryCount));
            }
            else
                e.TryAgain = false;

            break;

        case RichEditDecryptionError.WrongPassword:
            if (tryCount > 0)
            {
                if (System.Windows.Forms.MessageBox.Show("The password is incorrect. Try Again?", string.Format("{0} attempts left", tryCount),
                    MessageBoxButtons.YesNo, MessageBoxIcon.Warning) == System.Windows.Forms.DialogResult.Yes)
                {
                    e.TryAgain = true;
                    e.Handled = true;
                }
            }
            break;
    }

}

The RichEditControl.EncryptedFileIntegrityCheckFailed event occurs if the document did not pass the code verification.

Important

If an encrypted file is loaded using the RichEditControl.DocumentSource property, its format cannot be detected. Use the RichEditDocumentSource instance to bind encrypted files.

Encrypt a Document with a Password

Use the Document.Encryption property to access the document encryption options.

richEditControl.Document.Encryption.Type = DevExpress.XtraRichEdit.API.Native.EncryptionType.Strong;
richEditControl.Document.Encryption.Password = "12345";

Call the RichEditControl.SaveDocument(String, DocumentFormat, EncryptionSettings) method overload to password-protect the document on save. Use the DevExpress.XtraRichEdit.API.Native.EncryptionSettings object properties to specify password and protection type.

EncryptionOptions encryptionOptions = new EncryptionOptions();
encryptionOptions.Type = EncryptionType.Strong;
encryptionOptions.Password = "12345";

richEditControl.SaveDocument("EncryptedFile.docx", DocumentFormat.OpenXml, encryptionOptions);

Grant Permission to Users

Create Range Permissions as described in the steps below to allow certain users to edit parts of a protected document.

  1. Set the users and user group lists. The default users list is empty and the user group list contains predefined entries (Everyone, Administrators, Contributors, Owners, Editors and Current User). To use a custom list of users or user groups, provide a custom service implementing the IUserListService or IUserGroupListService interface and register this service with the RichEditControl.ReplaceService<T> method. The RichEditControl does not associate users with groups, so user names and group names are independent.

            richEdit.ReplaceService<IUserListService>(new MyUserListService());
            richEdit.ReplaceService<IUserGroupListService>(new MyGroupListService());
    class MyGroupListService : IUserGroupListService
    {
        List<string> userGroups = CreateUserGroups();
    
        static List<string> CreateUserGroups()
        {
            List<string> result = new List<string>();
            result.Add(@"Everyone");
            result.Add(@"Administrators");
            result.Add(@"Contributors");
            result.Add(@"Owners");
            result.Add(@"Editors");
            result.Add(@"Current User");
            result.Add("Skywalkers");
            result.Add("Nihlus");
            return result;
        }
        public IList<string> GetUserGroups()
        {
            return userGroups;
        }
    }
    class MyUserListService : IUserListService
    {
        List<string> users = CreateUsers();
    
        static List<string> CreateUsers()
        {
            List<string> result = new List<string>();
            result.Add("Nancy Skywalker");
            result.Add("Andrew Nihlus");
            result.Add("Janet Skywalker");
            result.Add("Margaret");
            return result;
        }
        public IList<string> GetUsers()
        {
            return users;
        }
    }
    
  2. The edit permission is given depending on the authentication credentials. To define the identity of the current user, use the AuthenticationOptions class properties.

    //Define the user credentials:
    richEdit.AuthenticationOptions.UserName = "Nancy Skywalker";
    richEdit.AuthenticationOptions.Group = "Skywalkers";
    
  3. Call the SubDocument.BeginUpdateRangePermissions method to access the document range permissions collection.
  4. Create a new RangePermission object using the RangePermissionCollection.CreateRangePermission method.
  5. Utilize the RangePermission.UserName and/or RangePermission.Group properties to specify the specific user and/or the group of users that are eligible to edit the document.

    The table below shows what properties should have the same value to make the range editable to the current user.

    This property value Should be equal to
    DXRichEditAuthenticationOptions.Group RangePermission.Group
    “Everyone”
    DXRichEditAuthenticationOptions.UserName
    DXRichEditAuthenticationOptions.EMail
    RangePermission.UserName
  6. Add the created object to the corresponding collection.
  7. Finalize the modification with the SubDocument.EndUpdateRangePermissions method.
  8. Enable document protection as described above

    RangePermissionCollection rangePermissions = richEdit.Document.BeginUpdateRangePermissions();
    
    RangePermission permission = rangePermissions.CreateRangePermission(rangeAdmin);
    permission.UserName = "Nancy Skywalker";
    permission.Group = "Skywalkers";
    rangePermissions.Add(permission);
    
    RangePermission permission2 = rangePermissions.CreateRangePermission(rangeBody);
    permission2.Group = @"Everyone";
    rangePermissions.Add(permission2);
    
    RangePermission permission3 = rangePermissions.CreateRangePermission(rangeSignature);
    permission3.Group = "Nihlus";
    rangePermissions.Add(permission3);
    
    richEdit.Document.EndUpdateRangePermissions(rangePermissions);
    // Enforce protection and set password.
    richEdit.Document.Protect("123");
    
  9. Customize the appearance of the protected ranges in the document. At runtime, they are highlighted with a certain color and enclosed with bookmark brackets. By default, the highlighting color is selected from a predefined colors collection. This is done to specify different highlighting colors for ranges that belong to different user groups. There is no straightforward way to change these colors manually.

    DXRichEdit_RangePermissions

    You can set the highlighting options to the ranges that are editable to the current user only. To do that, use the RangePermissionOptions properties. They can be accessed through the Options.RangePermissions notation.

    //Customize the editable ranges appearance: 
    richEdit.RangePermissionOptions.HighlightColor = Color.FromArgb(100, 213, 239, 255);
    richEdit.RangePermissionOptions.HighlightBracketsColor = Color.FromArgb(100, 0, 128, 128);
    

Restrict Performing Operations

Protect the document from editing, copying or printing by restricting the corresponding functions. To perform the restriction, access the desired operation using the RichEditControl.BehaviorOptions property and specify its behavior. Depending on the selected property value, the application menu buttons that correspond to restricted operations can be disabled or hidden. Additionally, you can prevent the showing of the context menu. To do that, use the DXRichEditBehaviorOptions.ShowPopupMenu property.

private void RestrictOperations()
   {
     richEditControl.BehaviorOptions.Drag = DocumentCapability.Disabled;
     richEditControl.BehaviorOptions.Printing = DocumentCapability.Disabled;
     richEditControl.BehaviorOptions.Copy = DocumentCapability.Hidden;
   }

The code execution result is illustrated in the picture below. Print, Quick Print and Print Preview are disabled, the Copy item is hidden from the context menu.

OperationRestrictions

Restrict Using Document Elements

You can also forbid the formatting of characters and paragraphs or the use of certain document elements, such as pictures, tables, fields, etc.

These restrictions can be specified by the RichEditControl.DocumentCapabilitiesOptions property, as illustrated in the following code sample.

private void RestrictFormatting()
{
  richEditControl.DocumentCapabilitiesOptions.CharacterFormatting = DocumentCapability.Hidden;
  richEditControl.DocumentCapabilitiesOptions.Comments = DocumentCapability.Disabled;
  richEditControl.DocumentCapabilitiesOptions.FloatingObjects = DocumentCapability.Hidden;
}

The application menu items that correlate with the forbidden actions can be hidden or disabled. If a document is loaded after certain restrictions are applied, the corresponding settings are set to default and the restricted objects are not created. The existing floating pictures are converted into inline pictures, the text boxes and their contents are hidden.

See Also