---
sourceDocument: Australia Healthcare and Life Sciences
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/healthcare-life-sciences

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Determining additional user profiles in Pre-Visit Management

# Determining additional user profiles in Pre-Visit Management {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Determining Additional User Profiles in Pre-Visit Management

This guide outlines how to determine user profiles that can serve as agent connectors or contributors within the Pre-Visit Management application.
With the upcoming deprecation of this application, it will be hidden on new instances but remain supported.
Admin users can create profiles with specified access to procedure request cases and related tasks.
Show full answer Show less  

## Key Features

* **Agent Connector:** Acts as a fulfiller who can create, update, and close procedure request cases. Admins can assign the `snprevisit.agentconnector` role to groups for user allocation.
* **Contributor:** Functions as a requester who can create and read procedure request cases. Admins can assign the `snprevisit.contributor` role to groups for user allocation.

## Key Outcomes

By managing user profiles effectively, you enable streamlined handling of procedure request cases. The agent connector and contributor roles allow for tailored access based on specific needs, enhancing workflow efficiency in Pre-Visit Management. Profiles can be customized to align with service organization membership and established patient relationships.  
You can determine who can act as an agent connector or contributor for procedure request
cases in the Pre-Visit Management application.  
Important:  
Starting with the Yokohama release, Pre-Visit Management is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

For details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support knowledge base.

As a user with the admin role, you can create contributor and agent connector profiles with the
desired level of access to procedure request cases, case tasks, and other case-related
information.

The sn_previsit.contributor and sn_previsit.agent_connector roles installed with the Pre-Visit Management application provide the following user profiles:

* [Agent connector](https://www.servicenow.com/docs/tKtUZ75geysQSHQ4EW78fQ#pre-visit-connector-contributor__section_yhp_czw_ztb)
* [Contributor](https://www.servicenow.com/docs/tKtUZ75geysQSHQ4EW78fQ#pre-visit-connector-contributor__section_r5b_czw_ztb)

{#pre-visit-connector-contributor__ul_amw_k4x_ztb}

## Agent connector {#pre-visit-connector-contributor__section_yhp_czw_ztb}

An agent connector within the Pre-Visit Management application acts as a
fulfiller who can create, update, and close procedure request cases and tasks.

As a user with the admin role, you can determine who can act as an agent connector for the
procedure request cases by assigning the sn_previsit.agent_connector role and other
agent-specific roles to a group, and then assigning the group to the user with the agent
connector profile. To assign roles to a group, see [Assign a role to a group](https://www.servicenow.com/docs/access?context=t_AssignRoleToGroup&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

The following table describes the location agent profile within the Pre-Visit Management application scope that you can refer to as an example for
combining the sn_previsit.agent_connector role with the [industry data model roles](https://www.servicenow.com/docs/access?context=csm-data-model-roles&version=australia&pubname=australia-customer-service-management&ft:locale=en-US) in the CSM
application.
{#pre-visit-connector-contributor__table_n1p_spx_ztb__entry__3}

| Profile | Description | Assigned roles |
|-|-|-|
| Location agent | Creates and fulfills procedure request cases in the agent's business location. Note: To create procedure request cases for a service organization (business location), a user with the location agent profile must be a member of the service organization and assigned the Location Consumer Agent responsibility type. The mapping of a service organization and its members is included in the Service Organization Member \[sn_csm_service_organization_member\] table. | sn_previsit.agent_connector and sn_customerservice.svc_location_consumer_agent |
[Table 1. Example agent connector profile for Pre-Visit Management]

{#pre-visit-connector-contributor__table_n1p_spx_ztb}

## Contributor {#pre-visit-connector-contributor__section_r5b_czw_ztb}

A contributor within the Pre-Visit Management application acts as a requester
who can create and read procedure request cases.

As a user with the admin role, you can determine who can act as a contributor to the procedure
request cases by assigning the sn_previsit.contributor role and other contributor roles to a
group, and then assigning the group to the user with the contributor profile. To assign roles to
a group, see [Assign a role to a group](https://www.servicenow.com/docs/access?context=t_AssignRoleToGroup&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

The following table describes different contributor profiles within the Pre-Visit Management application scope that you can refer to as an example for
combining the sn_previsit.contributor role with the [contributor roles](https://www.servicenow.com/docs/access?context=csm-contributor-user-roles&version=australia&pubname=australia-customer-service-management&ft:locale=en-US) in the CSM application.
{#pre-visit-connector-contributor__table_uvh_kmw_ztb__entry__3}

| Profile | Description | Assigned roles |
|-|-|-|
| Relationship contributor | Creates procedure request cases for only those patients with whom a relationship is established. For more information, see [Create relationships](https://www.servicenow.com/docs/access?context=configure-data-model-relationships&version=australia&pubname=australia-customer-service-management&ft:locale=en-US). Note: To create procedure requests for a patient, a user with the relationship contributor profile must have a relationship with the patient included in the Consumer Team Member \[sn_customer_rel_consumer_to_user_list\] table and the Relationship Manager responsibility type. | sn_previsit.contributor and sn_customerservice.relationship_contributor |
| Patient contributor | Creates procedure request cases for any patients. | sn_previsit.contributor and sn_customerservice.consumer_contributor |
| Location contributor | Creates procedure request cases for any patients in a particular service organization (business location) with which the user is associated as a service organization member. Note: To create procedure request cases for a service organization (business location), a user with the location contributor profile must be a member of the service organization and assigned the Location Contributor responsibility type. The mapping of a service organization and its members is included in the Service Organization Member \[sn_csm_service_organization_member\] table. | sn_previsit.contributor, sn_customerservice.service_organization_contributor, and sn_customerservice.consumer_contributor |
[Table 2. Example contributor profiles for Pre-Visit Management]

{#pre-visit-connector-contributor__table_uvh_kmw_ztb}