Document360 FAQs

White labeling refers to removing the ‘Powered by Document360’ logo from your public website.

(more)

Document360 has built-in support for two types of backups – scheduled (automatic – every day at 00:00 UTC) backups and manual (user created) backups. If something goes wrong, like someone accidentally deleted few contents, an admin/owner can easily restore the content from stored backups. (more)

A project is nothing but a knowledge base. It acts like a container for all of your articles, it can have its own branding, security, team members, custom domain etc. You probably will need only one project unless you are a multi-product company and need to maintain different knowledge bases. (more)

Document360 allows you to create and maintain different versions of your entire project documentation. This is useful in few scenarios where you need few different versions of the documentation, example: one for the beta customers, one for the deprecated features, or you are working on next major version of your documentation and you don’t want to mess around with current live one. (more)

Article revisions allows the authors to fork a new revision at the individual article level. Ex: You have a live version of the document, but when new features are added you may want to enhance the article with new content and publish it. There are tools in Document360 to view changes between revisions. (more)

Team Account is a user account in your Document360 project. You can invite and associate the users with any one of the roles like Owner, Administrator, Editor and Draft Writer from the Manage Teams section under Settings. (more)