Create Security Roles
- Have these permissions:
- settings.admin
- rbac.roles.create
- rbac.roles.update
- rbac.roles.read
- Any child roles you want to link must exist.
VNDLY has a set of preconfigured security roles, but you can create additional security roles to meet the needs of your organization.
You can also clone an existing security role by clicking
Clone
next to the appropriate role.- From the header, select .
- UnderSecurity, clickSecurity Settings.
- ClickCreate Role.
- As you create the role, consider:Only theNameof a role is required when creating, but the role will lack applicability unless other fields are completed.
Option Description NameRequired to create a new role. Identifies the role.DescriptionEnables you to provide additional details about the role.Role UsageIndicates the permissions that can be applied, as well as the types of users who can have this role.PolicyYou can use this to limit the role to specific resources or situations. See: Set Up Security Policies.Child RolesSelect an existing child role. Any user assigned this role is also assigned this child role. See: Create Child Security Roles.Role TagsRole tags are used to select roles and their members for list behaviors. Example: manager selection, notification targets, or report sharing.PermissionsSelect any additional permissions that you want to add to the role.You can find all permissions and their definitions on thePermissionstab of theSecurity Rolespage. Use these definitions to ensure you're selecting the correct permissions for the role. - ClickSave.
The new role is now available to assign to users.
Example: You need a resource manager role that doesn't have rights to edit work orders.
- Clone the resource manager role and rename the copyResource Manager No Work Order Edits.
- Keep the same role tags as the original resource manager role.
- Remove any permissions associated with editing a work order, such asworkorder.timekeeping_settings.edit.