{"id":605,"date":"2017-07-25T12:34:34","date_gmt":"2017-07-25T10:34:34","guid":{"rendered":"https:\/\/codesavory.com\/demo\/?post_type=knowledgebase&p=605"},"modified":"2021-06-30T16:24:09","modified_gmt":"2021-06-30T14:24:09","slug":"content-restriction","status":"publish","type":"knowledgebase","link":"https:\/\/basepresskb.com\/docs\/knowledge-base\/features\/content-restriction\/","title":{"rendered":"Content Restriction"},"content":{"rendered":"
<\/span><\/div>
Info<\/div>
The Content Restriction<\/strong> is a Premium feature.<\/p>\n

Upgrade today<\/a> to take your documentation to the next level!<\/div><\/section>\n

The BasePress Content Restriction feature gives you full control over the content in your knowledge base. It lets you decide who can see and read any of the articles, sections or KBs in your documentation.<\/p>\n

To enable Content Restriction navigate to BasePress >Settings >Content Restriction<\/em> and click on ‘Enable\u00a0content restriction’<\/strong>.<\/p>\n

\"BasePress
BasePress Content Restriction Settings<\/figcaption><\/figure>\n

Once activated you’ll find a new field in the knowledge base, sections and the articles’ editor called ‘Visible to’<\/strong> with a list of user roles. You can\u00a0 select each role individually or in any combination in order to only allow users with a specific role to view certain content. By default all users can see new content. To restrict the content deselect the roles you don’t want to have access to the articles. Shown in the screenshot below:<\/p>\n

 <\/p>\n

\"Restriction
Restriction roles<\/figcaption><\/figure>\n

There are some settings to adjust, in order to determine how content restriction functions in your knowledge base.
\nSee the full list of\u00a0 content restriction settings<\/a>.<\/p>\n

The most important setting is: “Redirected Pages” <\/strong>since it influences what users can see. Redirected Pages has three options and they work as follow:<\/p>\n

    \n
  1. All Pages<\/strong>
    \nAll the restricted knowledge bases, sections and articles are visible ONLY<\/strong> to users that have access to them. They won’t appear in any page, widget or search. Direct access to any of these pages will lead to a 404 error page as if the content isn’t present in the website.<\/li>\n
  2. None<\/strong>
    \nAll the restricted knowledge bases, sections and articles are visible to ALL<\/strong> users. They’ll appear in all pages, widgets and searches. It restricts only the content of the article. Anyone that doesn’t have the right role to view the content sees a content restriction notice. Optionally a content teaser with a login form.<\/li>\n
  3. Section Only
    \n<\/strong>This is a combination of the first two options. All restricted knowledge bases, sections and articles are visible ONLY<\/strong> to users that have access to them, similar to the first option. Yet if someone accesses an article with a direct link the article shows a restricted notice as in the second option.<\/li>\n<\/ol>\n

    This screenshot shows a restricted page notice:<\/p>\n

    \"Restricted<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    The BasePress Content Restriction feature gives you full control over the content in your knowledge base. It lets you decide who can see and read any of the articles, sections or KBs in your documentation. To enable Content Restriction navigate to BasePress >Settings >Content Restriction and click on ‘Enable\u00a0content restriction’. Once activated you’ll find a […]<\/p>\n

    Read More… from Content Restriction<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","knowledgebase_cat":[21],"knowledgebase_tag":[],"class_list":["post-605","knowledgebase","type-knowledgebase","status-publish","hentry","knowledgebase_cat-features"],"_links":{"self":[{"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase\/605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase"}],"about":[{"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/types\/knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/comments?post=605"}],"version-history":[{"count":4,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase\/605\/revisions"}],"predecessor-version":[{"id":1649,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase\/605\/revisions\/1649"}],"wp:attachment":[{"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/media?parent=605"}],"wp:term":[{"taxonomy":"knowledgebase_cat","embeddable":true,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase_cat?post=605"},{"taxonomy":"knowledgebase_tag","embeddable":true,"href":"https:\/\/basepresskb.com\/docs\/wp-json\/wp\/v2\/knowledgebase_tag?post=605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}