The suggested way to omit the Remove button is to not provide a Remove URL/Action.  However this breaks the list of the async upload such that the list doesn't get cleared with each new upload.  Since its an async upload that automatically uploads, there no point in accumulating a list of uploads.  Whether or not you expose a remove button shouldn't be tied in any way to the clearing of the list when a new upload is made.  That should only affect the availability of a remove button. At the very least you could provide some documentation on this quirky behavior.  Instead its random walk of, ok if I change this property what happens, how about this one, how about both, and whirl away a few hours screwing around with unpredictable behaviors.


    @(Html.Kendo().Upload()
                .Name("pdfFiles")
                .Multiple(false)
                .Async(configuration=> configuration
                    .AutoUpload(true)
                    .Save("UploadTemporaryPdf", "StatementOfCredit")
                    //.Remove("RemoveTemporaryPdf", "StatementOfCredit")
                )
                .Events(events=> events
                    .Select("onUploadSelect")
                    .Success("onUploadSuccess")                    
                    .Error("onUploadError")
                 )
                .HtmlAttributes(new { accept = "application/pdf" })