Cloud ALM documents, stored in your SharePoint.
DocSync connects SAP Cloud ALM to a SharePoint library you already own. Keep the files, version history and everyday work in SharePoint, with the documents linked to Cloud ALM.
Start in either tool. Keep one file.
Upload to a project first. Associate the document with a requirement, process or other object afterwards.
First: a document in the project. Then: its association.
Create a document in your Cloud ALM project and upload its file.
DocSync saves the file in the project folder in SharePoint.
Then you associate the document with a requirement in Cloud ALM. DocSync moves the file to that requirement’s folder.
Drop the file into the project folder in SharePoint.
The file uploads into the project folder in SharePoint. That triggers the sync process.
DocSync detects the file and creates a document in that Cloud ALM project during background sync.
The original stays in SharePoint. The dashed document in Cloud ALM is a link to that file; you can associate it with a requirement afterwards.
Illustrative timing. Cloud ALM uploads are immediate. SharePoint imports and association updates run every 5 min by default.
See the real integration →What needs to be connected?
An Entra ID app with access to the selected SharePoint site (Sites.Selected), a destination in your Cloud ALM subaccount and the required API permissions. DocSync connects the two through CMIS and Microsoft Graph.
Explore the full SharePoint library example
What your team sees in SharePointExample data
| Filled in by DocSync from Cloud ALM | ||||||||
|---|---|---|---|---|---|---|---|---|
| Name | Modified | Modified By | Document | ID | Type | Status | Owner | Cloud ALM link |
| docxOrder to Cash design.docx | 2 hours ago | Ana Ortega | Order to Cash design | 7-13 | Functional Specification | In Review | ana@example.com | 7-13 · Order to Cash design |
| xlsxCredit limits mapping.xlsx | Yesterday | Jun Lee | Credit limits mapping | 7-21 | Default | In Progress | jun@example.com | 7-21 · Credit limits mapping |
| pdfOTC workshop sign-off.pdf | 3 days ago | Marta Silva | OTC workshop sign-off | 7-30 | Project Documentation | Released | marta@example.com | 7-30 · OTC workshop sign-off |
Your SharePoint library
One stored file
Your permissions and policies
Every Cloud ALM action has a SharePoint answer
Tested against a live Cloud ALM tenant, one case at a time.
| In Cloud ALM you… | In SharePoint | When |
|---|---|---|
| Upload a file to a document | The file is stored in <project>/<object> with its real name, columns and a link back to Cloud ALM | at once |
| Replace the file | A new SharePoint version of the same file; the history stays complete | at once |
| Assign it to a requirement, process or test | The file moves to that object's folder | every 5 min |
See metadata, deletions and file locks
| In Cloud ALM you… | In SharePoint | When |
|---|---|---|
| Change title, status or owner | The columns follow | every 5 min |
| Delete it | Moved to the project's Eliminados folder; restoring it moves it back | every 5 min |
| Delete it permanently | The file is removed | at once |
| Discard a draft with a file | The file is removed; nothing is left behind | at once |
| Try to change a file someone checked out in SharePoint | Refused, and the document is tagged as locked until check-in | at once |
Every file, its state, and what to do
One page for the people who run the integration: the state of every file, warnings that say how to fix them, the activity log and a one-click sync.
The console, with example dataExample data
| File | State | Cloud ALM document | CALM status | Owner | Version | Modified |
|---|---|---|---|---|---|---|
| Order to Cash design.docx/S4 Rollout/Procesos/14-2 - Order to Cash | Synced | 7-13 · Order to Cash designFunctional Specification | In Review | ana@example.com | 4.0182 KB | 16 Nov, 09:10Ana Ortega |
| Credit limits mapping.xlsx/S4 Rollout/Requerimientos/3-118 - Credit check | Lockedby Jun Lee | 7-21 · Credit limits mappingDefault | In Progress | jun@example.com | 2.064 KB | 16 Nov, 08:47Jun Lee |
| Cutover plan.docx/ | Not confirmednot confirmed by Cloud ALM yet (document still a draft?) | — | 1.096 KB | 16 Nov, 11:20Marta Silva | ||
| server-cert.cer/S4 Rollout/Backlog | Rejectedno permitido en Cloud ALM: server-cert.cer | — | 1.02 KB | 15 Nov, 17:05Jun Lee |
Built for the people who run it
- Your library, your rules. Files stay in your SharePoint, under your retention and permissions.
- No duplicate. One file, one place; Cloud ALM reads it from SharePoint.
- Folders that mirror Cloud ALM. By project, then process, requirement, task or test.
- Columns people can filter. Document ID, title, type, status, owner and a link back.
- Two-way. Drop a file into a project folder and it becomes a Cloud ALM document.
- Nothing deleted by guesswork. A file Cloud ALM stops reporting goes to quarantine, never to the bin.
- Admin console. Every file with its state, warnings with what to do, activity, one-click sync.
- Least privilege. One SharePoint site, and only the Cloud ALM API scopes it needs.
One price per tenant, no charge per user
Essential
One project team.
- 1 Cloud ALM tenant
- Up to 20 projects
- Support 8×5, 2-day response
- Updates and backups included
Professional
Several projects in parallel.
- Up to 100 projects
- Support 8×5, 8-hour response
- Onboarding session included
- Updates and backups included
Enterprise
Groups and regulated environments.
- Unlimited projects
- 24×7 support option
- Test environment
- Annual security review
Indicative prices, excluding VAT. Annual billing includes two months free. Confirm tenant coverage, setup costs and backup scope in the proposal. Support times refer to the initial response, not resolution. Migration is quoted separately.
Before you connect
The essentials for your project and IT teams.
Where are the files stored?
In your SharePoint library. Cloud ALM reads the attachment through DocSync; it does not require a separate file copy in an SAP BTP document service.
What needs to be configured?
An Entra ID application with access to the selected SharePoint site, a destination in the Cloud ALM subaccount and the required Cloud ALM API permissions. We can review the setup in the demo.
Is every change immediate?
File uploads and replacements are handled at once. Metadata, associations and other background updates are reconciled every five minutes by default. The action tables above explain each case.
Does DocSync sign documents?
No. Files remain available to the signature and approval tools you use in SharePoint. Those tools and your configuration determine the signature process.
What will we cover in the demo?
An upload from Cloud ALM, the file and its columns in SharePoint, version history and the admin console. We will also review your prerequisites and deployment questions.
Moving from Solution Manager?
DocSync Migration will rebuild your Solution Manager documentation in Cloud ALM, with the files in SharePoint. We are looking for pilot customers.
- Inventory. A report of what you have and what is worth moving.
- Structure. Projects and process hierarchy recreated node by node, original IDs kept as reference.
- Documents. Created in Cloud ALM with type and state, files placed in SharePoint.
See DocSync in action
Thirty minutes to see the upload, the SharePoint file and version history. Tell us about your project and we will arrange the demo.