Lurana DMS¶
Lurana DMS is the document management product. It manages documents, repositories, folders, metadata, search, and document flows with Lurana BPM.
This guide is verified against DMS 1.0.84 and the live menu.
What you can do¶
| Area | What it covers |
|---|---|
| Dashboard | Document counts, storage, drafts, and recent activity |
| Folder Explorer | Browse repositories and folders |
| Documents | Search, review, update, version, and export documents |
| Queries | Run pre-built queries assigned to your areas |
| Document lists | Open the lists configured for your workspace |
| Upload document | Add a document through the guided wizard |
| Bulk upload | Upload many files or folders |
| BPM integration | Upload to BPM, BPM statistics, and case regularization |
| Audit | Review DMS activity and export evidence |
| Administration | Manage taxonomy, users, access, configuration, and queues |
| Deleted | Restore or permanently remove deleted documents |
| API | Integrate with DMS using the JSON API |
| Security | Permissions, visibility, encryption, and audit |
The top bar also gives you global search, notifications, messages, and your profile.
How DMS fits with BPM¶
- DMS organizes documents in its own repositories and folders.
- BPM cases can upload documents to DMS and read DMS views through an embedded session.
- DMS currently keeps a temporal audit log and publishes events to the shared audit service. The DMS audit log is transitional and may be replaced; do not treat it as a permanent compliance archive. The publishing flow is outside this first pass. See Audit.
Roles and permissions¶
DMS uses ACL entries in the form resource:action, such as documento:ver or
auditoria:exportar. A user can receive permissions directly or through
security groups. Deny rules override allow rules, and *:* is the superadmin
grant.
The Roles y permisos admin page is an ACL matrix over users and groups, not a role-inheritance model. See Administration.
Scope¶
This guide covers the pages users reach from the DMS menu. It does not document:
- unfinished or unreferenced code paths;
- API-only features without a web UI;
- internal diagnostic routes;
- backend services and infrastructure.
Start here¶
- Getting started — sign in and find your way around.
- Documents — the core document workflow.
- Upload document — add your first document.
- Folder Explorer — browse the document tree.