File chaos
Multiple copies of the same document, names like “contract_final_v3_corrected”. In Alfresco there is one document with a version history.
01 / Alfresco · ECM
Alfresco keeps contracts, invoices, technical documentation and correspondence in one place, with versions, permissions, search and approval workflows. We implement it from scratch, tailor it to your company and keep it running.

Multiple copies of the same document, names like “contract_final_v3_corrected”. In Alfresco there is one document with a version history.
Approval flows (e.g. cost invoices or contracts) run in a workflow with deadlines, reminders and a record of every decision.
Permissions at the level of folders, groups and individual documents. You know who can see what.
Search by content and metadata (counterparty, number, deadline), not just by file name.
Migration of existing documents from drives and other systems, preserving structure and metadata.
Integration with ERP, CRM, email and e-signature, so documents are created where you work.
Installation, configuration, security, backups and monitoring. On your server or in the infrastructure of your choice.
Document types, metadata, dictionaries and repository structure designed around how your company works.
Groups, roles, team workspaces and access rules. Consistent with how responsibilities are divided in your company.
Approval processes modelled in BPMN: who, in what order, by when, and what happens on rejection.
Connections to ERP, CRM, email, e-signature and other systems via API.
Moving existing documents from drives or other systems, with a completeness check after the move.
Custom actions, rules, views and extensions when standard functionality is not enough.
Updates, performance, backups, monitoring and support for users and administrators.
A review of configuration, performance and security, followed by a list of specific fixes.
We work at the level of the repository, the interface and integrations. Below are the specific Alfresco elements we configure and develop.
Content Model
Types, aspects, properties, constraints and associations defined in XML. A document model tailored to your company.
Aspects and metadata
Additional sets of properties attached to documents (e.g. contract data, counterparty, deadline), with value lists.
Folder Rules and Actions
Rules on folders: moving, assigning metadata, transformations, custom repository actions.
Smart Folders
Virtual folders built from metadata queries, without copying documents.
Content Store
Content storage configuration (file system, object storage solutions), backups and recovery.
Web Scripts
Custom REST endpoints in JavaScript or Java with FreeMarker templates. An API tailored to your applications.
Behaviours and Policies
Reacting to repository events (e.g. onCreateNode, beforeDeleteNode, onUpdateProperties) in Java code.
Repository Actions
Custom actions triggered manually, by rules or on a schedule.
Scheduled jobs (Quartz)
Recurring tasks: clean-ups, synchronizations, reports.
Transformations and renditions
Document conversions and previews (LibreOffice, ImageMagick, PDF), the Transform Service.
Audit
Enabling and configuring audit: who did what with a document and when.
ACL and permissions
Permissions on folders and documents, inheritance, roles (Consumer, Contributor, Collaborator, Coordinator) and custom permission groups.
Sites and groups
Team workspaces, groups and roles within sites.
LDAP / Active Directory
Synchronizing users and groups with the company directory.
SSO (SAML / OIDC / Kerberos)
Single sign-on, e.g. via Keycloak.
Dashlets and dashboards
Custom widgets on the home page and in sites: task lists, statuses, reports.
Alfresco Share: customization
Tailoring the Share interface (Surf): forms, evaluators, document list views, custom pages.
Document Library: actions and indicators
Additional buttons, actions and markers on documents.
ADF / ACA (Angular)
A custom interface built with the Alfresco Application Development Framework, or extensions to Alfresco Content App.
Activiti / Flowable (BPMN 2.0)
Approval processes defined in BPMN with task forms, deadlines, escalations and delegates in Java.
Task forms and listeners
Task forms and code executed on process events.
REST API v1 and CMIS
Access to the repository from other systems (CMIS AtomPub and Browser Binding).
FTP, WebDAV, CIFS/SMB
Exposing the repository as a network drive or over FTP.
Inbound email (IMAP/SMTP)
Documents from email go straight into the designated folders.
Solr / Elasticsearch
Full-text search: indexing, tuning, metadata queries.
AMP / JAR modules (Maven SDK)
Packaging extensions, deploying to Tomcat and in Docker/Compose.
ACS version upgrades
Migration between versions, compatibility of custom modules, JVM and database tuning.
If you are trying to set this up yourself and got stuck on one of the points above, tell us where you are. We will point you in the right direction, or do it for you.
We learn about your documents and processes: which matter most, who uses them, where you lose time today.
We describe the document model, permissions, approval flow and integrations. We agree on scope and schedule.
We launch the solution for one department or process to test it in practice before rolling it out company-wide.
We move the documents, train the team to work in the system and hand over the documentation.
We look after the system after go-live and extend it as your company’s needs grow.
Yes. Alfresco runs on your server or on one you choose, so documents do not go to an external cloud provider.
It depends on your requirements (vendor support, scale, features). At the start we discuss what you actually need, and only then recommend a version.
It depends on the scope: the number of processes, integrations and the size of the archive. After the analysis we give you a concrete schedule, not a vague “a few months”.
Yes. We start with an audit of configuration, performance and security, then take over maintenance or development.
In most cases yes, via API. It requires checking which interfaces your system provides.