Name: Managing Admins and Users in SAP Customer Data Cloud
Uploaded: 2019-9-12
Duration: 198 s
Description: In this video, we'll discuss the difference between an Admin user and a Console user, and then we'll go through a quick tutorial to show how you can invite, edit, and delete admins or users in the Console. Check the documentation link for more details.https://developers.gigya.com/display/GD/Console+Administration

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div>In this video, we'll discuss the difference between an Admin user and a Console user, and then we'll go through a quick tutorial to show how you can invite, edit, and delete admins or users in the Console. <br><br>Check the documentation link for more details.<br><a href="https://developers.gigya.com/display/GD/Console+Administration" rel="nofollow noopener noreferrer" target="_blank">https://developers.gigya.com/display/GD/Console+Administration</a><br></div></div></div></div></div></div>

Managing Admins and Users in SAP Customer Data Cloud

In this video, we are going to see how to manage SAP Customer Data Cloud Console administrators and users. CDC provides a general framework for setting and enforcing user and application level permissions. The permission system enables you to create users, grant them permissions, and evaluate their permissions upon incoming requests. The permissions determine which API methods the user can call, what parameters the user can pass, what the valid values for those parameters are, and what types of logical operations are allowed. In addition, permissions are scoped to certain partners or sites. First, we'll differentiate between a console admin and a user, and then we will see how to set this up in the CDC console. So what's the difference between an administrator and a user in your CDC console? An admin will have full access to make any changes they see fit. That means they can change site settings, pull user data, observe user records, look at reports, and add other admins or users to the console. Here's a tip you will want to invite more than one administrator in your console, and I suggest you do that as soon as you're done watching this video. The reason being is if someone were to leave the organization for some reason, you want to make sure that another person there has access in order to manage the account. A user, on the other hand, will belong to a group which has certain access privileges based on their need and their role. For example, if a developer needed access to update site settings for your deployment or to make changes to your registration screen sets or login screen sets, then you might want to limit their access and perhaps not allow them to look at user data. You can accomplish this by setting up groups in the console, which you will see next in the demo. We are at your homepage. Let's click on admin to get to the administrators page. This page allows the site administrator to invite additional admins and edit existing ones. You'll see the details tab here. You'll see the name and the email for the user. You'll also see the groups that they belong to. You can remove them from groups and you can also assign them to more groups. It's a simple dropdown, and it's very easy to add these users to different groups. You can also see the privileges they have for your CDC console. You can see here the site name and the privileges given to the users for that site. Let's go back from here. Inviting an administrator or user is very simple. Click on Invite administrator. Enter in the email address. Select the group you want the user to belong to and then click Invite Administrator. The user should get an email to accept the invite. Note that the email invitation expires 72 hours after it is sent. This ends the demo.