What Pipeer can read
Issue fields, comments, linked work, and related project context the authorizing user can already access.
Jira
Ask about Jira work, then take the next permitted action.
With Jira connected through each teammate’s own account, Pipeer can answer ticket status and blocker questions, link every claim to the issue, and prepare updates or owner briefs inside existing permissions.
What Pipeer can write
Permissioned issue updates, comments, and assignment changes when the workflow calls for action—and only through the connected identity.
Why this matters for security
There is no shared all-access Jira bot. Each workspace member authorizes their own connection, and tool-call history stays visible.