Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

General information

Updated on March 2, 2023

Use the General information tab to define the name and description of the mission.


Mission titles should reflect your content. The titles should be either role-based, product-based, or competency-based.

Attention: Mission titles are limited to 50 characters.

Use the following best practices when naming your mission:

GuardrailsUse ThisAvoid This
Use headline case when naming missions

Customer Decision Hub

Data Scientist

Introduction to customer decision hub

Data scientist

If the mission is capability-based, use a title that describes the capability using proper nouns

Low-Code App Builder

Cross-Sell on the Web

Building low-code applications with Pega Platform

Cross-sell on the web

If the mission is role-based, use a title that reflects the role using proper nouns

System Architect

Customer Service Developer

System Architect Essentials

Basics of Customer Service development

If the mission is product-based, use a title that reflects the product name

Pega Robot Manager

Customer Decision Hub

Introduction to Pega Robot Manager

Getting started with Customer Decision Hub

Level labels (Foundation, Intermediate, and Advanced) are also capitalized

Case Management Intermediate

Pega Customer Service Foundation

Case Management intermediate

Pega Email Bot foundation

Do not include introductory labels such as About, Introduction to, Overview of, How toCustomer Decision HubIntroduction to Customer Decision Hub
Do not add a year or version number in the mission title

User Interface Foundation

Pega Platform Release Update

Introduction to Pega Sales 2019

Pega Platform 8.5 Release Update

Do not include an audience label

System Architect

Pega Express Delivery

System Architect for Beginners

Pega Express Delivery for Product Teams

For more information about naming missions, see the article Naming your Pega Academy content.


In the Description field, enter a short description (2-3 lines) that describes the purpose of the mission. For example:

Begin your journey as a business architect with Pega technology by learning the capabilities of App Studio to develop applications on Pega Platform. Apply Design Thinking and the Pega Express methodology to define the right scope and yield faster business results. Influence the design of applications to support building for change, gain better business insight, and achieve greater user adoption.

Attention: Do not include a list of overall mission objectives. Objectives are added to each module.
Note: As a best practice for UX, do not include a Note tag or similar at the beginning of a description. The first 144 characters of the description are displayed on the content card in search results to provide users with a quick preview of the content.

Training Library

Add terms from the Training Library to indicate if the mission is a specific type of training. For example, Sales training, Corporate training, or UAP training.

Note: Training Library terms can be used on Pega Academy as a search filter.

To add a term from the Training Library:

  1. Click Add term from Training Library
  2. Select one of the training categories.
    "Training Type"

Member-type access

Use Member-type access to determine who can view the mission.

Select one or more roles to restrict mission visibility.

Note: To provide access for all, leave the Member-type access checkboxes clear.
Attention: A mission can only contain modules whose member-type access settings are equal to or less restrictive than the member-type access settings of the mission. For example, if the member-type access setting in the module is Pega only, the module can only be included in a mission whose member-type access setting is also Pega-only. If the member-type access setting in the mission is set to anything but Pega-only, you cannot include the Pega-only module in the mission.

For more information about member-type access settings, see the article Member-type access settings.

Organization access

The Organization Accessfield automatically populates to restrict viewing access of unpublished content to only members of your organization; the content is searchable from the Master Content list but is unable to be opened and edited.

Select the Bypass Organization Access to Allow members of other organizations check box to allow members outside your organization to edit the unpublished content.

Organization access field and bypass organization access check box
Note: Member-access settings override the organization bypass functionality. For example, if content is set to Pega-only, using the Bypass Organization check box does not work to allow Partner view or edit access.

Badge ID

Badge IDs are automatically associated to a mission.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us