Payment service provider user roles and access
This article describes how to configure user access for payment service provider (PSP) roles in Microsoft Dynamics 365 Fraud Protection.
Payment service providers (PSPs) can grant users of Microsoft Dynamics 365 Fraud Protection various levels of access, based on logical or functional roles. PSPs can include any organization that provides payment services to other organizations (also referred to as "payment gateways," "payment processors," etc.). This article applies to both PSPs and merchants that were onboarded to Fraud Protection by their PSP.
Important
Information in this article is subject to change at any time.
Assign PSP roles
Users are managed through your assigned Microsoft Entra tenant.
Roles can be assigned to either of the following types of users:
- Users inside the organization's Azure tenant
- Users outside the organization's Azure tenant, who will be invited to join the tenant as guest users
Important
Users inside the organization's Azure tenant who are member users can view a list of all other users in the tenant. By contrast, users outside the tenant who join as guest users can view only users who are in the same Fraud Protection environment that they have access to. Assign member or guest roles to users according to your business privacy requirements.
For more information about how to directly add users to your Microsoft Entra tenant as members or nonguest users, see Create a user account in Microsoft Entra ID.
Assign PSP roles to users in Fraud Protection
To assign PSP roles to users in Fraud Protection, follow these steps.
- Open the Fraud Protection portal page.
- In the left navigation pane, select Settings, and then select User access.
- Select Assign role(s).
- Enter the name or email address of the person or group that you want to assign a Fraud Protection PSP role to.
Note
In the Azure tenant, suggestions for users will appear while you type. Select a suggestion if it matches the user that you want to assign a user role to. Otherwise, a message informs you that an invitation email is sent to the person or group that you entered, so that the person or group can join the Fraud Protection environment.
- In the Roles field, select one or more defined roles that you want to assign to the user.
- Select Assign role(s).
Note
Users outside the Azure tenant will join the tenant as guest users and will appear in the User access grid after they accept the invitation that is emailed to them and complete the sign-in/sign-up process.
Edit assigned roles
To edit the role that is assigned to a user in Fraud Protection, select the user in the Member list, and then select Edit.
In this part of the page, roles can be added to or deleted from a user. If you edit your own account (for example, if you delete your own administrative role), your edits might interfere with your ability to use some features of Fraud Protection. If you must restore permissions, you can reset them in the Azure portal.
To learn more about the available PSP roles, see the PSP user roles and access section of this article.
Revoke user access to the environment
To revoke a user's access to the current environment, select the user in the member list, and then select Revoke access.
Important
When you revoke access for a user, the user is removed from the current environment. However, they might still have access to other environments in the hierarchy. To fully remove a user's access to Fraud Protection, delete the user from your Microsoft Entra tenant. In this way, you completely remove the user's access to your tenant and its associated applications or services.
PSP user roles and access
Fraud Protection offers a defined set of user roles, each of which has access to specific features and functions. You can select the appropriate role when you assign a user to the system. The following roles are available:
- PSP Admin – This role is a high-level administrative account that has full access to all PSP-related features. A user in this role can manage Fraud Protection for a PSP and its merchant customers.
- Fraud Manager – This role is an internal role in a PSP. A user in this role is intended to manage Fraud Protection for the PSP's merchant customers.
- Fraud Supervisor – This role provides the highest level of authority in a PSP's merchant customer. A user in this role can access merchant-facing functions that the PSP delegates to them.
- Fraud Analyst – This role is intended for a PSP's merchant customer who runs analysis and reports. A user in this role has read-only access to the merchant customer's data.
- Manual Review Agent – A user in this role is responsible for reviewing individual transactions and approving or declining them. Although manual review agents don't have direct access to the Support Lists page, they can modify the status of an entry in the support list through the Transaction Search page.
- Technical Developer – A user in this role is responsible for managing the technical configurations and integrations of a Fraud Protection instance for a PSP.
- Customer Service Support – A user in this role can view the transaction details and is provided with information that is required to handle customer queries.
- Reporting – A user in this role can view the reports such as Virtual Fraud Analyst and also access activity logs.
Note
If you are shown a different selection of roles than those detailed below, you may be using the standard version of Fraud Protection. Go to Configure user roles and access instead.
Permissions
Members can access Fraud Protection by visiting https://dfp.microsoft.com/ and using a Microsoft Entra account to sign in. Tables below describe permissions that different roles have on various functionalities within Fraud Protection.
Virtual Fraud Analyst - Summary, Rule analyst, Threat analyst & Monitoring
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Fraud Analyst, Reporting |
| No access | Manual Review Agent, Technical Developer, Customer Service Support |
Virtual Fraud Analyst -Score analyst
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Fraud Manager, Reporting |
| No access | Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support |
Search, View Transaction Details & Export
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Customer Service Support |
| No access | Technical Developer, Reporting |
Notes
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Manual Review Agent, Customer Service Support |
| Read only | Fraud Analyst |
| No access | Technical Developer, Reporting |
Decision Rules, Branches, Functions & Velocities
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager |
| Read only | Fraud Supervisor, Fraud Analyst |
| No access | Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Custom Lists & Support Lists
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| Read only | Fraud Analyst |
| No access | Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Note
Users with the Manual Review Age** role can add or remove items to the Support list on the Transaction details page. However, they can't access the full Support lists page.
External Calls & Event Tracing
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Routing rules
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| Read only | Fraud Analyst |
| No access | Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Queues
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| Read only | Fraud Analyst, Manual Review Agent |
| No access | Technical Developer, Customer Service Support, Reporting |
Note
Users with the Manual Review Agent role can make decisions (for example, Approve, Reject, or Send back to queue) on cases in queues. However, they can't modify queue settings.
Assign users to queues
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| No access | Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Case Review
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Manual Review Agent |
| Read only | Fraud Analyst |
| No access | Technical Developer, Customer Service Support, Reporting |
Case Review Reports
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| No access | Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Data Upload
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager |
| No access | Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
API Management
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Technical Developer |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Customer Service Support, Reporting |
Templates
| Template Type | Permission | Roles |
|---|---|---|
| Rules | Read/Write/Export | Product Admin, PSP Admin, Fraud Manager |
| Rules | No access | Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
| Environment | Read/Write/Export | Product Admin, PSP Admin |
| Environment | No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Note
- To create a template from a resource, the user must have read permission on the resource as well as write permission on the template.
- To create a resource using a template, the user must have write permission on the resource as well as read permission on the template.
Integration - Dashboard
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Technical Developer |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Customer Service Support, Reporting |
Integration - Entra Applications and SSL Certificate
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Technical Developer |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Customer Service Support, Reporting |
Note
To create a Microsoft Entra application, the user must also be assigned the Application Administrator, Cloud Application Administrator, or Global Administrator role in your Microsoft Entra tenant.
Settings - Usage
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Settings - Activity Logs
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Reporting |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support |
Settings - Access Management (Users & Entra Groups)
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor |
| No access | Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Note
- PSP Admin can assign all roles except Product Admin.
- Fraud Manager can assign all roles except Product Admin, PSP Admin, and Reporting.
- Fraud Supervisor can assign all roles except Product Admin, PSP Admin, Reporting, and Fraud Manager.
Settings - Subject Requests
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Settings - Transaction acceptance booster
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Notifications
| Notification Type | Roles that have permissions to view and dismiss |
|---|---|
| Environment Management, Event tracing, Subscription Expiry, Subject requests, SSL certificate & External call | Product Admin, PSP Admin |
| Actions | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Fraud Analyst |
| Search & Notes | Product Admin, PSP Admin, Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Customer Service Support |
Manage Environments - Create and Delete Environments
| Permission | Roles |
|---|---|
| Read/Write | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Note
PSP Admin can't create root (top-level) environments. They can only create children environments.
Manage Environments - Update Environments
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin, Fraud Manager |
| No access | Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Note
Update includes updating name and tags, and assigning APIs.
Admin Settings - Subscription
| Permission | Roles |
|---|---|
| Read only | Product Admin |
| No access | PSP Admin, Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Admin Settings - Configuration
| Permission | Roles |
|---|---|
| Read only | Product Admin, PSP Admin |
| No access | Fraud Manager, Fraud Supervisor, Fraud Analyst, Manual Review Agent, Technical Developer, Customer Service Support, Reporting |
Guest user access
Guest users can access Fraud Protection after they accept an email invitation and sign up (or sign in). To accept an invitation to Fraud Protection, follow these steps.
- Check your email inbox for an email that has the subject line "<Name> invited you to access applications within their organization."
- Select Accept invitation.
- If an existing Microsoft account or related account uses your email address, you're prompted to use that account to sign in. Otherwise, follow the setup process to sign up for a new account. After you're fully signed in, you should have access to Fraud Protection.
- Return to the invitation email, and write down or bookmark the exact link that appears after the text "If you accept this invitation, you will be sent to...." This link is in the format
https://dfp.microsoft.com/.../.... Each time that you access Fraud Protection, you must use this exact link. - For future access, go to https://dfp.microsoft.com/ and sign in with the guest user account.
Switch between tenants
You can use the tenant picker to select which tenant you want to be in, provided you have multiple tenants with Fraud Protection provisioned.
The tenant picker can be found by selecting the profile symbol on the top right of the dashboard, and then selecting Switch tenant. The tenant picker gives you a set of options to pick from. The options are only tenants that you, as a guest or administrator, have access to. To change to a different tenant, select the tenant name you want to be in to be redirected.
If you receive an error that says global administrator privileges are required, select Switch tenant at the bottom of the screen. The tenant picker opens and you can select the proper tenant.
Additional resources
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for