Portal
Define permissions for the Portal Component object
The Portal Component object contains data for the portal components in your tenant. The Access Control List allows you to define permissions for the Portal Component 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.
Important:The Authenticated Users role has read access to the Portal Component object by default. DSI highly recommends that you do not revoke this access.
To define permissions for the Portal Component object, complete the following steps in the portal.-
Go to the ACL page.Step InformationNote: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 Portal Component Object.Step InformationResult: 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 ResultResult: 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 the role to add portal components.
-
Read: Allows the role to view portal components.
-
Modify: Allows the role to change the object definition for the Portal Component object.
-
Search: Allows the role to search for specific portal components.
-
Update: Allows the role to edit portal components.
-
-
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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal Component 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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal Component object.
-
If you selected Custom Access, select Apply Permissions.Expected ResultResult: 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 Portal Component object
The Access Control List (ACL) allows you to customize the level of access users have to the fields within the Portal Component object.
The list of fields is populated from the list of attributes in the Portal Component 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 Portal Component object.
Name
The name of the portal component.
Full access to this field is required when adding or editing a portal component.
Usage
The usage category of the component. Possible values are page, card, and config.
Full access to this field is required when adding or editing a portal component.
Moduleid
The ID of the module to which the component belongs.
Full access to this field is required when adding or editing a portal component.
Createdby
The userid of the user who created the portal component.
Full access to this field is required when adding or editing a portal component.
Updatedby
The userid of the user who last updated the portal component.
Full access to this field is required when adding or editing a portal component.
Whencreated
The date and time a portal component was created.
Full access to this field is required when adding a portal component.
Whenupdated
The date and time a portal component was updated.
Full access to this field is required when adding or editing a portal component.
Portalfileid
The ID of the portal file that contains a component.
Full access to this field is required when adding or editing a portal component.
Thumbnailfileid
The ID of the thumbnail file associated with the component.
Full access to this field is required when adding or editing a portal component.
Portalcomponentid
The ID assigned to a portal component.
Full access to this field is required when adding or editing a portal component.
Define permissions for the Portal Page object
The Portal Page object contains data for the portal pages in your tenant. The Access Control List allows you to define permissions for the Portal Page 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.
Important:The Authenticated User role has read access to the Portal Page object by default. DSI highly recommends that you do not revoke this access.
To define permissions for the Portal Page object, complete the following steps in the portal.-
Go to the ACL page.Step InformationNote: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 Portal Page Object.Step InformationResult: 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 ResultResult: 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 the role to add portal pages.
-
Read: Allows the role to view portal pages.
-
Modify: Allows the role to change the object definition for the Portal Page object.
-
Search: Allows the role to search for specific portal pages.
-
Update: Allows the role to edit portal pages.
-
-
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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal Page 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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal Page object.
-
If you selected Custom Access, select Apply Permissions.Expected ResultResult: 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 Portal Page object
The Access Control List (ACL) allows you to customize the level of access users have to the fields within the Portal Page object.
The list of fields is populated from the list of attributes in the Portal Page 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 Portal Page object.
Name
The name of the portal page.
Full access to this field is required when adding or editing a portal page.
Title
The title of the portal page.
Full access to this field is required when adding or editing a portal page.
Moduleid
The ID of the module to which the portal page belongs.
Full access to this field is required when adding or editing a portal page.
Createdby
The userid of the user who created the portal page.
Full access to this field is required when adding or editing a portal page.
Updatedby
The userid of the user who last updated the portal page.
Full access to this field is required when adding or editing a portal page.
Description
The description associated with the portal page.
Whencreated
The date and time a portal page was created.
Full access to this field is required when adding a portal page.
Whenupdated
The date and time a portal page was updated.
Full access to this field is required when adding or editing a portal page.
Portalpageid
The ID assigned to the portal page.
Full access to this field is required when adding or editing a portal page.
Portalcomponentid
The ID for the portal component associated with a portal page.
Full access to this field is required when adding or editing a portal page.
Define permissions for the Portal File object
The Portal File object contains data for the portal files in your tenant. The Access Control List allows you to define permissions for the Portal File 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.
Important:The Authenticated User role has read access to the Portal File object by default. DSI highly recommends that you do not revoke this access.
To define permissions for the Portal File object, complete the following steps in the portal.-
Go to the ACL page.Step InformationNote: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 Portal File Object.Step InformationResult: 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 ResultResult: 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 the role to add portal files.
-
Read: Allows the role to view portal files.
-
Modify: Allows the role to change the object definition for the Portal File object.
-
Search: Allows the role to search for specific portal files.
-
Update: Allows the role to edit portal files.
-
-
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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal File 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 InformationNote: Some fields are required for specific actions. For more information about the available fields, refer to Field level permissions for the Portal File object.
-
If you selected Custom Access, select Apply Permissions.Expected ResultResult: 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 Portal File object
The Access Control List (ACL) allows you to customize the level of access users have to the fields within the Portal File object.
The list of fields is populated from the list of attributes in the Portal File 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 Portal File object.
Name
The name of the portal file.
Full access to this field is required when adding or editing a portal file.
Filename
The filename of the portal file.
Full access to this field is required when adding or editing a portal file.
Moduleid
The ID of the module to which the portal file belongs.
Full access to this field is required when adding or editing a portal file.
Createdby
The userid of the user who created the portal file.
Full access to this field is required when adding or editing a portal file.
Updatedby
The userid of the user who last updated the portal file.
Full access to this field is required when adding or editing a portal file.
Whencreated
The date and time a portal file was created.
Full access to this field is required when adding a portal file.
Whenupdated
The date and time a portal file was updated.
Full access to this field is required when adding or editing a portal file.
Portalfileid
The ID assigned to a portal file.
Full access to this field is required when adding or editing a portal file.
Loading...
There was a problem loading this topic