---
sourceDocument: Yokohama Healthcare and Life Sciences
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/healthcare-life-sciences

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama 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: Yokohama  
Updated January 30, 2025  
![](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

In the Pre-Visit Management application, you can define who acts as agent connectors or contributors for procedure request cases.
This functionality allows admins to assign specific roles and permissions to users, controlling access and actions related to procedure request cases and tasks.
Note that starting with the Yokohama release, Pre-Visit Management is preparing for future deprecation---it will be hidden on new instances but remains supported.
Show full answer Show less  

## Key Features

* **Agent Connector Role:** Users with this role act as fulfillers who can create, update, and close procedure request cases and tasks. Admins assign the `snprevisit.agentconnector` role and relevant agent-specific roles to groups, which are then assigned to users.
* **Contributor Role:** Contributors can create and read procedure request cases. Admins assign the `snprevisit.contributor` role along with appropriate contributor roles to groups, then assign users to these groups.

## User Profile Examples and Role Assignments

The application provides example profiles combining Pre-Visit Management roles with Customer Service Management (CSM) industry data model roles:

* **Agent Connector Example:** `Location agent` -- Can create and fulfill procedure requests at their business location. Requires membership in the service organization and assignment of the Location Consumer Agent responsibility type. Roles assigned include `snprevisit.agentconnector` and `sncustomerservice.svclocationconsumeragent`.
* **Contributor Examples:**
  * **Relationship contributor:** Creates requests only for patients with an established relationship. Requires membership in the patient's consumer team and the Relationship Manager responsibility type. Assigned roles: `snprevisit.contributor` and `sncustomerservice.relationshipcontributor`.
  * **Patient contributor:** Creates requests for any patient. Assigned roles: `snprevisit.contributor` and `sncustomerservice.consumercontributor`.
  * **Location contributor:** Creates requests for patients within a specific service organization where the user is a member. Requires Location Contributor responsibility type. Assigned roles: `snprevisit.contributor`, `sncustomerservice.serviceorganizationcontributor`, and `sncustomerservice.consumercontributor`.

## Practical Application for ServiceNow Customers

By configuring these roles and profiles, admins can precisely control access to procedure request cases in Pre-Visit Management, ensuring users have appropriate permissions based on their job function and relationship to patients or service organizations. This setup enhances security and operational efficiency in managing procedure requests.

For role assignment, admins should assign roles to groups and then assign those groups to users, following standard ServiceNow role and group management practices.  
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://servicenow-prod.fluidtopics.net/pVdBKh1mMw7tvatgh2xIYA#pre-visit-connector-contributor__section_yhp_czw_ztb)
* [Contributor](https://servicenow-prod.fluidtopics.net/pVdBKh1mMw7tvatgh2xIYA#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=yokohama&pubname=yokohama-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=yokohama&pubname=yokohama-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=yokohama&pubname=yokohama-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=yokohama&pubname=yokohama-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=yokohama&pubname=yokohama-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}