Version
11.40.4
When setting headers via the collection pre request script when trying to troubleshoot and export the request to a developer using the code snippet option, the headers set via the collection do not show.
Curl snippet:
This does not give the developer an accurate reflection of the request if sharing it.
Hey @annaboek 
Are you setting these headers via a script at the Collection level? If it’s setting these in a script that wouldn’t show in the code snippet.
If this was a Team Workspace, you could invite your teammates to this and they would see exactly what you see without needed to share code snippets.
There are also other Share options available for the Collection and the Request.
Hey @danny-dainton I just like the speed of convenience of this feature. I happened to share a failing request to a dev today and they pointed out they couldn’t see a client-id or client-secret header and we’d added those via a pre-request script to the collection level so you only see those being added when viewing via the console.
It can be quite confusing to other people if they don’t check the scripts at collection level to see other headers added. I get it because they are set inside a pre-request script so wouldn’t show as an inherited header. It would be good as a additional feature if this could be considered.
I didn’t think there was a way round this. We don’t have a paid for licence so can only have 3 people at a time using the workspaces, so don’t tend to use that. To share I would export as json or copy the code snippet.
I’d argue that it’s quicker to be working on the same Collections, in the same Workspaces together, over needing to manual export or copy and paste something. 
For the scripts - That’s where team processes/practices and documentation (Both in line and at the Collection/Folder/Request level) comes into play, for a well documented Collection, there wouldn’t be the need for guess work or confusion as each person would have a reference guide to tell them what and why something has been added.
Feature Request can be raised over on our Github Issue Tracker:
