Skip to main content
Open

Allow for article-level permissions

Related products:CC Knowledge Base
jean.nairon
jessica_owens
colleen_fleming
kraig
andr_raposo
+104
  • jean.nairon
    jean.nairon
  • jessica_owens
    jessica_owens
  • colleen_fleming
    colleen_fleming
  • kraig
    kraig
  • andr_raposo
    andr_raposo
  • elizabeth_04d7d9
    elizabeth_04d7d9
  • tyler_mcnally
    tyler_mcnally
  • matthew_lind
    matthew_lind
  • anthonysabato
    anthonysabato
  • cmultanen
    cmultanen
  • kate_green
    kate_green
  • james_dahlgard
    james_dahlgard
  • sagan_sherlin
    sagan_sherlin
  • heather_hansen
    heather_hansen
  • pele
    pele
  • meenal_shukla
    meenal_shukla
  • spencer_engel
    spencer_engel
  • lori_austin
    lori_austin
  • perry_rogers_10158d
    perry_rogers_10158d
  • lyne_therien
    lyne_therien
  • sacha
    sacha
  • ana_g
  • eriklangston
    eriklangston
  • parimala_agnihotri
  • jamoreman
    jamoreman
  • mwood
  • jenniferpa
    jenniferpa
  • cliff_pape
    cliff_pape
  • tyler_tew
  • davebrown2242
    davebrown2242
  • ml2019
    ml2019
  • gunjanm
    gunjanm
  • andreammelde
    andreammelde
  • kerri.lindstrom
  • HollySimmons
    HollySimmons
  • tammy_c
  • TMaier
    TMaier
  • darshana.shah
    darshana.shah
  • jochle
  • mathieu.brillon
    mathieu.brillon
  • anna-whitehouse
    anna-whitehouse
  • ramos.vonage
  • mikewayner
    mikewayner
  • GraceP
  • cankney
    cankney
  • jlicciardello
    jlicciardello
  • Nalin
  • kumaranbcak
  • clamoureux
  • bradley
    bradley
  • kstim
    kstim
  • JoleneS
  • mindym
    mindym
  • ltsponhour
    ltsponhour
  • Seyi Adesola
    Seyi Adesola
  • iainr
    iainr
  • benwanlessmenlo
    benwanlessmenlo
  • Christina P
    Christina P
  • nmrivas
  • tmorgan
    tmorgan
  • sarahmiracle
    sarahmiracle
  • rachelhibbardtmo
    rachelhibbardtmo
  • josh.broome
  • Cheri
  • Callan-HotDoc
  • alizee
    alizee
  • Molly.McQ
    Molly.McQ
  • yaslongoria
    yaslongoria
  • jestewart
    jestewart
  • TRF
  • Chae Stewart
  • chiggitt
  • ADPNumeroUnoUser
  • AnaCosta
    AnaCosta
  • bnopel
  • Joe-Flanagan
  • jrzlawrence
    jrzlawrence
  • JessicaV
  • jessicatang
    jessicatang
  • Brayden
    Brayden
  • Sai Kiran
    Sai Kiran
  • Alicia Fisk
    Alicia Fisk
  • zdsiegert
    zdsiegert
  • umur.korkut
  • tjohnson
  • amasica1217
    amasica1217
  • Aludow96
  • mbond
    mbond
  • RVN
  • amanda.sepe
  • Alexandra.schwenke
  • emily.silva
  • kerri.keohane
  • ebuessler
  • tzbaby86
  • Tomas Trijonis
    Tomas Trijonis
  • Kornelija_V
  • htesar
  • sarah.kenney
  • mnishimi
    mnishimi
  • K_C_
  • h-kushibiki
  • dcassidy
    dcassidy
  • karibarthel
  • Heather C
  • kelcijowalker
    kelcijowalker
  • marcus samsara
  • mmcgowan
  • tim.carwheel

I would like to be able to “stage” articles in their correct Categories for internal review.

Also, we have “internal-only” product content that should reside in the same place as publicly accessible content (such as internal v. external release notes).

4 replies

  • Gainsight Employee ⭐️
  • 37 replies
  • March 28, 2025

Hi ​@danielwal_coco - correct me if I am wrong but by

I would like to be able to “stage” articles in their correct Categories for internal review.

 

Do you mean you want to have your team review articles before they are available to the public? This may help you:

You should be able to create an article, select the category it should belong to and save if as a draft. You can then find the article in the Article overview page - you can use the filter Status > Draft and Published In > (Category name)

 

Also, we have “internal-only” product content that should reside in the same place as publicly accessible content (such as internal v. external release notes).

 

This is currently not possible - you can only set visibility permissions at the category level where you can set the whole category to be visible or not to certain user roles. It sounds like you wanted to do this at the topic level.

I’d suggest you have a separate category where you place the internal release notes and revoke visibility permissions to users that should not be able to see such content.


  • Author
  • Contributor ⭐️⭐️
  • 3 replies
  • March 28, 2025

Drafts won’t work for us; we have hundreds of folks we’d want to review/access “hidden” content and we don’t want them all to have access to the backend. This should be standard functionality for any purpose-built documentation platform.


  • Gainsight Employee ⭐️
  • 37 replies
  • March 31, 2025

​Thank you for sharing your feedback @danielwal_coco.

We’ll open this idea for further voting so we can monitor and assess this request.


  • Gainsight Employee ⭐️
  • 37 replies
  • March 31, 2025
New IdeaOpen

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings