Invite Collaborator window Inviting collaborators

Use this window to invite people (by email) to collaborate in developing the application. For example, a Lead Business Analyst can invite other business analysts to edit and add specifications and requirements to the application. They can also invite subject matter experts to review the application in progress, the specifications, and other assets.

When you invite people, you also set their access level to the application. Collaborators can be editors (having access to add and edit application assets) or reviewers (having access only to review assets, and not create or edit them).

After specifying the information in this window, click Send Invitation. The system generates operator IDs based on the specified email addresses, and then sends invitations by email to those addresses. Each email includes:

• A boilerplate message inviting them to access the application.
• The specified access level (Editor or Viewer)
• The recipient's assigned operator ID and password
• The personal message (if specified)
• A link that the recipient can click to log into the application.

Field	Description
Email Address	Email addresses for the invitees. Click to add more than one address.
Collaborator Role	Application access level for the invitees. All of the invitees specified in the Email Address receive this access level. Choices are: Viewer — Access to only view application assets, and not create new ones or edit existing ones. The Profile Explorer is available to people with the Viewer access. The other explorers are not available to people with Viewer access. Editor — Access to edit application assets and create new ones.
Personal Message	A text message that is included in the invitation email. In the Personal Message field, enter the text message, such as "I would like you to review the application profile by August 31, 2012."

How it works

After clicking Send Invitation, the system uses directed Web access and the standard Default outbound email account to send invitation emails to the invitees. The system sends the email according to the schedule for the SendCorr agent, one of the set of Pega-ProCom agents.

Each invitation email contains the personal message (if entered by the inviter) and a URL for the invitee to click to activate their operator ID in the system. If the inviter's operator ID has a specified email address, the invitation email uses that as its From: address. If the inviter's operator ID does not specify an email address, the system uses the Default email account's From address in the invitation.

To complete activation of their system access, the invitees use the Internet Explorer browser to go to the URL listed in their invitation emails. The system displays a form in which the invitee enters a name and password of his or her choice, and clicks the button to activate his or her system access. The system then sends a confirmation email to the collaborator with their log-in name and the URL to log into the PRPC system.

Note: The system creates an operator ID for the collaborator, using the collaborator's email address as the Operator ID and the password submitted by the collaborator on the activation form. The name submitted by the collaborator is used for the Full Name field of the operator ID.

About the collaborator access groups

When the first invitee of a collaborator role (Viewer or Editor) activates his or her account, the system generates the corresponding access group, using the name of the inviter's current application:

• current_application_name:Viewers
• current_application_name:Editors

The system uses those access groups in the operator IDs of subsequent invitees, according to whether Viewer or Editor is specified as their role.

By default, the access groups use the standard PegaRULES:ViewerCollaborator and PegaRULES:EditorCollaborator access roles.

Required system configuration

The following items must be configured in the PRPC system to support the ability to invite collaborators and create and activate their operator IDs:

• The system's Public Link URL must be set. See the description for Public Link URL on the Resource URLs tab of the System — Settings landing page.
• The standard Default.Notify email account must be configured for outbound email.
• Agents must be enabled for the system, and the SendCorr agent in the Pega-ProCom agent schedule must be enabled to run periodically. See Agents — Concepts and terms.

	directed Web access
	Atlas — Initial Email Accounts

Help Home