# Include inherited authentication in Documentation **URL:** \ **Category:** Help Hub\ **Created:** [April 6, 2018, 9:26am UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383 "2018-04-06T09:26:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Zoltan](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/zoltan/32/502_2.png) [@Zoltan](https://community.postman.com/u/Zoltan)\ **Post date:** [April 6, 2018, 9:26am UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/1 "2018-04-06T09:26:52Z")
Hi, When authentication is set as inherited in a collection, the collection documentations shows requests as unauthenticated. In my case, since all requests are authenticated, and all use the same details, auth is set on collection level and is inherited everywhere (which seems to be the default as there is no mention of auth in the collection export json when inheritance is used) Screenshots in my other thread about [GET request parameters not showing up in the documentation](https://community.postman.com/t/get-request-params-do-not-show-up-in-documentation/1380) include proof of this one as well (although you will have to take my word for it, that authentication IS configured on collection level 🙂 ) ---
**Author:** ![steffenschebesta](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/steffenschebesta/32/809_2.png) [@steffenschebesta](https://community.postman.com/u/steffenschebesta)\ **Post date:** [August 3, 2018, 2:05pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/2 "2018-08-03T14:05:54Z")
I have the exact same problem. Authorization headers (Basic and Bearer) are not shown at all in the documentation. That of course results in incorrect code being generated. This happens for inherited authorization as well as authorization on the request level. The only difference is that on the request level a small lock is shown (which is probably supposed to show that this call is not publicly accessible). But doesn’t change anything else: ![image](https://us1.discourse-cdn.com/getpostman/original/3X/b/4/b463c979156ae6bcb439b0a12e2fe3c8c3d57252.png) More information in this thread: [https://community.postman.com/t/show-authorization-header-on-documentation/2023](https://community.postman.com/t/show-authorization-header-on-documentation/2023) ---
**Author:** ![jean\_tymate](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/jean_tymate/32/1018_2.png) [@jean\_tymate](https://community.postman.com/u/jean_tymate)\ **Post date:** [October 16, 2018, 12:36pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/3 "2018-10-16T12:36:07Z")
Still no answer from the Postman team about this bug ? My workaround for now is to stop using the option `Inherit from parent` and set Authorization for each Request manually. ---
**Author:** ![godfrzerp](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/godfrzerp/32/11_2.png) [@godfrzerp](https://community.postman.com/u/godfrzerp)\ **Post date:** [October 16, 2018, 12:42pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/4 "2018-10-16T12:42:06Z")
The inherited auth should already be showing up as a “lock” in both the private and public docs. We’re still working on figuring the best way to display the actual auth helper in the docs. ---
**Author:** ![steffenschebesta](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/steffenschebesta/32/809_2.png) [@steffenschebesta](https://community.postman.com/u/steffenschebesta)\ **Post date:** [October 16, 2018, 4:28pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/5 "2018-10-16T16:28:18Z")
@jean_tymate that’s what I also did. Not pretty (at all) but somehow works. @godfrzerp The lock item doesn’t help at all. ---
**Author:** ![steffenschebesta](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/steffenschebesta/32/809_2.png) [@steffenschebesta](https://community.postman.com/u/steffenschebesta)\ **Post date:** [November 21, 2018, 12:28pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/6 "2018-11-21T12:28:32Z")
@godfrzerp any updates on this issue? ---
**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\ **Post date:** [December 9, 2024, 2:34pm UTC](https://community.postman.com/t/include-inherited-authentication-in-documentation/1383/7 "2024-12-09T14:34:42Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.