Skip to main content
Administrator Guide
Last Updated: 2024-12-13
Create Security Roles

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.
  1. From the header, select
    More
    Company Settings
    .
  2. Under
    Security
    , click
    Security Settings
    .
  3. Click
    Create Role
    .
  4. As you create the role, consider:
    Only the
    Name
    of a role is required when creating, but the role will lack applicability unless other fields are completed.
    Option Description
    Name
    Required to create a new role. Identifies the role.
    Description
    Enables you to provide additional details about the role.
    Role Usage
    Indicates the permissions that can be applied, as well as the types of users who can have this role.
    Policy
    You can use this to limit the role to specific resources or situations. See: Set Up Security Policies.
    Child Roles
    Select an existing child role. Any user assigned this role is also assigned this child role. See: Create Child Security Roles.
    Role Tags
    Role tags are used to select roles and their members for list behaviors. Example: manager selection, notification targets, or report sharing.
    Permissions
    Select any additional permissions that you want to add to the role.
    You can find all permissions and their definitions on the
    Permissions
    tab of the
    Security Roles
    page. Use these definitions to ensure you're selecting the correct permissions for the role.
  5. Click
    Save
    .
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.
  1. Clone the resource manager role and rename the copy
    Resource Manager No Work Order Edits
    .
  2. Keep the same role tags as the original resource manager role.
  3. Remove any permissions associated with editing a work order, such as
    workorder.timekeeping_settings.edit
    .