Post History
This is a decision you need to make in consultation with your company's legal advisors. The ability to defend against claims is affected by both what the warranty says and how prominent it is. A ...
Answer
#3: Attribution notice added
Source: https://writers.stackexchange.com/a/16845 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
This is a decision you need to make in consultation with your company's legal advisors. The ability to defend against claims is affected by both _what_ the warranty says and _how prominent_ it is. A separate document or appendix that people are less likely to read might cause problems in this area. (Never mind that users are trained to skip past all that stuff at the front of manuals in consumer products...) In my position I don't have to deal with warranties but I do have to deal with licensing terms, a similar case. We have restrictions on what you can do with our product based on what license you bought; that text is owned by product management and we technical writers don't alter even one word without discussion. The placement of that documentation in the doc set (ours is part of the bundle too) was worked out with product management. I would personally prefer that this be in a separate document (that product management can then maintain), but it's not my decision to make. I suggest that you consult with your product manager if you have one or your team lead otherwise, to make sure you know all the requirements before you act.