Configuration and Permissions

This page explains what to configure and what access the app uses.

Project-scoped behavior

Simple Stakeholder Map is context-aware inside Jira projects:

  • Data is scoped to the current project
  • Each Jira project has a separate stakeholder map and task set
  • Users do not need to select a project manually inside the app

Required app scopes

The app uses minimal scopes:

  • read:jira-work
  • read:jira-user
  • storage:app

These scopes support project context, user display, and app data storage.

Before rollout, align on:

  1. Map owner: who keeps stakeholder ratings current
  2. Update cadence: weekly or sprint-based updates
  3. Task workflow: how communication tasks move to done
  4. Review participants: who joins engagement reviews

Team onboarding baseline

Use this lightweight onboarding checklist:

  • Team understands Power vs Interest scoring rules
  • Team understands SEAM level definitions
  • Team uses consistent stakeholder naming
  • Team agreed who can archive or remove stale entries

Where to document your internal conventions

Store your local process in project documentation, for example:

  • Who approves score changes for executive stakeholders
  • Which meetings trigger map review
  • How task outcomes are recorded