4/8/2023 0 Comments Group message opera mail![]() Note: Users assigned to the OPERA Supervisor user group may post to all transaction codes. This feature is useful if you wish to restrict posting ability according to a person's job. The user may only post against transaction codes assigned to the user group(s) to which the user belongs. This feature is active when the Cashiering>Transaction User Groups application function is set to Y. ![]() See User Group Administration below for further details.įor users with cashiering responsibilities, user groups may also be used to manage the user's ability to manually post to specific transaction codes. Because this feature is designed to be utilized by those users with limited access within OPERA, the user permission User Group Administration, must be granted and the application function General>User Group Administration must be set to Y prior to creating user groups that can be administratively attached to users. When this application function is set to active, a check-box appears on the User Group - Edit screen that allows for the permissions attached to the selected user group to be administered to other users. This feature is controlled by the application function General>User Group Administration. For instance Help Desk personnel and IT staff, whom would normally have no need to have access to any modules within OPERA, would still have a need to assign, modify and revoke user permissions and user groups to users. And if the user group is deleted, it will be deleted from all users who were previously associated to the group.įor users with no need to utilize OPERA for anything other than administering users and user groups, such as Help Desk or IT staff, user groups can be assigned to users without the administering user having to also have the same permissions or belonging to the same groups. In this situation, modifying permissions associated to a user group will in fact affect all users associated to the group. Users from multiple properties can be associated to the same user group as this is intentional making the assigning of individual permissions quicker for multiple properties in the same schema. For example, the Reservation group can have all Reservation permissions granted at Property A, but only permissions to view the reservations at Property B. Individual permissions for each property can then be associated to the configured user groups. If a user group is created while logged into a property, not only will this property see it, but as will all of the other properties that are part of the schema. This being the case, user groups can't be copied to other properties. User groups are not property specific, but global with regards to all of the properties in the schema. By assigning users to user groups, it is easier to manage user rights: Adding or removing a permission from the user group immediately affects the system rights for all users in that group. You assign OPERA permissions to the user group based on the job responsibilities of group members. User groups are a way to classify OPERA users by their need to access specific OPERA features in doing their jobs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |