Questions

An archive for an organisation’s documents. People file records into libraries, search the extracted text, and ask a question that comes back with the page it came from.

PDF, Word, plain text, and Markdown, up to 25 MB. Opening a file hands it to the browser. A preview drawn inside Dox is planned.

Libraries are the only container in this release. Folders, departments, and projects are planned. Custom fields beyond the title, description, and filename are planned too.

A later upload keeps the earlier file. The document panel lists each version, its filename, and its processing state. Choosing an older version and making it current is planned.

The text extracted from the document. A scanned page with no text layer is not searched. OCR for those pages is planned.

Everyone except a viewer. Viewers can search and open documents they are allowed to see. An answer cites the document and the page.

The document and the page the passage came from. The citation sits with the answer. Viewers can search and open documents. Asking is for every other role.

No. Search and ask use the text extracted from the file. A scanned page, or a PDF made only of images, has no text layer and is not read. OCR for those pages is planned.

No. Summaries, tags, and suggested document types are planned.

With email and password, or with Alkademy when single sign-on is turned on for the deployment. An invitation in the link is accepted as part of sign-in.

Organisation administrator, document manager, contributor, and viewer. In the product those are tenant admin, archivist, member, and viewer. A platform administrator manages the installation and is separate from a role inside an organisation.

Yes. They can switch. Each organisation has its own people, documents, and settings.

Access follows the role on the organisation. Restricting a single document or folder is planned. A link for someone outside the organisation, with an expiry, is planned.

On the server’s filesystem, or in an S3 bucket when the deployment is configured that way. Google Drive is planned. The catalogue, permissions, and audit trail stay in Dox either way. Local storage does not mean the archive works offline.

Yes. Local storage keeps the files on a designated filesystem on the server. That does not mean the archive works offline. The deployment can use an S3 bucket instead, including a private MinIO bucket. The catalogue, permissions, and audit trail stay in Dox either way.

Free allows 1 library, 100 documents, 1 GB, and 50 questions a month. Pro allows 20 libraries, 5,000 documents, 50 GB, and 2,000 questions a month. Uploads and questions stop at those numbers. Raising them is a plan change in Settings.

No. Review, retention rules, legal hold, and policy-controlled disposal are planned, on both plans. Deleting a document is available to people who can write. Reports beyond the usage figures in Settings are planned.

Create an account, then name the organisation. That stands on its own. A conversation, if you want one first, is a separate form.

It is stored for the people who operate this installation. If mail is configured, a copy is emailed and the form says so. The message is not filed into an archive.