Home › CaRD Workspace for CMIS
Archived documents only help those who can reach them. The CaRD Workspace opens your archive to everyone who needs it — warehouse, service, quality assurance, subsidiaries, auditors — in the browser, with cleanly separated permissions and without a single additional SAP S/4HANA® account.
A neatly archived document that is only reachable through SAP has a very small audience. Everyone else asks somebody who has SAP. And that somebody is rarely the cheapest person in the building.
Setting up SAP access so somebody can look at a delivery note is out of all proportion — yet it is regularly considered for exactly that reason.
“Could you send me that document?” costs two people time, creates a copy in a mailbox, and is needed again the next day.
Auditors, customs or a customer on the phone do not wait. Whoever can search for themselves answers in seconds instead of the next working day.
Users sign in with their familiar company account. Which permissions they receive is controlled centrally through roles — they set nothing up and install nothing.
Where several archives are connected, users switch between them at the top. SharePoint, Azure Blob, Amazon S3 or a file system all look the same in the window — the difference stays in the basement.
Via the folder structure or via search: search fields are defined by you, several criteria can be combined and narrowed to a folder branch. Documents are found through the metadata given when they were filed.
Download a document, look at its properties — or upload new files with the right metadata. What a user may do is decided by their permissions; whatever is protected stays protected.
Anyone who only needs to read no longer needs SAP access. That relieves the colleagues who have it, and makes departments able to answer questions that previously could not.
SharePoint, Azure Blob Storage, Amazon S3, STACKIT or a file system — users switch between the connected archives at the top. To them, all of them look the same.
Which fields are searchable is up to you — document number, supplier, date, whatever matters at your site. Several criteria can be combined and narrowed to a folder branch.
Read, create, update and delete are separate and can be combined freely. That is exactly what an archive needs: adding yes, altering what is there no.
When uploading, the dialog asks for the fields of the selected document type — so no documents are created that nobody can find later.
German, English, French, Spanish, Italian and Dutch. The interface follows the browser language — for international sites there is nothing to set up.
Opening an archive to more people is only a good idea if nothing can be lost in the process. That is why protection in the Workspace does not sit beside the permissions but above them.
That is the difference between a file share and an archive. On a file share anyone with write access can remove anything; here the document’s protection status decides first, and only then the user’s permission.
For retention obligations that means the rule lives on the document, not in a written procedure.
The Workspace is a standalone application next to the CaRD Connector. It changes nothing in the archive, nothing in the connector, and needs no access to your SAP system.
From every deployment model — SAP S/4HANA Public Cloud and private cloud, RISE with SAP, S/4HANA on-premise and SAP ECC. The Workspace never talks to SAP itself: it reads the archive through CMIS. What sits there was filed by the CaRD Connector or another archive system, so your SAP deployment model is irrelevant to the access.
A web interface for your document archive. Users search, open and file documents in the browser — without SAP access and without installed software. Underneath, the CaRD Connector addresses the archive through the open CMIS standard.
No. That is precisely the point: anyone who merely has to look at an archived document — warehouse, service, quality assurance, subsidiaries, auditors — no longer needs SAP access, and no longer has to ask anyone for it.
All those the CaRD Connector connects: SharePoint, Azure Blob Storage, Amazon S3, STACKIT and the local file system. Where several are connected, users switch between them in the same window.
Through four separate permissions — read, create, update, delete — which can be combined freely. Splitting create from update is deliberate: in an archive you should be able to add without being able to alter what is there. They are assigned centrally through roles in Microsoft Entra ID.
No. Protection sits above the permissions: a document with a hold or a running retention period cannot be deleted or changed even if the user would have the right to do so. Documents managed by SAP are protected in the same way.
No. The Workspace speaks nothing but the open CMIS standard — the same interface SAP uses. Nothing is adapted in the connector, nothing rebuilt in the archive, and your existing filing keeps working unchanged.
German, English, French, Spanish, Italian and Dutch. The language follows the browser setting automatically — users do not have to switch anything.
Wherever you want: in your own data centre on Windows/IIS, in Azure as a web app, or on a Cloud Foundry platform. It is a standalone application next to the connector and needs no access to your SAP system.
We quote per customer — by number of users, connected archives and operating model. Request an individual quote; we are happy to show you a no-obligation live demo first.
Tell us where your documents live today and who should be able to reach them - we will sort out the rest in a conversation.