Skip to content

docs: Add setup prerequisites and collaborative onboarding to quickstart guide#309

Merged
prithvi2206 merged 3 commits intomainfrom
promptless/setup-prerequisites-and-collab-onboarding
Mar 18, 2026
Merged

docs: Add setup prerequisites and collaborative onboarding to quickstart guide#309
prithvi2206 merged 3 commits intomainfrom
promptless/setup-prerequisites-and-collab-onboarding

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Mar 18, 2026

Open this suggestion in Promptless to view citations and reasoning process

Expands the Setup & Quickstart guide to address common questions prospects have before starting setup.

Changes:

  • Added "What permissions are needed?" subsection listing admin requirements for Slack, GitHub, Jira/Confluence, and Linear integrations
  • Added tip callout explaining the invitation flow for users without required permissions
  • Enhanced the collaborative onboarding explanation to clarify that setup doesn't need to be completed by a single person

Revision (Mar 18): Converted the "Inviting teammates to help with setup" section from a heading with paragraph text to a Tip callout for better visual prominence.

Why this helps:
Prospects often ask what they need to have ready before scheduling kick-off calls. This update lets them self-serve answers about required permissions and understand that they can invite IT/Engineering teammates to help connect specific integrations.

promptless bot and others added 2 commits March 17, 2026 20:25
Expands the "Before You Start" section to address common prospect questions:
- Lists admin permissions needed for each integration (Slack, GitHub, Jira, Linear)
- Explains that teammates can be invited to help with setup
- Clarifies that setup can be handed off between team members

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Reformatted the inviting teammates content from a heading with
paragraph text to a Tip callout for better visual hierarchy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

<Tip>
If you don't have admin access to connect a particular integration, you can invite someone from your IT or Engineering team directly from the onboarding wizard. The invited person receives an email that brings them to the same onboarding page you're on, and they can pick up exactly where you left off.
</Tip>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Prithvi's response to prospect Susannah (Alation): "you can invite an admin from eng/IT to connect those apps to Promptless, and they can pick up where you left off... The email they get will bring them to the same exact onboarding page that you are looking at. Everyone you invite can continue the onboarding steps."

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

/>

Your progress saves automatically—if you leave and come back later, you'll pick up where you left off. Team members from the same organization can continue setup without losing previous progress.
Your progress saves automatically—if you leave and come back later, you'll pick up where you left off. Setup doesn't need to be completed by a single person: any teammate you invite can continue from the current step, making it easy to hand off to someone with the right permissions for a specific integration.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Prospect email question: "What information do we need to have ready from GitHub, Slack, JIRA, etc?" - prompted documentation of prerequisites and collaborative setup flow.

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

@vercel
Copy link

vercel bot commented Mar 18, 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 18, 2026 2:43pm

Request Review

The Tip component was used without being imported, causing the build to fail
with "Expected component Tip to be defined" error.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@prithvi2206 prithvi2206 merged commit 102102d into main Mar 18, 2026
4 checks passed
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