Skip to content

Commit adfaeea

Browse files
authored
Update impersonate-another-user.md
Adjusting to improve Acrolinx score
1 parent 9d70650 commit adfaeea

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

powerapps-docs/developer/data-platform/impersonate-another-user.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ contributors:
1717

1818
Use impersonation to execute business logic on behalf of another Microsoft Dataverse user to provide a desired feature or service using the appropriate role and object-based security of that impersonated user.
1919

20-
This is necessary because the Dataverse web services can be called by various clients and services on behalf of a Dataverse user.
20+
Impersonation can be used by various clients and services to call the Dataverse web services on behalf of a Dataverse user.
2121

2222
Impersonation involves two different user accounts:
2323

@@ -38,17 +38,17 @@ In other words, the *impersonator* is allowed to do something *if and only if* t
3838

3939
### Direct assignment required
4040

41-
The **Act on Behalf of Another User** privilege (`prvActOnBehalfOfAnotherUser`), or a role containing that privilege, must be assigned directly to users since it cannot be inherited through a Team. This direct assignment is needed because of the sensitive nature of the privilege.
41+
The **Act on Behalf of Another User** privilege (`prvActOnBehalfOfAnotherUser`), or a role containing that privilege, must be assigned directly to users since it can't be inherited through a Team. This direct assignment is needed because of the sensitive nature of the privilege.
4242

4343
## Impersonation with Server-to-Server authentication
4444

45-
If you are creating a web client application that requires a user account that can act on behalf of a subscribing user, you can use the special *application user* account so that you do not need to use a paid Dataverse user license.
45+
If you're creating a web client application that requires a user account that can act on behalf of a subscribing user, you can use the special *application user* account so that you don't need to use a paid Dataverse user license.
4646

4747
More information: [Build web applications using Server-to-Server (S2S) authentication](build-web-applications-server-server-s2s-authentication.md).
4848

4949
## Impersonate another user using the Web API
5050

51-
To impersonate a user, add a request header named `CallerObjectId` with a GUID value equal to the impersonated user's Microsoft Entra ID object id before sending the request to the web service. The user's Microsoft Entra ID object id is included in the [SystemUser.AzureActiveDirectoryObjectId](reference/entities/systemuser.md#BKMK_AzureActiveDirectoryObjectId).
51+
To impersonate a user, add a request header named `CallerObjectId` with a GUID value equal to the impersonated user's Microsoft Entra ID object identifier before sending the request to the web service. The user's Microsoft Entra ID object identifier is included in the [SystemUser.AzureActiveDirectoryObjectId](reference/entities/systemuser.md#BKMK_AzureActiveDirectoryObjectId).
5252

5353
More information: [Impersonate another user using the Web API](webapi/impersonate-another-user-web-api.md).
5454

@@ -63,7 +63,7 @@ To impersonate another user, set the `CallerId` property to the Guid value of th
6363

6464
## Impersonate another user using plug-ins
6565

66-
You can register a plug-in you can specify a user that the operations should use. Within the code of a plug-in you can override this setting.
66+
You can register a plug-in containing code to specify the user that the operations should use.
6767
More information: [Impersonate a user](impersonate-a-user.md).
6868

6969

0 commit comments

Comments
 (0)