Skip to content

docs: Clarify that context sources are read-only#341

Open
promptless[bot] wants to merge 1 commit intomainfrom
promptless/clarify-context-sources-read-only
Open

docs: Clarify that context sources are read-only#341
promptless[bot] wants to merge 1 commit intomainfrom
promptless/clarify-context-sources-read-only

Conversation

@promptless
Copy link
Copy Markdown
Contributor

@promptless promptless bot commented Mar 30, 2026

Open this suggestion in Promptless to view citations and reasoning process

Adds explicit language across all context source documentation pages making clear that Promptless only reads from these services (Jira, Linear, Confluence) and never writes back to them. This addresses user confusion about whether Promptless updates Jira tickets or other context sources.

Changes:

  • Added prominent Info callout on the main Context Sources page stating context sources are "one-way"—Promptless reads but never writes
  • Updated intro paragraphs on Jira, Confluence, and Linear pages to explicitly state "read-only" access
  • Added clarifying sentences to Data Privacy sections on each page confirming Promptless never creates, updates, or deletes content

Why users were confused:

  1. The previous docs used verbs like "connect," "access," and "integration" without clarifying directionality
  2. The Atlassian OAuth consent shows write:jira-work scope (required by Atlassian for API access), which may have suggested write capability
  3. There was no explicit statement that context sources are one-way data flows

Files changed:

  • src/content/docs/docs/configuring-promptless/context-sources.mdx
  • src/content/docs/docs/configuring-promptless/context-sources/jira.mdx
  • src/content/docs/docs/configuring-promptless/context-sources/confluence.mdx
  • src/content/docs/docs/configuring-promptless/context-sources/linear.mdx

Context sources are integrations that give Promptless **read-only** access to your organization's existing tools and data. They provide additional context that helps Promptless create more accurate and comprehensive documentation suggestions.

<Info>
Context sources are **one-way**: Promptless reads information from these services to inform documentation updates, but never writes back to them. Your Jira tickets, Linear issues, and Confluence pages remain unchanged.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

User feedback in #dogfood about confusion thinking Promptless updates context sources like Jira

Source: https://Promptless.slack.com/archives/C08RZNK94GN/p1774543991616249

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
promptless-docs Ready Ready Preview, Comment Mar 31, 2026 10:38pm

Request Review

@mattlink
Copy link
Copy Markdown
Contributor

@Promptless are you able to fixup the commit history on this PR so that there is only a single commit with the intended changes?

Add explicit language across all context source pages making clear that Promptless only reads from these services and never writes back to them. This addresses user confusion about whether Promptless updates Jira/Linear tickets or Confluence pages.

Changes:
- Added prominent Info callout on main Context Sources page stating context sources are "one-way"—Promptless reads but never writes
- Updated intro paragraphs on Jira, Confluence, and Linear pages to explicitly state "read-only" access
- Added clarifying sentences to Data Privacy sections on each page
@promptless promptless bot force-pushed the promptless/clarify-context-sources-read-only branch from 0e912c0 to eb26955 Compare March 31, 2026 22:38
@promptless
Copy link
Copy Markdown
Contributor Author

promptless bot commented Mar 31, 2026

Done! I've squashed the commit history down to a single commit with a clean, descriptive message. The PR now shows just the one content commit instead of the 12 sync commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant