How to collaborate on tickets and requests in the Self Service Portal
On this page
When a ticket or a service request concerns more people than its requester, the requester can invite colleagues to it as collaborators. An administrator decides in the Admin Center who besides the requester may change a ticket's collaborators and checks the portal views that list shared tickets. Portal users invite collaborators, follow the shared tickets, and add comments in the Self Service Portal. Technicians follow the tickets in the Web App.
A ticket's collaborators are people related to the ticket by the collaborators relationship type, which comes from the workflow configuration. In a new 2026.1 database created with the Default Workflow, it is Collaborating / Collaborators.
Before you begin
- The actions, views, and workflow parameters described here are those of a new 2026.1 database created with the Default Workflow. A database upgraded from an earlier version need not have them, and an administrator may have changed them. See Default Workflow Configuration.
- To change workflow parameters in the Admin Center, you need the Workflow Configuration permission, which shows the Workflow Configuration tile. See Workflow Configuration and Parameters.
- To change a portal instance's settings in the Admin Center, you need the permission to configure the Self Service Portal. See Self Service Portal Settings.
- Portal users work in the Tickets and Requests area, which requires signing in. The area shows the tickets list or the service requests list only when its module is enabled for the portal; see Modules.
- Give every collaborator a valid primary e-mail address. On an incident and a service request, Web App actions such as Notify Requester check every active collaborator's address, and an action stops when the address is blank or not valid. See Find out why an action stops on an e-mail address.
1. Decide who may change the collaborators
In the portal, the Collaborators action of a ticket or a service request opens the form Add or Remove Collaborators. The Collaboration category of the workflow parameters holds two switches on who may add or remove collaborators. In a new 2026.1 database created with the Default Workflow, they are set as follows:
- "Self-Service Managers can add/remove collaborators" is set to on.
- "Self-Service Collaborators can add/remove other collaborators" is set to off.
To change them, in the Admin Center:
- In the Workflow and Business Logic section, click the Workflow Configuration tile.
- In the category tree, open Collaboration. The page shows one control for each parameter of the category.
- Change the values. Save and Cancel appear once you change a field.
- Click Save.
Saving writes only the current values of the category's parameters. A changed value reaches a running workflow engine only when the engine notices that the parameters were modified; see Workflow Overview. To change the values in the Settings App instead, see Workflow Configuration and Parameters.
2. Check the collaborator views of the portal
The portal lists a shared ticket in two kinds of views:
- A list's ordinary views show the tickets or service requests that the customer requested and the ones the customer collaborates on.
- A collaborator view shows the records the customer collaborates on. Collaborator views are listed to everyone.
In a new 2026.1 database created with the Default Workflow, the view configuration of the default settings holds three collaborator views of tickets, All Tickets (Collaborator), Open Tickets (Collaborator), and Closed Tickets (Collaborator), and three of service requests, All Service Requests (Collaborator), Open Service Requests (Collaborator), and Closed Service Requests (Collaborator). A new portal instance starts with a copy of the default settings' view configuration, and an instance that has no view configuration of its own uses the default settings' document.
When the supplied views suit your customers, there is nothing to do in this
stage. To change the columns of a collaborator view, edit the instance's
View Configuration tab in the Admin Center, under Apps and Portals >
Self Service Portal. The collaborator views are the TicketCollaboratorView
and ServiceCollaboratorView elements; to add or remove a column, add or
remove its <Field Name="…" /> line. Saving does not validate the document,
and a view that names a field the portal cannot resolve fails as a whole, not
just that column. Changes take effect in a few minutes after saving. See
Data views.
3. Invite colleagues to a ticket
The requester invites colleagues from the ticket's page in the Self Service Portal:
- Open the ticket or the service request. See Open a ticket.
- Click Collaborators. The page shows up to three actions as buttons. If there are more, click … and choose the action from the menu.
- In the form Add or Remove Collaborators, add the people you want to collaborate with, and submit the form.
For how the portal checks a form and what it shows, see Submit a Ticket. A manager can also add or remove collaborators while "Self-Service Managers can add/remove collaborators" is on. A collaborator can add or remove other collaborators only while "Self-Service Collaborators can add/remove other collaborators" is on, and it is set to off in a new 2026.1 database created with the Default Workflow.
4. Follow and add to a shared ticket
A collaborator finds the shared tickets in the Self Service Portal:
- In the drawer, click Tickets and Requests.
- In the tickets list or the service requests list, click the button with the name of the current view and choose a collaborator view, such as Open Tickets (Collaborator). The ordinary views list the shared tickets too.
- To open a ticket, click the link in the first column of its row.
The page of a ticket or a service request shows its history. At first only the newest entry is expanded; the history panel has buttons that expand or collapse every entry at once.
To add a comment:
- On the page of the ticket or the service request, click Update on a ticket or Update Request on a service request. If the action is not shown as a button, click … and choose it from the menu.
- In the form Add a Comment or Update Service Request, type the Comment, which is required. You can attach new files or existing attachments.
- Submit the form.
In a new 2026.1 database created with the Default Workflow, the comment is added to the history as a published entry in the Communication category, with the text "A comment was added via Self Service Portal". The action also runs its notification steps for the assigned party, the collaborators, the followers, and VIP enhanced service. The status is set to In Progress unless it is Unassigned, In Progress, Closed, or Pending Approval. The same form has a Mark Closed check box, which sets the status to Closed; its hint says that closing either cancels the record or confirms that it is resolved.
For searching, sorting, and refreshing the lists, see Track Your Tickets.
5. End collaboration
A collaborator who no longer needs to take part leaves the ticket in the Self Service Portal:
- Open the ticket or the service request.
- Click Update on a ticket or Update Request on a service request.
- Type the Comment, select End Collaboration, and submit the form.
End Collaboration removes you from the collaborators. The check box is in a part of the form whose condition depends on whether you collaborate on the record. To remove another person from the collaborators, use the form Add or Remove Collaborators of stage 3.
6. Keep technicians informed in the Web App
A technician can follow the ticket in the Web App to be e-mailed about it:
- Open the incident or the service request in the Web App.
- On the toolbar of the form, click Follow. When the toolbar is too narrow for all its action buttons, the last of them move into the More menu.
In a new 2026.1 database created with the Default Workflow, every active follower of an incident or a service request is e-mailed, at the primary e-mail address, when certain events happen to the ticket. One of them is a comment added through an update from the Self Service Portal; others are the ticket's creation and a status change. Each event has its own workflow parameter, whose name begins with Notify Followers, in the Following category, and all of them are on in the supplied configuration. The records you follow are listed in My Followed Items, an entry of the ITSM license module that appears only when the installed license includes that module; see Follow, Star and Mention.
In the Web App, an incident and a service request also have the Collaborators action, on the form's toolbar only, not on the Action Bar; see Incident Workflow and Service Request Workflow. A mention in a rich-text field reaches technicians only: the list of people to mention offers active technicians, and requesters cannot be mentioned. See Mention a technician.
Result
In a new 2026.1 database created with the Default Workflow, portal users invite colleagues to their tickets and service requests with the Collaborators action, and managers can do so too. Each collaborator finds the shared tickets in the portal's ordinary views and in the collaborator views, reads their history, and adds comments with Update or Update Request, which go into the history and run the notification steps for the assigned party, the collaborators, and the followers. A collaborator leaves a ticket with End Collaboration. Technicians who follow the ticket in the Web App are e-mailed when a comment arrives from the portal.