Skip to content

Commit 11f99a2

Browse files
authored
Update manage-cards.md
1 parent 9b34632 commit 11f99a2

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

powerapps-docs/cards/manage-cards/manage-cards.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,27 +16,29 @@ ms.collection:
1616

1717
This article will help you use security roles to manage cards and explains how to delete a record.
1818

19-
## Administrate cards
19+
## Manage cards with security roles
2020

2121
This section shows you how to manage cards using security roles.
2222

2323
### Change who can create cards
2424

2525
Cards are stored as rows in Dataverse within the **Card** table. Administrators can use [security roles to control who can create, read, and update cards](/power-platform/admin/wp-security-cds#tablerecord-ownership).
2626

27-
For example, if the user is only assigned a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards in the Maker Portal.
27+
For example, if the user is only assigned to a security role that does not have permission to create rows in the **Card** table, then the user will not be able to create cards.
2828

29-
Note that a user will still be able to receive and use cards sent in Teams regardless of the security role assigned to them as those cards are accessed by the Cards for Power Apps service.
29+
Note that a user will still be able to receive and use cards sent in Teams, regardless of the security role assigned to the user, as those cards are accessed by the Cards for Power Apps service.
3030

3131
### Disable cards for an environment
3232

3333
The Cards for Power Apps service uses the security role called **Cards Role** to communicate with Dataverse. By removing permissions for the **Cards Role** in an environment to create, read, or update the **Card** table, no one will be able to use cards within that environment.
3434

3535
### Cards security roles
3636

37-
**Cards Basic Role** can be used to grant a user access to view, create, and use cards in that environment. Other security roles can also be modified to impact view, create, and use scenarios by changing security role access to the **Card** table in Dataverse.
37+
- **Cards Basic Role** can be used to grant a user access to view, create, and use cards in that environment.
3838

39-
**Cards Role** is used internally by the Cards for Power Apps service to communicate with Dataverse.
39+
Other security roles can be modified to view, create, and use cards by changing security role access to the **Card** table in Dataverse.
40+
41+
- **Cards Role** is used internally by the Cards for Power Apps service to communicate with Dataverse.
4042

4143
## Delete a card
4244

@@ -53,4 +55,4 @@ This section shows you how to delete a card.
5355

5456
### Delete a card as the administrator
5557

56-
If the owner of an app is unavailable, it is currently not possible for an administrator such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.
58+
If the owner of an app is unavailable, it is currently not possible for an administrator, such as Global admin, Azure Active Directory Global admin, or Dynamics 365 admin to delete a card. We are working on enabling this capability.

0 commit comments

Comments
 (0)