Access and permissions

Promptless connects to the tools your team already uses, and follows the principle of least privilege: each connection grants only the access the work needs. Promptless reads from your tools, writes only to your documentation repository, and keeps each connection within the scope you set. You can revoke that access at any time. This page describes that posture for a security review and links to the pages that cover each connection in detail.

Use cases

• Answer a security reviewer’s questions about which systems Promptless reads, which it writes to, and how far each connection reaches.
• Choose how to connect a documentation repository: with write access limited by path scope, or through the read-only GitHub app.
• Plan how to revoke or rotate Promptless’s access, for example at the end of a pilot.
• Decide which Promptless role each member of your team needs.

What Promptless reads versus writes

Promptless writes in one place, your documentation repository. Every other connection is for reading:

Connection	Access	What Promptless does
Context sources, such as Jira, Linear, Confluence, Notion, Google Drive, and Slite	Read-only	Reads content to inform suggestions. Your tickets, issues, and pages stay unchanged.
Source code, such as a GitLab project that sends merge request triggers	Read-only	Reads code changes for context and pushes no code to these projects. Connecting a GitLab group does write to GitLab: Promptless creates merge request webhooks on the group’s projects and sets its bot avatar.
Documentation repositories on GitHub or GitLab	Write	Pushes a branch and opens a pull request on GitHub or a merge request on GitLab. Path scope limits which files it can change.

By default, you review every pull or merge request before it merges. If you enable auto_merge in a publishing policy, Promptless merges its own changes without review.

Promptless also stores little. It keeps the feedback you give it and integration auth tokens, but not the content behind those tokens. It processes source code, support conversations, and context-source data in real time without keeping a copy. It doesn’t use customer data to train or fine-tune models. For the full breakdown, see Data handling and classification.

Scope each connection

Each integration reaches only what you authorize:

Connection	How to keep its scope tight
GitHub repositories	When you install the GitHub app, choose Only select repositories and grant only the repositories Promptless needs. See the GitHub and GitHub Enterprise integration pages.
GitLab groups	Scope the group access token to a group or subgroup that contains only the projects Promptless needs. See the GitLab integration page.
Context sources	These connect through OAuth, so Promptless inherits the permissions of the account that authorized the connection. It searches only the projects, spaces, or drives you configure. For the tightest scope, connect through a dedicated service account, and share only the drives and folders Promptless needs with it.

Read-only options

If you don’t need Promptless to write to a repository, you can connect it read-only:

Provider	Read-only option
GitHub	The GitHub (read-only) app reads any repository you grant it. It publishes documentation to a public repository by opening a pull request from a fork.
GitLab	None. One api-scoped group access token serves reads and writes. Limit its reach by scoping it to a group or subgroup with only the projects Promptless needs.

For how GitLab tokens limit what Promptless can reach, see Token scope considerations.

Limit where Promptless can write

Path scope limits which files Promptless can change in a documentation repository it has write access to. Set it with Only watch these folders when you set up a doc collection. Promptless then changes only files that match one of those paths or sit inside them. It rejects a suggestion that reaches outside that scope, with an error that lists the out-of-scope files. Path scope keeps writes inside your documentation area, which matters in a monorepo where docs live beside source code. For setup, see GitHub repos (docs as code) and GitLab projects (docs as code).

Revoke or rotate access

You can end Promptless’s access at any time:

• Disconnect an integration from its card on the integrations page. Disconnecting revokes Promptless’s access to that service.
• Uninstall the GitHub app. You or Promptless can revoke the GitHub app connection.
• Rotate or remove a provider token, such as a GitLab group access token, on the provider’s side.

Roles inside Promptless

Role-based access control governs what each person can do in Promptless itself:

Role	What it can do
Admin	Full access to organization settings, team management, integrations, projects, and all suggestions, including the Agent Knowledge Base.
Editor	Edit suggestions and create tasks. Editors can’t manage organization settings, integrations, or team members.
Collaborator	View suggestions and leave comments. Collaborators can’t edit suggestions or send requests to Promptless.

To assign roles, see Account management.

Related resources

• Single sign-on (SSO) setup for sign-in through your identity provider.
• Network architecture for multi-tenant isolation and encryption.
• Compliance and certifications for SOC 2, penetration testing, and incident notification.