# Collabs on docs (specs, marketing plans, etc.) - how do \*you\* handle change management? **URL:** \ **Category:** Get Help\ **Created:** [November 3, 2020, 11:42pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126 "2020-11-03T23:42:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 3, 2020, 11:42pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/1 "2020-11-03T23:42:46Z")
I’ve just started collaborating with a new team in Fibery and in these early stages we are doing a lot of planning, creating specs for things, marketing plans, etc, etc. This process involves multiple members contributing their thoughts to these docs over time. We are wanting a way to highlight changes made by given members, and/or “changes since last visit/view” so we can focus on what’s new as-needed. Unfortunately I don’t see a 100% ideal way to do this effectively in Fibery just yet. The best I’ve come up with is for each user to highlight their own changes and add a comment describing what they did, but it’s clunky and cluttering when you don’t need/want to see those changes, you can’t compare before/after, etc. Obviously [a proper history function](https://community.fibery.io/t/approved-versioning-in-rich-text-fields-and-entities-as-a-whole-too/260) would be great to have. In the absence of that, what’s the best solution you’ve found? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 4, 2020, 12:24pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/2 "2020-11-04T12:24:09Z")
Interesting problem. Indeed versioning would solve this problem, we’ll add this case into History feature. So far it is indeed hard to propose a good solution, just special marks in a text maybe ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 4, 2020, 5:21pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/3 "2020-11-04T17:21:44Z")
> [@mdubakov](#): > > just special marks in a text maybe Yeah, I thought of different editors utilizing different formats, e.g. bold, italic, underline. Obviously there are issues with that though. Simpler and less obtrusive could perhaps be to add distinguishing regular characters to the beginning of edited lines/paragraphs, or even to sort of enclose them. But all of this is hard to clean up later. We’re on the same page, it seems: no perfect way yet, but it’s in the plans, so that’s good. 😃 And we’ll make do for now… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [November 4, 2020, 7:25pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/4 "2020-11-04T19:25:06Z")
I don’t know if you had thought of it, but each user can highlight text that he/she has added and then link to the User entity for him/herself. Anyone can then click on the text and see who added it, and it’s a bit less obtrusive/cluttered than using the comments feature. Plus, if the References extension is enabled for the user type, it’s possible to open a user entity and see everything that a person has contributed. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 4, 2020, 7:47pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/5 "2020-11-04T19:47:14Z")
Oh my god, I _hadn’t_ thought of it!! That’s actually brilliant. Obviously we still need history at some point, but this is basically “manual history” in a sense. Thank you! And on a positive note re: Fibery in its present state, I’ll just say that this kind of flexibility is what helps make it a better option than most any other, despite lacking some features that others may have. Very often you can find a reasonable workaround… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [November 4, 2020, 8:41pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/6 "2020-11-04T20:41:07Z")
> [@Oshyan](#): > > That’s actually brilliant. …Thank you! You’re welcome 😊 By the way, in case it’s not obvious, you might want to recommend that users only highlight/link the headline for a block of text if they’re adding a lot. You can then assume that everything after the headline until the next text block was written by them. Also, you could perhaps ask people to include a date in the headline. > [@Oshyan](#): > > this kind of flexibility is what helps make it a better option than most any other I don’t want to throw more into the mix, but you could also just use #mention of a user prior to typing text… ![adding history](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b7164508c969d3eebd07ad904e151d495954b08f.gif) These both show up in the user entity view references section: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0f240eb02ac967c0ab0e460fc68881fc429e933d.png) ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 4, 2020, 8:47pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/7 "2020-11-04T20:47:37Z")
> [@Chr1sG](#): > > I don’t want to throw more into the mix, but you could also just use #mention of a user prior to typing text… Yeah, I did think of that option, but I find it more obtrusive, especially since it is harder to remove later if/when you want to “finalize” the document. The linked references you suggested first are pretty out-of-the-way, i.e. don’t interrupt the flow of text, and easily removed in the right sidebar if desired. So I think they’re a pretty great solution. Date would be nice to have, and comments could make the date text unobtrusive inside the comment, but I think we can do without dates for now. 👍 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [July 30, 2021, 3:03pm UTC](https://community.fibery.io/t/collabs-on-docs-specs-marketing-plans-etc-how-do-you-handle-change-management/1126/8 "2021-07-30T15:03:00Z")
Docs version history is released and should solve this problem. > [@CHANGELOG: July 30 / Documents and Rich-text History, HubSpot integration](https://community.fibery.io/t/changelog-july-30-documents-and-rich-text-history-hubspot-integration/1855): > > Documents and Rich-Text History Starting this week, rich-text Fields and Documents have version history: [doc-history] Here are a few scenarios when version history can help (or even save the day): Somebody (Alex, you again!) has accidentally erased a significant part of your doc and you need to restore it. There is an unexpected paragraph and you’d like to find out who has added it. You rewrote a specification during an all-nighter — now you’ve sobered woken up and realized it’s all been a…