--- 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 --- # Roles and visibility for project tasks # Roles and visibility for project tasks {#ariaid-title1} Release version: Brazil Updated September 17, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Roles determine which store personas see project tasks in Retail, which surfaces they reach, and which actions they can take on a task. ## Roles required {#rahi-retail-spm-project-tasks-roles__spm-project-tasks-roles-required} To see project tasks, a store persona needs a retail responsibility and one of the project stakeholder roles. The stakeholder roles are defined by the App SPM Retail dependency. Retail neither defines nor assigns them, and no retail role inherits them. {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_roles__entry__3} | Role | Persona | Grants | |-|-|-| | A retail contributor or fulfiller responsibility | Store associate or store manager | Base requirement. A persona needs one of these before a stakeholder role has any effect. | | `sn_bus_loc.location_project_stakeholder` | Store associate | Access to the project task surfaces for the persona's service organization. | | `sn_bus_loc.location_manager_project_stakeholder` | Store manager | The same access as the associate role, plus the actions that change assignment. | [Table 1. Roles that grant access to project tasks] {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_roles} Note: Access is scoped to the persona's service organization. A persona at one store doesn't see the project tasks of another store, even when they belong to an assignment group that includes members of that store. ## Surfaces by persona {#rahi-retail-spm-project-tasks-roles__spm-project-tasks-roles-surfaces} The surfaces aren't all available to the same personas, and the two mobile paths differ from each other. Note: A stakeholder role is always required, and access is scoped to the persona's own store. A persona holding a retail role but no stakeholder role sees none of these surfaces. {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_surfaces__entry__3} | Surface | Available to | Notes | |-|-|-| | Projects category in the portal | Contributor or fulfiller with a stakeholder role | The category appears whenever the plugin is active and the persona holds a stakeholder role. It isn't hidden when no project tasks are assigned. | | Projects entry on mobile | Contributor or fulfiller with a stakeholder role | Hidden when the persona has no project tasks assigned to their store. This differs from the portal. | | Tasks filter in My Work on mobile | Fulfiller with a stakeholder role | A contributor never reaches this filter, because the My Work tab is itself limited to fulfillers. A stakeholder role doesn't override that. | [Table 2. Project task surfaces and who reaches them] {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_surfaces} ## Actions by persona {#rahi-retail-spm-project-tasks-roles__spm-project-tasks-roles-actions} {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_actions__entry__3} | Action | Store associate | Store manager | |-|-|-| | View projects and project tasks for their store | Yes | Yes | | Add a comment or an attachment | Yes | Yes | | Close a task | Yes, when the task is assigned to them and has no open child tasks | Yes, on the same conditions | | Assign task and Assign to me | Yes, when the persona can change the assignee and the assignment group of the task | Yes, on the same condition, including reassigning a task that is assigned to an assignment group | [Table 3. Project task actions by persona] {#rahi-retail-spm-project-tasks-roles__table_spm_project_tasks_actions} Each action is checked separately, so an action appears only when the persona can perform it. The check runs again on the server before the update is applied, and a persona without permission receives a message rather than a silent failure. Note: Whether these actions appear depends on the persona's permission to change the assignee and assignment group fields. That permission is granted by the Customer Service Management (CSM) and Retail Strategic Portfolio Management Suite applications, not by Retail. The requirements expect it to sit with the store manager. The portal and the mobile application apply the same rule. ## What makes an individual task visible {#rahi-retail-spm-project-tasks-roles__spm-project-tasks-roles-visibility} The Visible to customer field : The project manager sets this field on each project task. A task without it set doesn't appear on any store-facing surface, whatever roles the persona holds. Service organization scoping : A persona sees only the project tasks of the store they belong to. Record-level access to project and project task records is owned by the Customer Service Management (CSM) and Retail Strategic Portfolio Management Suite applications. Retail adds no access control rules or query rules of its own on those tables. Its portal lists filter on the Visible to customer field as well, so an unflagged task is excluded before the list reaches the browser. **Related concepts** * [Project tasks in Retail](https://www.servicenow.com/docs/5Bv_n72Z6nphxp28_poJGg "Store associates and managers can view and act on the project work behind a store opening, closing, renovation, or relocation without leaving the Retail.") **Related reference** * [Project task data model](https://www.servicenow.com/docs/wr6TVFRZV68pu_TtpY_jBg "The project and project task records that Retail reads, the fields it displays, and the three fields it writes.")