Stories of digital innovation by no-code
Discover the opportunities of the channel program
Join the Network
Leverage the resources of Jamio
We collaborate with universities
News from the world of Jamio Openwork
Stay up to date on the world of no-code and digitalization
The periodical on no-code and BPM
Events dedicated to Jamio producers, partners, and customers
Free downloadable guides
Independent Software Vendor
Join our team
Our locations
Forever part of who we are
Jamio platform is equipped with a Document Management with which it implements all the functions of a Document Management System (DMS), allowing you to model objects such as Documents , Files , Volumes .
Document Automation features , Jamio allows you to build any type of business case related to document management issues, thus enabling the total digitalization of document flows .
With Jamio it is therefore possible to manage the life cycle , versioning and revision , classification and indexing , filing , registration , access and permissions and sharing of a document, simple and complex Human Task Management and Process Management components , it is possible to:
Any process that involves the creation , editing , archiving , sharing , and distribution of documents can benefit from effective and automated document management, reducing errors , time , and costs Jamio's no-code approach
Purchasing or supply processes - These involve managing the life cycle of an order : templates, subscriptions, requests for quotes, contracts, supplier evaluation, etc.;
Personnel management processes - These involve the management of an employment contract : negotiation, signing, distribution of pay slips, requests for holidays and permits, creation and distribution of workplace safety and training documents, etc.;
Quality management processes - These include managing the lifecycle of quality- related documents , such as quality manuals, standard operating procedures, audit reports, non-conformity reports, corrective and preventive actions, etc.;
Project management processes - They deal with the lifecycle management of documents relating to the planning , execution and monitoring of the projects , with delivery documentation, risk reports, deadline and status control;
Technical support processes - Documents relating to the technical support provided to the company's customers are managed, such as intervention reports, intervention sheets, customer evaluation sheets and documents relating to warranties and maintenance contracts;
and many others.....
A Document in Jamio is not a simple file, but a more complete structure , customizable with specific metadata, which can contain not only files but also relationships with other documents or forms on the platform ( for example, a contract with a price list, or the Privacy Policy ) or external resources ( e.g., a link to a website ). It is also possible to create links between different documents or versions of documents, ensuring access to the most up-to-date version or the one chosen when developing the document.
A typical example of a Document is a contractual model made up of multiple attachments, each attachment has its own life cycle , everything is assembled into a single Document subjected to overall versioning .
During its life cycle, a Jamio document can be: Created , Read , Edited , Published , Deleted ; additional elements are managed in addition to the basic CRUD (create, read, update, and delete) mode.
Jamio allows you to aggregate documents into Files , which shouldn't be thought of as simple collection folders, but as business entities with a lifecycle and metadata . Files can contain documents related to the same transaction or subject area and can be organized in a navigable hierarchical structure. Files can also contain other Files, allowing for further organization. With Jamio, you can create, close, reopen, move, and delete Files and their related documents efficiently and easily.
In Jamio, you can define permissions for accessing documents and lists design time authorization schemes . Authorization schemes define access control lists (ACLs) on various entities that specify which users can use them and what operations they can perform on them authorization scenarios and distribution lists , can be associated with these
ACLs can be assigned to different elements of the organization . You can therefore define at design time which office, role, or group is authorized to manage the CRUD functionality of a modeled document, but you can also define such permissions on the individual document at run time — for example, this document is viewed by the manager of the person who created it .