Welcome
Managing security
HCL Launch uses a flexible team-based and role-based security model that maps to your organizational structure.
Roles and permissions
A role is a list of permissions that users have on the HCL Launch server. These permissions include the ability to create, edit, and delete objects, such as applications, environments, and components. The permission also includes the parts of the server interface that users can access.
Permissions reference for using application templates
Permissions for roles that create applications from templates.

Welcome
Welcome to the HCL Launch 7.2.2 documentation, where you can find information about how to install, maintain, and use HCL Launch.
Release information
Overview
This section provides overview and getting started information.
Learning
Tutorials and instructions for all experience levels.
Installing
An HCL Launch installation consists of the HCL Launch server, a database, and at least one agent.
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
Uninstalling
Learn how to uninstall an HCL Launch server, or agent.
Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Managing security
HCL Launch uses a flexible team-based and role-based security model that maps to your organizational structure.
- Guidelines for setting up server security
  Although there is no single best way to set up security for the server, the following steps are sufficient in most cases.
- SSL configuration
  With Secure Sockets Layer (SSL) technology, clients and servers can communicate securely by encrypting all communications. Data is encrypted before it is sent and decrypted by the recipient. This communication cannot be deciphered or modified by third-parties. In addition to encryption, SSL can also support authentication.
- Authorization realms
  Use the Authorization Realms pane to create authorization realms and user groups for the server. Groups can be imported from external systems, such as LDAP.
- Authentication realms
  Authentication realms manage users and determine user identity within authorization realms for the server.
- Roles and permissions
  A role is a list of permissions that users have on the HCL Launch server. These permissions include the ability to create, edit, and delete objects, such as applications, environments, and components. The permission also includes the parts of the server interface that users can access.
  - Creating roles and assigning permissions
    You can create roles on the server and assign permissions to them.
  - Setting server configuration security
    Set the server configuration permissions to define what users can do with the HCL Launch server security, also referred to as system security. Typically, these permissions are granted to administrative roles.
  - Permission reference
    This table lists the permissions on the server that you can assign to roles.
  - Permissions reference for using application templates
    Permissions for roles that create applications from templates.
- Security teams
  Users and groups on the server are assigned roles when they are added to teams.
- Security types
  Security types define categories of objects on the server. You can put all objects into a single category, or you can put them in separate categories and give roles different access rights to different categories.
- Tokens
  Tokens provide authorization for agents, agent relays, users, and external systems or applications from the server. Agents use tokens when they run process steps and communicate with the HCL Launch server and external services.
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Deploying
Learn how to deploy applications in HCL Launch.
Reporting
provides several different deployment and security reports.
Extending product function
Learn how to extend the function of HCL Launch.
Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.

Permissions reference for using application templates

Permissions for roles that create applications from templates.

Application templates can contain information about the components and environments that are initially available to applications that are created from the templates. The composition of the application template determines which role permissions are needed to create an application from a template.

Note: The role permissions in the following tables are only the permissions that are required to create the application from a template. More permissions are necessary to add elements to an application, run processes, or complete a deployment.

To create an application from a template, the user's role must have the following minimum permissions.

Note: The user cannot select components or create environments for the application.

Table 1. Permissions for role that creates applications from an application template
Product area	Permissions	Subpermissions
Application	View Applications	Edit Edit Basic Settings Manage Properties Manage Teams Create Create Applications From Template
Application Template	View Application Templates
Resource	Create Resources	Edit Manage Teams

To assign existing components to an application from the application template wizard, the user's role must also have the following permissions.

Note: To create an application from the application template wizard, the user's role must also have the permissions that are listed in Table 1.

Table 2. More permissions that are required to specify components
Product area	Permissions	Subpermissions
Application		Edit Manage Components
Component	View Components

To create environments for an application from the application template wizard, the user's role must also have the following permissions. To map resources to the environments from the application wizard, the role must also have the permissions in Table 2.

Note: To create an application from the application template wizard, the user's role must also have the permissions that are listed in Table 1.

Table 3. Permissions to create environments and map resources to them
Product area	Permissions	Subpermissions
Agent	View Agents
Application		Edit Manage Approvals Manage Environments
Environment	View Environments	Edit Edit Basic Settings Manage Base Resources Manage Properties Create Create Environments From Template
Environment Template	View Environment Templates
Resource	View Resources	Edit Manage Children Map to Environments Manage Teams
Resource Template	View Resource Templates