⚠️ Pre-release. The SAP Sales Cloud V2 integration is still under development. This page describes what is being built so you can prepare your system and review the access uman needs. Details can still change before release.

🔌 Setup and details

uman connects to SAP Sales Cloud Version 2 through the public /sap/c4c/api/v1 API of your own environment. Every object sits behind its own service, so uman calls one collection per object. Nothing outside the collections listed below is touched. Every route on this page is relative to /sap/c4c/api/v1.

📇 Objects uman uses

In uman	In SAP Sales Cloud V2	Entity	Collection uman calls
Account	Account	`sap.crm.md.accountservice.entity.account`	`/account-service/accounts`
Contact	Contact Person	`sap.crm.md.contactpersonservice.entity.contactPerson`	`/contact-person-service/contactPersons`
Deal	Opportunity	`sap.crm.opportunityservice.entity.opportunity`	`/opportunity-service/opportunities`
Pipeline and stages	Sales Cycle and Sales Phases	`sap.crm.opportunityservice.entity.opportunitySalesCycle`	`/opportunity-service/salesCycles`
Note	Note	`sap.crm.noteservice.entity.note`	`/note-service/notes` and `/opportunity-service/opportunities/{id}/notes`
Field and code list definitions	Repository Service	Your own object model	`/repository-service/entities`, `/services`, `/apis`

1. Accounts

Entity: sap.crm.md.accountservice.entity.account
Route: /account-service/accounts

Access	What uman does
Read	Account name, created and changed information, every field marked as required, and any field you map in uman
Create	A new account, when you choose to create one from uman. Required fields are read from your object model and offered to fill in
Update	Never
Delete	Never

2. Contacts

Entity: sap.crm.md.contactpersonservice.entity.contactPerson
Route: /contact-person-service/contactPersons

Access	What uman does
Read	First name, last name, the account the contact belongs to, email address, phone number, job title, created and changed information
Create	A contact on an account, with the same set of details
Update	The same set of details on an existing contact
Delete	Never

3. Opportunities (Deals)

Entity: sap.crm.opportunityservice.entity.opportunity
Route: /opportunity-service/opportunities

Access	What uman does
Read	Name, the account it belongs to, sales cycle, sales phase, expected close date, status, created and changed information
Create	An opportunity on an account, with a sales cycle and a sales phase
Update	Move an existing opportunity to another sales phase
Delete	Never

How uman reads the status:

Status	uman treats it as
Open, In Process	Open
Stopped, Lost	Closed
Won	Closed and won

4. Sales Cycles and Sales Phases (Pipelines)

Entity: sap.crm.opportunityservice.entity.opportunitySalesCycle
Route: /opportunity-service/salesCycles

Access	What uman does
Read	Every active sales cycle, with the sales phases it contains, in their own order, including each phase's probability. This fills the pipeline and stage choices in uman
Create	Never
Update	Never
Delete	Never

5. Notes

Entity: sap.crm.noteservice.entity.note
Route: /note-service/notes for account and contact notes
Route: /opportunity-service/opportunities/{id}/notes for opportunity notes

Access	What uman does
Read	The notes on an account, contact or opportunity you have linked in uman
Create	A note on an account, contact or opportunity. Account and contact notes are stored under the note type configured for that object, opportunity notes on the opportunity itself
Update	Only the most recent note of its type, and only by the person who created it, unless the note type configuration allows otherwise
Delete	Same rule as an update. Removing a note leaves the older notes as they are

Good to know
Titles	A Sales Cloud V2 note holds content only, so uman sends the content and no title
Same note on a second record	A note belongs to exactly one record, so uman writes a copy on the second record

6. Field and code list definitions

Routes: /repository-service/entities, /repository-service/services, /repository-service/apis

Access	What uman does
Read	Which fields exist on each object, which of them are required, what they are called, and which values a code list field accepts. This is what makes the fields uman shows you match your own configuration instead of a fixed list
Create, Update, Delete	Never. This is configuration, and uman only reads it

New fields and code list values are picked up automatically, but can take a moment to appear in uman.

7. Custom objects and custom fields

Optional, depending on your Sales Cloud V2 setup.

Entity: any entity your object model exposes
Route: looked up in your own object model through the Repository Service, because a collection is not always named after the entity it serves

Access	What uman does
Read	Objects and extension fields that are needed to create an account, contact or opportunity
Create	Those same objects, when a record you are creating requires one
Update	Never
Delete	Never

Objects that exist only as rows inside another object, such as an address on an account, have no collection of their own in Sales Cloud V2. uman reads and writes them as part of their parent record, and cannot list them separately.

🔐 Permissions

uman acts as the person who connected, and works inside exactly the authorizations your setup grants that user. Anything they cannot see in Sales Cloud V2, uman cannot see either.

The connecting user needs:

Access	On
Read	Accounts, Contact Persons, Opportunities, Sales Cycles, Notes, and the Repository Service (field and code list definitions)
Create	Accounts, Contact Persons, Opportunities, Notes
Change	Contact Persons, Opportunities, Notes

uman never deletes an account, a contact or an opportunity.
uman never changes your sales cycles, sales phases or code lists.
uman writes only when you trigger it. Nothing is created or updated in the background.

🔗 How you connect

⚠️ Planned, not final. The authentication flow below is the design we are validating with SAP. It still has to be confirmed and can change.

Step 1 - Share your Sales Cloud V2 URL with uman

Provide the base URL of your Sales Cloud V2 environment to your uman account manager. Copy it from your browser while you are logged in to Sales Cloud V2. Example: https://my123456.eu10.crm.cloud.sap

Step 2 - Register uman on your identity provider

An application for uman is registered on your SAP Cloud Identity Services environment (IAS), and is allowed to issue an assertion for the individual user who is using uman.

Step 3 - Each team member connects

uman exchanges that user level assertion for an access token on your Sales Cloud V2 environment, and uses that token for every call it makes. Because the token belongs to the individual user, uman inherits exactly their authorizations, and records created or changed are attributed to that person, not to uman and not to an administrator.