---
sourceDocument: Brazil Retail Industry
sourceDocumentLink: https://www.servicenow.com/docs/r/retail-industry

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Retail Industry

ft:clusterId :

    - rahi

bundleId :

    - rahi

workflow :

    - Customer and Industry


---

# Enable project tasks

# Make project tasks available to a store team {#ariaid-title1}

Release version: Brazil  
Updated September 17, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Install the App SPM Retail plugin and give your store personas the roles and organization
membership they need before project tasks appear in Retail.

## Before you begin

Role required: sn_customerservice.projectmanager, sn_service_org.project_manager or sn_customerservice.projectstakeholder

## About this task

Project tasks reach a store team only when three things are true: the plugin is installed, the persona
holds a project stakeholder role, and the persona belongs to the retail organization for their store.
Retail has no separate setting that turns the feature on or off.

## Procedure

1. Install the App SPM Retail application on your instance.  
   The project task surfaces install with the plugin. When the plugin isn't present, none of the
   artifacts are installed and no activation errors occur.
2. Grant a project stakeholder role to each store persona who needs project task access.  
   Assign sn_bus_loc.location_project_stakeholder to a store associate, or
   sn_bus_loc.location_manager_project_stakeholder to a store manager. These roles come from the
   App SPM Retail dependency. No retail role includes them, so a persona who holds
   only a retail role sees nothing. For the procedure, see [Assign roles to Retail users](https://www.servicenow.com/docs/WhpkfWSBYKeRcv6jLFAy2w "Assign specific roles to give retail users visibility into organizations and the hierarchies they manage.").
3. Confirm that each persona belongs to the retail organization for their store.  
   Project task access is scoped to the persona's service organization, so a persona who isn't a
   member of their store's organization sees no project tasks. For the procedure, see [Configure your organizational structure](https://www.servicenow.com/docs/sJfdmMvvatuRe6BuMCb0Iw "Configure the structure of your retail organization within Retail Core.").
4. Ask the project manager to set the Visible to customer field on the project tasks that the store team should work.  
   This is done on the headquarters side. A project task without the field set doesn't appear in
   the portal or the mobile application, whatever roles the persona holds. For more information,
   see [Explore retail projects](https://www.servicenow.com/docs/access?context=explore-retail-projects-spm-r&version=brazil&pubname=brazil-it-business-management&ft:locale=en-US).
{#rahi-retail-spm-project-tasks-enable__steps_spm-project-tasks-enable}

## Result

Store personas see the project tasks for their own store, and can act on them in the portal and in the
mobile application. For what each persona can do, see [Roles and visibility for project tasks](https://www.servicenow.com/docs/VRYeJfqknVo_uH3ei8pYog "Roles determine which store personas see project tasks in Retail, which surfaces they reach, and which actions they can take on a task.").