Changes to Guide Article View Permissions

Have more questions? Submit a request

10 Comments

  • Chris Stock

    Is there a corresponding UI change to accompany this, or will permissions still be set via the Section in the UI?

    0
  • James Dietrich

    Hi Chris,

    This change is being made in support of the new permissions model, which will also be surfaced in the UI. For detailed information about the change, please see https://support.zendesk.com/hc/en-us/community/posts/360004271168-The-new-Zendesk-Guide-view-permissions

    1
  • Greg DeVore

    Once this is rolled out on the 27th, when a new article is created via the API will it still inherit the permissions of the Section until January 7th?

    0
  • James Dietrich

    Hi Greg,

    That's right. We will maintain backwards compatibility for writes to articles and sections during the deprecation period (between September 27th 2018 and Jan 7th 2019).

    0
  • Greg DeVore

    @James - do you know when the API docs will be updated to reflect this change?

    0
  • Jennifer Rowe

    Sorry about that, Greg. We are behind on the docs update, but it is in progress now. Should be ready early next week.

    Please let us know if you have a specific question in the meantime and we'll get the API experts to help you out!

    0
  • Harold

    Hi, excellent UI and perspective change, however it poses a challenge to my organisation. We manually create a section and a user segment to restrict it to a certain customer.

    Up until now one of our departments, through the API, generates articles in these sections using only the section ID (and a mapping to their user/customer table). 

    Can we easily match the current section - segment combinations or do I need to manually create a list of section ID's and corresponding segment ID's?

    Also I understand that, as soon as I create a new section, they need to use the new API call because there's no way to add the segment ID to the section through the UI anymore.

    0
  • Terry

    Hey Harold,

     

    Your understanding is correct, after deprecation we will remove the user_segment_id property from the Sections API. Which means you will need to get the segment_id value from the Articles API

    0
  • Tom Morris

    Are you going to replace the /api/v2/help_center/user_segments/{user_segment_id}/sections.json endpoint with an equivalent for Articles?

    1
  • Daniel Pawluk

    Please note the new changeover date of February 8th, 2019 to allow developers more time to incorporate the new required field.

    -1

Please sign in to leave a comment.

Powered by Zendesk