Track Resource for Documented Workflow within the Tool
backlog
C
Concrete Swordfish
In Doc360, there are several places where a certain action like creating a redirect rule or fixing a broken link does not show the person responsible for performing that action.
Now there are two reasons; accountability and record keeping. We have multiple apps within our software and each is suited to a different category of customers. To cater to that, internal resources are accordingly assigned to deliver the best possible documentation experience.
Often there is overlap between resources and when two or more teams work together, mistakes can occur. Following areas are without any visible resource tracking:
- 'URL Mapping' in Knowledge base widget
- 'Article redirect rules' in Site builder
- 'Style guide' in Site builder
- 'Variables' in Content tools
- 'Snippets' in Content tools
- 'Glossary' in Content tools
For Glossary, we're already awaiting a Category-based glossary implementation, but to not able to sort via 'Last Modified by' or 'Created by', etc. makes the job very cumbersome.
Similarly:
- 'Import and export project' in Content tools
- 'Export to PDF' in Content tools
- 'Manage links' in Analytics
While Team auditing is available, however it's a global setting to monitor any compliance issues.
We request you extend the existing functionality to the areas above.
- 'Templates' in Content tools
- Recycle bin
- Audit trail functionality at the article level
The ask is a genuine business use case of 'who did what.'
Tl;dr: Add a column 'Last Modified by' / 'Created by' to aforesaid settings/config pages.
Log In
D
D360 Product Management
marked this post as
backlog
K
Kavya
Hi Concrete Swordfish,
Thank you for sharing this detailed and well-articulated request. We completely understand the underlying business need here—accountability, traceability, and clear ownership of changes (“who did what”) are essential, especially when multiple teams collaborate across different products and documentation scopes.
You’ve rightly pointed out that while Team Auditing exists, it operates at a global level and doesn’t fully address day-to-day operational needs across several configuration and content areas. Extending visibility such as “Created by” and “Last modified by”to the areas you mentioned would certainly improve usability, governance, and collaboration.
That said, this request spans multiple touchpoints across the product, including:
* Knowledge Base widget configuration
* Site Builder settings
* Content tools (variables, snippets, glossary, templates, imports/exports, PDF exports)
* Analytics and link management
* Recycle bin and article-level audit trails
Because of the breadth and impact across multiple modules, this will require deeper analysis from both product and engineering perspectives to evaluate feasibility, consistency, and performance implications. To move this forward in a structured way, we recommend formally tracking this as an improvement so we can assess scope and prioritize it based on customer traction and overall effort.
Once reviewed, we’ll be better positioned to share guidance on what can be taken up and potential timelines. We truly appreciate the clarity and depth of the use case—it’s extremely helpful for long-term planning.