The answer to all of the questions is Yes!

Yes, you control user access, as well as what each user can see and do. Do you want certain users to see only a portion of the document? Or only be able to review and comment but not edit? No problem; you decide. And you can put a time limit on user access too.
Yes, multiple users can edit the same document at the same time. And changes and comments made by multiple users are present and visible at the same time.
Yes, you can be sure you will never accidently overwrite other users’ edits or duplicate their work. Everyone can access and edit the same document at the same time and all edits and comments will be present and visible. This is real collaboration.
Yes, all of the content you import or create in the system is impervious to viruses and ransomware. Because ActiveWrite converts content into logical data components and saves each component as its own database object. Viruses are blind to these objects as they don’t touch the file system where viruses live.
Yes, all of the user detail of who viewed, edited or comment on what and when is captured as part of a complete audit trail.
Yes, you control what users can edit – the entire document or only specific sections, paragraphs, or even sentences.
Yes, version control is foolproof. You will never again waste time working on the wrong version of a document. But if you need to, you can always restore a previous version or section of a document.
Yes, you can create multiple sub-versions that use content from a master document. That content will automatically be updated in the sub-versions when the source document is updated. See Document Branching.
Yes, all the content from the master or source document that appears in other instances of that document will be updated as edits are made. But you can also decide to have the reused content remain static and not update automatically. You’re in control.
Yes, you have a complete revision history of the document over time and by user. Nothing is ever lost or overwritten. But there’s more! The system retains all comments, discussions, and annotations on a document as well. See Genealogy.
Yes, in addition to the revision history of a document, all comments, discussions, and annotations are captured too. See Genealogy.
Yes, it’s like having your own time machine. You can wind back the clock to review revision history at any point in time or restore a previous version or section of a document.
Yes, users can vote suggested edits or changes up or down. Easy to determine among the group which edits are preferred.
Yes, it is easy to find and redact content in a document. You can also find and replace content.
Yes, you can import, export, share and work with any document format. And you can always export a document as a PDF, RTF, or plain text.
Yes, it is easy to find content with simple search queries and then drag and drop from one document to another. You can also control if the reused content remains static or if it updates automatically when the source content is updated.
Yes, you can create a content gallery to save frequently used content. You control who has access to the gallery and you can post content. You also control which content remains static and which content updates automatically wherever it has been used when the source content is updated.
Yes, if content from another source has been used in a document, the origin of that content will be captured in document’s complete history.
Yes, an icon will indicate that content is being used in other documents. Just click on the icon for a list of documents. Click on a document in the list to go to that document and see the specific content you are looking for.
Yes, the system highlights the differences between the versions in a side-by-side view.See What’s Different View.
Yes, a simple query will find exactly what you need. Instead of storing documents as files, ActiveWrite converts content into logical data components. So there is no need to index files. No need to remember the name of a file, find it and then open it to discover its content.
Yes, and here’s why. The ActiveWrite system saves edits made to content that has been converted into logical data components. So, it is not resaving the entire document every time an edit is made to it – only those components that were changed. By contrast, conventional file-based systems resave the entire document each time, even if only a single word has been changed.

Let’s say your team is working on a 50-page document and four people submit changes. It doesn’t matter how significant those changes are, a conventional file-based system saves the 50-page document four more times regardless. So you have an additional 200 pages saved for a total of 250 pages. With ActiveWrite, only changes to the content are saved. Say the changes those four people made represent 20% of the document, the ActiveWrite system saves the equivalent of an additional 10 pages of content for a total of 60. Or to put it a different way, 1 MB of content becomes 5 MB of saved content in a file-based system. As ActiveWrite only saves the changes made, 1 MB becomes 1.2 MB of saved content. While these are simple examples, they give you a clear picture of how efficiently ActiveWrite handles data storage compared to conventional file-based systems.