Enhance Portal Link Sharing to Display Article Name Along with Project Name
under review
Uppili Srinivasan
When sharing a portal article URL in platforms such as Microsoft Teams, Confluence, or Jira, the link appears as:
A raw URL (e.g., https://portal.document360.io/projectID/document/v1/view/articleID)
or
“Documentation – [Project Name]” with the link embedded
When multiple article links are shared in the same thread, they all appear identical, making it difficult to distinguish between them without opening each link individually.
Use Case:
Portal links are frequently shared with leadership teams for review and approval before publishing. Since the preview only displays the project name (and not the article name), reviewers must click and open every link to identify the specific article.
This creates unnecessary friction in review workflows, especially when multiple articles are under review simultaneously.
When copying and sharing portal article links, the preview should display:
Documentation – [Project Name] – [Article Name]
Note: We do not want to use the private link for this functionality as we don't have track of the user who has created the private link and the list of articles which has the private link.
Log In
Mohamed Shakheen
marked this post as
under review
Mohamed Shakheen
Hi Keppel green Cattle
Thank you for sharing the detailed context. I understand the concern regarding the link preview when portal article URLs are shared in platforms such as Microsoft Teams, Confluence, or Jira. Since the preview currently shows only “Documentation – [Project Name]”, multiple shared links appear identical, which makes it difficult for reviewers to quickly identify the respective article without opening each one. This can certainly add friction when several articles are under review simultaneously.
Regarding the suggested improvement to display “Documentation – [Project Name] – [Article Name]” in the preview, we will evaluate the feasibility of enhancing the metadata so that the article title is reflected when the link is shared. This would improve clarity during collaboration and review workflows.
In the meantime, I would like to understand the review process a bit better. If the primary use case is internal leadership review before publishing, have you considered using the workflow/status-based review process within Document360? By updating the article status in the workflow, reviewers can directly view the articles that require review from the dashboard, which may streamline the approval process without relying on shared portal links.
Uppili Srinivasan
Created on behalf of Keppel green Cattle