Dashboard cards

Define permissions for the User Card object

The User Card object contains data about the cards on a user's dashboard. The Access Control List allows you to define permissions for the User Card object. Modifying permissions for an object allows you to grant access to actions that affect the object, which can be executed from API calls or portal pages. You can grant a role full access, custom access, or no access to the object. You can also customize the level of access users have to the actions and fields within the object. The TenantAdministrator role has full access to all objects.

To define permissions for the User Card object, complete the following steps in the portal.

Go to the ACL page.

Step Information

Note:The default location for the ACL page is Configuration > ACL. If the menu items for your tenant have been customized, it may be located elsewhere. For more information, contact your tenant administrator.
In the list, expand Object (System), and then select User Card Object.

Step Information
Result: The list of roles displays, along with each role's access to the object.
Select a role from the list, and then select Modify.
In the context menu, select one of the following options.
- To allow the role full access to the object, select Full Access.
  Note:This allows all users within the role to use API calls to add, read, modify, search, and update the object itself, and all fields within the object.
- To prevent the role from being able to view the object, select No Access.
- To customize the level of access the role will have to the object, select Custom Access.
Expected Result
Result: If you selected Full Access or No Access, a "Permissions Applied" message displays, indicating that the object permissions were successfully updated. If the role has access to any portal pages that use data from the object, the pages inherit the new permissions.
If you selected Custom Access, under Action Level Permissions, turn the Execute switch on to allow, or off to disallow, each of the following actions.
- Add: Allows each user in the role to add cards to their dashboard.
- Read: Allows the role to view cards.
- Modify: Allows each user in the role to change the object definition for cards on their dashboard
- Search: Allows the role to search for specific cards.
- Update: Allows each user in the role to modify the cards on their dashboard.
If you selected Custom Access, under Field Level Permissions, turn the Read switch on to allow read access, or off to disallow read access, for each of the fields.

Step Information

Note: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the User Card object.
If you selected Custom Access, under Field Level Permissions, turn the Update switch on to allow the role to update, or off to disallow update access, for each of the fields.

Step Information

Note: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the User Card object.
If you selected Custom Access, select Apply Permissions.

Expected Result
Result: A "Permissions Applied" message displays, indicating that the object permissions were successfully updated. If the role has access to any portal pages that use data from the object, the pages inherit the new permissions.

Field level permissions for the User Card object

The Access Control List (ACL) allows you to customize the level of access users have to the fields within the User Card object.

The list of fields is populated from the list of attributes in the User Card object. The following permissions can be modified for each field.

Read: allows or disallows read access.
Update: allows or disallows editing.

When modifying field level permissions, keep in mind that some fields are required for specific actions.

The following fields are available for the User Card object.

Userid

The ID of the user to which the dashboard belongs.