articles not showing after connection
ART-15726_KNOWLEDGE_NODE-1
is private (i.e., if the article is not shared with everyone in the external system).\n\nThis most frequently occurs if you're a customer success employee who helped a customer do an import and you're verifying the imported data. In that case consult the Airdrop import report:\n\nIf it says that all the extracted articles were created or updated in DevRev, then you can be reasonably sure that that was the case\n\nIf you're still skeptical you can ask the customer to verify that they see the
Visibility of Airdrop-imported articles
ART-15161_KNOWLEDGE_NODE-0
b"Articles and other help center items from Zendesk are intentionally extracted only during manual syncs (tier 2 sync) due to performance considerations. Including article extraction in periodic automatic syncs (tier 1) would significantly impact sync performance and time. Symptoms\n\nCollections with zero articles in DevRev while the same collections in Zendesk contain articles\n\nIncomplete article migration after initial integration setup\n\nArticles not updating in DevRev despite changes in
Zendesk Articles are Extracted Only During Manual Sync
ART-15726_KNOWLEDGE_NODE-0
b"If you just imported a bunch of articles from your favorite external system, but can't see them in DevRev, the most important question to ask yourself is whether that article was shared with you in the external system. Airdrop is permission-aware for articles, so if an article (or document, or page, whatever gets imported as an Airdrop article) was not shared with you in the external system, then you won't have access to it in DevRev (even if you're an admin), assuming the default visibility
Visibility of Airdrop-imported articles
ART-1985_KNOWLEDGE_NODE-39
customers, the article should be visible to customers. If the **Visible to** option is set to **Verified Customers**, only signed-in customers are able to view the article.\n* When sharing an external link with customers, the article status should be *Published*. If it is in *Draft* mode, they won\xe2\x80\x99t be able to view it.\n\nArticle Formatting\n------------------\n\nWhen you\xe2\x80\x99re creating a new article or editing an existing article, formatting options are displayed. While
Articles | Knowledge Base | Computer for Support Teams | DevRev
ART-15726_KNOWLEDGE_NODE-2
articles\n\nAs a last resort, you can ask the Airdrop team to check whether the articles are indeed in DevRev's database"
Visibility of Airdrop-imported articles
ART-15161_KNOWLEDGE_NODE-1
Zendesk Common Scenarios\n\nInitial sync failure : If there's a failure during the initial sync (which is tier 2/manual), the subsequent periodic syncs (tier 1) won't complete the article extraction process.\n\nNew articles added in Zendesk : Articles added to Zendesk after the initial integration will not appear in DevRev until a manual sync is performed. Resolution\n\nTo import or update Zendesk articles in DevRev:\n\nTrigger a manual sync from Zendesk to DevRev through the integration
Zendesk Articles are Extracted Only During Manual Sync
ART-15716_KNOWLEDGE_NODE-19
DevRev documentation or contact support for CSV-specific workflows.\n\nTroubleshooting Missing Migrated Articles\n\nIf you can\xe2\x80\x99t find your migrated articles:\n\nDouble-check the knowledge base section in your DevRev workspace.\n\nConfirm with your admin or implementation team which articles were migrated and to which workspace or project.\n\nSometimes, articles may be in draft/unpublished state or linked to a different part of the product.\n\nIf you still can\xe2\x80\x99t locate
Support queries related playbook
ART-15161_KNOWLEDGE_NODE-2
settings\n\nWait for the sync to complete\n\nVerify that all articles are now showing in DevRev collections Notes\n\nArticle creation dates should be preserved from the original Zendesk articles\n\nAll accessible Zendesk articles should be imported during a successful manual sync\n\nEnsure the account used for integration has sufficient permissions to access all articles in Zendesk"
Zendesk Articles are Extracted Only During Manual Sync
ART-1980_KNOWLEDGE_NODE-29
by customers through the Plug widget and customer portal.\n\nIn the Plug widget, articles are available in two places: the search bar and the Help section.\n\n**Search bar**\n\n![]()\n\n**Help section**\n\n![]()\n\nUsers can also view articles grouped into collections by visiting your help center hosted on your website. The visibility of collections and articles depends on the **Visible to** settings configured.\n\n[### Articles](/docs/product/articles)[###
Knowledge Base | Computer for Support Teams | DevRev
ART-15716_KNOWLEDGE_NODE-11
Answers\n\nMake sure your articles are published and accessible to PluG, and that \xe2\x80\x9cAI Answers\xe2\x80\x9d is enabled in settings. It may take a few minutes for new articles to be indexed. Try reloading the widget or clearing cache. If it still doesn\xe2\x80\x99t work, contact DevRev support.\n\nInstalling the PluG SDK\n\nFor web, you only need the JavaScript snippet. For mobile, check DevRev\xe2\x80\x99s documentation for SDKs. For React Native, follow the release process and update
Support queries related playbook
ART-1985_KNOWLEDGE_NODE-35
and no longer required can be removed by archiving them.\n\nVisibility settings\n-------------------\n\n### Article visibility\n\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\n\n* **Customers**: Allows public access without verification.\n\n  ![]()\n\n  Public access requires the public portal to be enabled. If the public portal is not enabled, only
Articles | Knowledge Base | Computer for Support Teams | DevRev
ART-4215_KNOWLEDGE_NODE-31
pages, update the access manually:\n\n1. Go to **Notion Home**.\n2. Click **Settings** (bottom-left panel).\n3. Under **Accounts > Connections**, find the DevRev integration.\n4. Click the menu (\xe2\x80\xa2\xe2\x80\xa2\xe2\x80\xa2) > **Access selected pages**.\n5. Select additional pages and **Save**.\n\nYou can use the same connection in DevRev to import more Notion pages.\n\n![]()\n\nWhen setting up a new connection for the same workspace, reselect all pages that were linked in the previous
Notion AirSync | AirSync | Snap-ins | DevRev
ART-2040_KNOWLEDGE_NODE-44
will be added, and the article status will be switched to *draft*. While our converter supports Zendesk's native editor tags, we cannot guarantee compatibility with all user-added HTML, potentially resulting in rendering issues and disruptions to the editing experience.\n* The ordering of articles and collections during the initial import and subsequent syncs is not assured. This is because of limitations in how Zendesk transmits positions in its response and how we internally store the rank of
Zendesk AirSync | AirSync | Snap-ins | DevRev
ART-1985_KNOWLEDGE_NODE-38
and **Public Portal**.\n\n### Share an article\n\nOnce you've created an article, you have two options to share it:\n\n* Use **Copy external link** to share with your customers, allowing them to access the article directly.\n* Use **Copy internal link** to share with your internal organizational team members.\n\nThe ability to view the article depends on the settings for **Visible to** and **Status** that have been configured.\n\n* If you are sharing an external link with non-signed-in
Articles | Knowledge Base | Computer for Support Teams | DevRev
ART-16263_KNOWLEDGE_NODE-34
Token** \xe2\x80\x93 the token you generated from Atlassian\n7. After establishing the connection, select the Confluence spaces you want to import.\n8. Map them to the appropriate DevRev parts.\n9. Review the auto-configured field mappings and proceed through each screen.\n10. Once the extraction is complete, view the report showing imported objects:\n\n    * Pages\n    * Blogs\n    * Users\n    * Attachments\n    * Folders\n\nPost-import options\n-------------------\n\nAfter a successful
Confluence Datacenter AirSync | AirSync | Snap-ins | DevRev
ART-1985_KNOWLEDGE_NODE-31
verified customers.\n4. Click **Create** and select whether you want to **Create** an article in draft mode, **Submit for review**, or **Publish**.\n\nTo ensure that the article is visible to your users, the **Status** of the article must be *Published* and the user group must be indicated in the **Visible to** field.\n\n### Edit article content and settings\n\nTo update the content or settings of an existing article, do the following:\n\n1. Go to [**Settings** > **Support** > **Knowledge
Articles | Knowledge Base | Computer for Support Teams | DevRev