You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/cards/manage-cards/manage-cards.md
+8-6Lines changed: 8 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -16,27 +16,29 @@ ms.collection:
16
16
17
17
This article will help you use security roles to manage cards and explains how to delete a record.
18
18
19
-
## Administrate cards
19
+
## Manage cards with security roles
20
20
21
21
This section shows you how to manage cards using security roles.
22
22
23
23
### Change who can create cards
24
24
25
25
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).
26
26
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.
28
28
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.
30
30
31
31
### Disable cards for an environment
32
32
33
33
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.
34
34
35
35
### Cards security roles
36
36
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.
38
38
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.
40
42
41
43
## Delete a card
42
44
@@ -53,4 +55,4 @@ This section shows you how to delete a card.
53
55
54
56
### Delete a card as the administrator
55
57
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