Protocols provide developers with another possible avenue for building their own applications and extensions. For example, if you are building a client application to connect with multiple repositories from multiple vendors, including Alfresco, then CMIS is a consideration. If you are building a client to connect via the SharePoint Protocol, then use the Alfresco Office Services (AOS). Protocols provide a resource for developers, in addition to the numerous other extension points and APIs built into Alfresco.
When any of these protocols are used to access or upload content to the Alfresco repository, access control is always enforced based on configured permissions, regardless of what protocol that is used.
The following table list some of the main protocols supported by Alfresco and links to more detailed documentation.
|HTTP||The main protocol used to access Alfresco content repository via for example the Alfresco REST APIs.||Standard in Alfresco One and Community Edition.|
|WebDAV||Web-based Distributed Authoring and Versioning is a set of HTTP extensions that lets you manage files collaboratively on web servers.||Standard in Alfresco One and Community Edition.|
|FTP||File Transfer Protocol - standard network protocol for file upload, download and manipulation. Useful for bulk uploads and downloads.||Standard in Enterprise and Community.|
|CIFS||Common Internet File System - allows the projection of Alfresco as a native shared drive. Any client that can read or write to file drives can read and write to Alfresco, allowing the commonly used shared file drive to be replaced with an ECM system, without users knowing.||Standard in Alfresco One and Community Edition.|
|SPP||Enables Alfresco to act as a Microsoft SharePoint Server. Allows Microsoft Office users to access documents within the Alfresco repository.||Supported as part of Alfresco Office Services (AOS). Enterprise only. Community versions have support for the older SharePoint Protocol Support.|
|Alfresco Office Services||Alfresco Office Services (AOS) allow you to access Alfresco directly from all your Microsoft Office applications.||Standard in Alfresco One and Community Edition.|
|CMIS||Alfresco fully implements both the CMIS 1.0 and 1.1 standards to allow your application to manage content and metadata in an on-premise Alfresco repository or Alfresco in the cloud.||Standard in Alfresco One and Community Edition.|
|IMAP||Internet Message Access Protocol - allows access to email on a remote server. Alfresco can present itself as an email server, allowing clients such as Microsoft Outlook, Thunderbird, Apple Mail and other email clients to access the content repository, and manipulate folders and files contained there.||Standard in Alfresco One and Community Edition.|
|SMTP||It is possible to email content into the repository (InboundSMTP). A folder can be dedicated as an email target.||Standard in Alfresco One and Community Edition.|