Securing

When building applications, user roles require various levels of security access. A manager is able to review submitted forms, but an administrator can delete them. The following topics describe how to set security levels for all levels of users.

Leap allows application designers to compose applications that combine user interfaces, data records, and a stages-based lifecycle. The Leap security settings govern access to applications and data by defining who can edit, maintain, deploy applications, and access data for submitted forms.

You can define your security rules using the Access tab from within the Design environment. These topics describe the Leap security concepts and how to use the Access tab to grant access to users in your organization.

• Defining basic security roles for users
  Create roles for users in your organization so they can work with data that is relevant to them.
• Assigning users or groups to roles
  Give the users in your organization permission to work with the data relevant to them by assigning them roles.
• Setting Stage permissions
  Setting Stage permissions defines the “Create”, “Read”, “Update”, and “Delete” permissions for each role in a stage.
• Defining permissions to share data with other applications
  HCL Leap applications can share data through services with other Leap applications. To allow other applications access to the data from the application you are designing, you must define the security permissions.
• Assigning users to maintain the application
  To define who can edit an HCL Leap application, use the design settings in the Access tab.
• Setting up security for anonymous access
  Using the correct permissions, you can allow anonymous users to access a form.