Name: Identifying User Personas in CIAM for B2B in SAP Customer Data Cloud
Uploaded: 2024-5-29
Duration: 177 s
Description: This video explains the various user personas involved in CIAM for B2B implementation.

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><div>This video explains the various user personas involved in CIAM for B2B implementation.</div><div></div></div></div></div></div></div></div>

Identifying User Personas in CIAM for B2B in SAP Customer Data Cloud

In this video, we will talk about  the different user personas  that interact with the B2B solution.  These break down into three categories.  First, we have an IT admin.  These are members of SAP's  customer's organization  who are interacting with our solution  implemented into their applications.  These users will have a  Customer Data Cloud Console account.  They won't exist  in the standard accounts database.  Next, we have an organization member.  These are the members of the organizations  that work with our customers,  the third-party organizations  that we've spoken about.  These will exist as a contact  in the customer data cloud database,  not as a console user.  And finally, we have the delegated admin,  which is like a subcategory  of the Organization member.  The difference is  that they have permissions  to manage accounts in their organization.  They are also stored as a contact in the  account database in Customer Data Cloud. Next we'll take a look at some of the use cases  that an IT admin could cover.  There's lots of different categories here  that can form an IT admin,  but let's not forget that they will always have to  have a Customer Data Cloud Console account  in order to be able to perform these duties.  We have a policy creator -  someone who is actually implementing and  creating the policies that are going to define  access within the applications.  We've got an organization administrator -  someone who's going to manage  organizations which that company works with,  and possibly their members as well.  They could also be a security auditor -  somebody who wants to be able  to see what access has been granted  to whom and when. They might also be an approver -  someone who is approving organizations  as part of the approval flow  when someone requests to start  working with customers.  And finally, it could be someone who is  implementing the B2B solution  on an application.  Let’s take a look at  the organization member use cases.  These break down into two categories.  First, we have a standard user,  or an “end-user” -  someone who is fulfilling their business duties  by interacting with different applications  as a member of those external organizations.  Secondly and separate to that,  we have the delegated admin,  which is someone, or an “end-user”, who also  has the responsibility of managing members of  their organization as well. Thank you for watching.