Within SAP Customer Data Cloud, permission groups can be managed to control access and permissions. The following actions can be performed on a permission group:
* Clone group: This allows you to create a duplicate of an existing permission group, making it easier to set up new groups with similar permissions without starting from scratch.
* Delete group: This action removes an existing permission group from the system, thereby revoking all permissions associated with it.
These functionalities help in efficiently managing user permissions and access controls within the system.
References
* SAP Customer Data Cloud Documentation on Permission Groups

In SAP Customer Data Cloud dataflows, the components that can be added include:
* Datasource: This is where the data originates. It could be a database, an API, or other data storage systems.
* Datatarget: This is where the processed data will be stored or sent after the dataflow execution.
* File: This component is used to import or export data in various file formats, such as CSV or JSON.
These components are essential for designing and executing dataflows that move and transform data between different systems and formats.
References
* SAP Customer Data Cloud Dataflows Documentation

To add a new custom field to the accounts schema in SAP Customer Data Cloud, you can use either of the following methods:
* Schema Editor in the Admin Console: This is a user-friendly interface within the admin Console where you can visually add and configure custom fields directly in the accounts schema.
* Navigate to the schema editor.
* Add the new custom field with the desired attributes and settings.
* Save the changes to update the schema.
* REST API (accounts.setSchema): This method allows for programmatic updates to the accounts schema.
* Make an API call toaccounts.setSchemawith the necessary parameters to define the new custom field.
* Include the field's name, type, and any other required attributes in the request payload.
Both methods provide flexibility in how you manage and extend the user schema to include additional custom fields based on your specific requirements.
References
* SAP Customer Data Cloud Schema Editor Documentation
* SAP Customer Data Cloud REST API Documentation

To mark an account as successfully transferred in SAP Customer Data Cloud after updating an external database via a new webhooks endpoint, you need to use theaccounts.setAccountInfomethod.This method requires the UID (User ID) received in the webhook notification and a bearer token for authentication.
* Step 1: Receive the webhook notification, which includes the UID and other necessary information.
* Step 2: Update the external database with the user information as required.
* Step 3: Use theaccounts.setAccountInfoAPI endpoint to update the user's account status in SAP Customer Data Cloud.
* UID: Include the UID received in the webhook notification to specify which user's account needs to be updated.
* Bearer Token: Use a valid bearer token for authentication purposes.
* Step 4: Call theaccounts.setAccountInfoAPI with the necessary parameters to mark the account as successfully transferred.
This approach ensures that the user's account status is accurately updated in the SAP Customer Data Cloud after the external database operations are completed.
References
* SAP Customer Data Cloud API Documentation
* SAP Help Portal