Quickstart
Choose Knowledge or Admissions, then follow that product’s setup guide. This quickstart covers the shared first steps; exact screens and available sources can vary by deployment.
1. Sign Up
Open the console address provided by your administrator and create an account. During setup, you may be asked to:
- Enter your email and create a password
- Name your organization
- Confirm the product access and commercial terms available to your organization
After sign-up, you're taken to the Pragence dashboard.
2. Create a Project
Projects keep a product’s sources, settings and access together.
Create a project from the console and choose the product available to your organization. If you are not sure which product to choose, see Choose your product.
3. Connect a Knowledge Source
Connect an authorized source offered by your deployment. Common options include:
- Google Drive — Google sign-in or a service account, with optional folder scoping
- SharePoint, OneDrive and Confluence — Microsoft or Atlassian sign-in, when the deployment has that sign-in set up
- Notion — integration token and optional database scoping
- Website sources — sitemap or Firecrawl when enabled
- File upload — when available in your workspace
- Help centres, sites and trackers — Zendesk, Intercom, ServiceNow, Airtable, GitHub, GitLab, Canvas, WordPress and Ghost; see Help centres, sites and trackers
- Workplace tools — Slack messages, Jira, HubSpot, Zendesk tickets, GitHub, Freshdesk, Pipedrive and Google Sheets; see Workplace tools
In the console these are all under Sources. Use
GET /api/v1/connectors/types to see the connector types enabled in your
deployment. The generic SQL, REST and file-storage pipelines are available only
when the deployment turns them on.
After connecting, wait for the run to complete before testing answers. The Sources guide explains run statuses and what to do when a document fails.
4. Ask a Question
Open the product’s test or chat experience and ask a question that your source content answers.
What does our onboarding policy say about probation periods?Review the answer and its source citations. If a result is missing or unexpected, check the project and the source permissions before expanding access.
If you don't see citations, make sure your sources contain the relevant content and indexing has completed. Large documents can take a few minutes to process.
5. Embed the Widget (Optional)
To add Pragence to your own website:
Follow Embed the widget to generate the snippet for your project and add it to your site.
Use the snippet generated for your deployment and project; see Embed the widget. Keep secret API credentials off public pages.
Next Steps
-
Continue Knowledge onboarding or Admissions onboarding
-
Read Support and change management for versions, handoffs and rollback
-
Read Core Concepts to understand how Pragence works
-
Configure team sign-in for your organization
-
Explore the API to build custom integrations
-
See Deployment options for self-hosting