# Migration Guide ### Important Dates & Timeline | Date | Milestone | | ------------------ | ---------------------------------------------------------- | | **April 16, 2025** | Data export functionality available | | **April 23, 2025** | Dashworks API discontinued | | **July 16, 2025** | Logins disabled for Dashworks web application and Slackbot | ### What's Happening As announced in our [blog post](https://www.dashworks.ai/blog/dashworks-is-joining-forces-with-hubspot), Dashworks has been acquired by HubSpot. As our team focuses on integrating our technology into the HubSpot platform, the standalone Dashworks service will be sunset according to the timeline above. * No new sign-ups will be accepted for Dashworks web application or Slackbot as of April 16, 2025 * Existing customers will maintain full access until July 16, 2025 * All customers will receive prorated refunds based on the last date their workspace is active ### Exporting Your Data We've created straightforward processes to help you export your valuable data from Dashworks. You can request exports anytime between April 16 and July 16, 2025. #### For Workspace Administrators As a Workspace Admin, you can export all workspace-level data by following these steps: 1. Go to [Dashworks > Settings > Workspace > General](https://web.dashworks.ai/admin/appearance) 2. Click Request under **Workspace data export**. The data export will typically be available within 30 minutes. 3. You'll receive an email with download instructions when your export is ready. **What's included in the user data export:**
Workspace Bookmarks | Field Name | Data Type | Description | | ---------- | --------- | --------------------------------- | | title | `string` | The display name of the bookmark. | | link | `string` | The URL the bookmark points to. |
App connections | Field Name | Data Type | Description | | -------------- | --------- | -------------------------------------------------------------------------------------------------------- | | app\_name | `string` | The name of the connected application (e.g., Google Drive, Slack). | | user\_email | `string` | The email address of the user within the Dashworks system. | | type | `string` | Indicates if the connection is for the entire organization ('org') or an individual user ('individual'). | | account\_email | `string` | The email address used to log in to the connected application. |
Files | Field Name | Data Type | Description | | ------------- | ----------------- | ---------------------------------------------------- | | author\_email | `string` | The email address of the user who uploaded the file. | | link | `string` | A direct link or URL to access the file. | | title | `string` | The name or title of the file. | | created\_at | `ISO 8601 string` | The date and time when the file was created. |
Answers | Field Name | Data Type | Description | | ------------- | ----------------- | ------------------------------------------------------ | | title | `string` | The title or question associated with the Answer. | | content | `string` | The body or text content of the Answer. | | created\_at | `ISO 8601 string` | The date and time when the Answer was first created. | | modified\_at | `ISO 8601 string` | The date and time when the Answer was last updated. | | author\_email | `string` | The email address of the user who authored the Answer. |
Workspace Bots | Field Name | Data Type | Description | | ----------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | bot\_id | `string` | A unique identifier for the bot within Dashworks. | | bot\_name | `string` | The display name of the bot. | | icon | `string` | URL or identifier for the bot's avatar/icon image. | | description | `string` | A brief summary of the bot's purpose or capabilities. | | model | `string` | The specific Large Language Model (LLM) powering the bot (e.g., 'gpt-4', 'claude-3'). | | sources | `list[dict]` | A list of data sources the bot can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. | | is\_managed | `boolean` | Indicates if the bot is managed by Dashworks administrators (`true`) or potentially user-created (`false`). | | admin\_emails | `list[string]` | A list of email addresses of users who have administrative control over this bot. | | instructions | `string` | Custom instructions or guidelines provided to the bot to influence its behavior and responses. | | creator\_email | `string` | The email address of the user who originally created the bot. | | created\_at | `ISO 8601 string` | The date and time when the bot was created. | | learned\_feedback | `list[string]` | Instructions learned from feedback provided to the bot. |
Slack Channels | Field Name | Data Type | Description | | ------------------------- | --------- | --------------------------------------------------------------------------------------------------------- | | channel\_name | `string` | The name of the Slack channel where the bot integration is active (e.g., `#general`, `#support`). | | bot\_id | `string` | The unique identifier (`bot_id`) of the Dashworks Bot assigned to this Slack channel integration. | | reply\_only\_when\_tagged | `boolean` | If `true`, the bot will only respond in the channel when explicitly tagged (e.g., `@DashworksBot`). | | acknowledge\_question | `boolean` | If `true`, the bot may send an initial message acknowledging it received the question before answering. | | confidence\_threshold | `integer` | A percentage (0-100) representing the minimum confidence level required for the bot to attempt an answer. | | fallback\_message | `string` | The message displayed by the bot when it cannot answer or its confidence is below the threshold. | | create\_draft | `boolean` | If `true`, the bot's response will be generated as a draft in Slack for review before sending. |
Org-wide Workflows | Field Name | Data Type | Description | | -------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | `string` | The display name of the workflow. | | description | `string` | A brief summary of what the workflow does. | | prompt | `string` | The core instructions or prompt text that defines the workflow's task for the LLM. | | sources | `list[dict]` | A list of data sources the workflow can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. | | model | `string` | The specific Large Language Model (LLM) used by the workflow (e.g., 'gpt-4', 'claude-3'). | | creator\_email | `string` | The email address of the user who created the workflow. | | created\_at | `ISO 8601 string` | The date and time when the workflow was created. |
Workspace General Settings | Field Name | Data Type | Description | | ----------------- | --------- | ----------------------------------------------------------------------- | | company\_name | `string` | The name of the organization using Dashworks. | | logo | `string` | A URL pointing to the company's logo image file. | | background\_image | `string` | A URL pointing to the custom background image for the workspace. | | background\_color | `string` | The HEX color code used for the workspace background (e.g., `#FFFFFF`). |
Workspace AI Controls | Field Name | Data Type | Description | | ------------- | --------- | -------------------------------------------------------------------------------------------------------------- | | instructions | `string` | Global instructions applied to all AI interactions within the workspace, guiding overall AI behavior. | | text\_filters | `string` | A comma-separated list of keywords or phrases that the AI should avoid or filter out in its responses. | | disclaimer | `string` | A standard disclaimer message that may be appended to AI-generated content within the workspace. | | model | `string` | The default Large Language Model (LLM) used across the workspace unless overridden by specific bots/workflows. |
Workspace Members | Field Name | Data Type | Description | | ---------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------- | | name | `string` | The full name of the user. | | email | `string` | The user's primary email address used for login and identification within Dashworks. | | role | `string` | The user's permission level within the workspace. Typically 'admin' (full access) or 'member' (standard access). | | status | `string` | The current state of the user's account: 'signed\_up' (active), 'provisioned' (invited but not yet active), 'blocked' (access revoked). |
**Need to delete your workspace?** You can request this by going to [Dashworks > Settings > Workspace > General](https://web.dashworks.ai/admin/appearance) as well. Once deleted, the workspace and all associated data will be permanently removed from our systems. #### For Individual Users Individual users can export their personal data directly from the Dashworks interface: 1. Go to [Dashworks > Settings > Personal > General](https://web.dashworks.ai/my-settings) 2. Click Request under **Personal data export**. The data export will typically be available within 30 minutes. 3. You'll receive an email with download instructions when your export is ready. **What's included in the user data export:**
Private Bots | Field Name | Data Type | Description | | -------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | bot\_id | `string` | A unique identifier for the bot within Dashworks. | | bot\_name | `string` | The display name of the bot. | | icon | `string` | URL or identifier for the bot's avatar/icon image. | | description | `string` | A brief summary of the bot's purpose or capabilities. | | model | `string` | The specific Large Language Model (LLM) powering the bot (e.g., 'gpt-4', 'claude-3'). | | sources | `list[dict]` | A list of data sources the bot can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. | | is\_managed | `boolean` | Indicates if the bot is managed by Dashworks administrators (`true`) or potentially user-created (`false`). | | admin\_emails | `list[string]` | A list of email addresses of users who have administrative control over this bot. | | instructions | `string` | Custom instructions or guidelines provided to the bot to influence its behavior and responses. | | creator\_email | `string` | The email address of the user who originally created the bot. | | created\_at | `ISO 8601 string` | The date and time when the bot was created. |
Private Workflows | Field Name | Data Type | Description | | -------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | `string` | The display name of the workflow. | | description | `string` | A brief summary of what the workflow does. | | prompt | `string` | The core instructions or prompt text that defines the workflow's task for the LLM. | | sources | `list[dict]` | A list of data sources the workflow can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. | | model | `string` | The specific Large Language Model (LLM) used by the workflow (e.g., 'gpt-4', 'claude-3'). | | creator\_email | `string` | The email address of the user who created the workflow. | | created\_at | `ISO 8601 string` | The date and time when the workflow was created. |
App connections | Field Name | Data Type | Description | | -------------- | --------- | -------------------------------------------------------------------------------------------------------- | | app\_name | `string` | The name of the connected application (e.g., Google Drive, Slack). | | user\_email | `string` | The email address of the user within the Dashworks system. | | type | `string` | Indicates if the connection is for the entire organization ('org') or an individual user ('individual'). | | account\_email | `string` | The email address used to log in to the connected application. |
Topics | Field Name | Data Type | Description | | ----------- | ----------------- | ----------------------------------------------------------------------------------------------------------- | | title | `string` | The title or name assigned to this Dashworks Topic. | | created\_at | `ISO 8601 string` | The date and time when the Topic was initially created. | | messages | `list[Message]` | An ordered list of messages exchanged within the Topic. See the "Messages" table below for details. | | visibility | `string` | Controls who can view the Topic: 'private' (only creator), 'workspace' (all members), 'anyone\_with\_link'. | ### Messages (within a Topic) | Field Name | Data Type | Description | | -------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | role | `string` | Indicates who sent the message: 'User' or 'Dashworks'. | | content | `string` | The textual content of the message. | | attachments | `list[string]` | A list of the titles of any files attached to this specific message. These files are linked from the main "Files" data structure. | | sources | `list[dict]` | A list of data sources cited or used to generate Dashworks’ response. Each dictionary contains: `app_name` (string), `title` (string), `url` (string), `modified_at` (ISO 8601 string). | | bot\_id | `string` | The unique identifier (`bot_id`) of the Org-wide Bot that was tagged or generated this message, if applicable. Null or absent otherwise. | | deep\_research | `boolean` | Indicates whether the "deep research" mode was used by Dashworks to generate this specific message (`true` or `false`). |
**Important notes:** * You may only request one data export per user account * Exports will be available for download for 7 days after processing * If you request account deletion, you'll no longer be able to log into Dashworks ### Enterprise Customer Support Our enterprise customers will receive dedicated migration support: * Schedule a personalized migration consultation using our [Calendly link](https://calendly.com/prasad-kawthekar/30m) * Get tailored recommendations for alternative solutions based on your specific use case * Receive priority support for data export and transition questions We understand this transition represents a significant change for your team. We're committed to making it as smooth as possible. ### Frequently Asked Questions **Q: Will I receive a refund for my subscription?** A: Yes, all customers will receive prorated refunds for any prepaid amounts based on the on the last date their workspace is active. **Q: What happens to my data after July 16?** A: All customer data will be securely deleted from Dashworks systems within 30 days after the sunset date, in accordance with our data retention policies. **Q: How large will my export files be?** A: This depends on your usage. Most exports will be under 10GB, but high-usage accounts may have larger exports. **Q: Can I still access support during the transition?** A: Absolutely! Our support team will be available through the entire transition period. For questions, please contact . Thank you for being part of the Dashworks journey. We're excited to bring even more powerful capabilities to you through our integration with HubSpot. # Introduction Dashworks helps you quickly find answers to your team's internal questions with real-time AI-powered search across all your work apps and knowledge bases. Here you’ll find guides on setup and how to use the platform. Please reach out to the Dashworks team at or via the in app support chat for any questions or feedback! {% hint style="info" %} Want to jump right in to setting up Dashworks? Check out our [quick start page](/get-started/quick-start)! {% endhint %} {% embed url="" %} # Quick Start ## 1. Add Knowledge Once you're [signed up to Dashworks](https://web.dashworks.ai/signup), you can connect your apps, upload files, and add FAQs. {% content-ref url="/pages/gHX8PqnXjHtWWhAtxRMt" %} [Connect Apps](/knowledge/connect-apps) {% endcontent-ref %} ## 2. Ask Questions Learn how to use Dashworks for your use case. {% content-ref url="/pages/hmSDBJKvzLcNYHFTDDIT" %} [Sales](/use-cases/sales) {% endcontent-ref %} {% content-ref url="/pages/Mma3NnK8NN9w37lLFVQM" %} [Customer Support](/use-cases/customer-support) {% endcontent-ref %} {% content-ref url="/pages/W1qtXiO5nzI3w7gezLiw" %} [Engineering](/use-cases/engineering) {% endcontent-ref %} {% content-ref url="/pages/CnZ06Ivdgw3sjQXu7kM5" %} [Product Management](/use-cases/product-management) {% endcontent-ref %} ## 3. Add Slackbot Invite the Dashworks Slackbot to your Slack to automatically answer questions asked in channels. {% content-ref url="/pages/bRkaQylZkKCrMpSaIxgk" %} [Setup Bots](/bots/setup-bots) {% endcontent-ref %} {% content-ref url="/pages/l2ucS72EultlYzQQK5NH" %} [Slackbot](/surfaces/slackbot) {% endcontent-ref %} ## 4. Customize Dashworks Add Instructions and create custom bots to teach Dashworks how to respond and prioritize sources for different use cases. {% content-ref url="/pages/PQWVXYkTDoEjMgl0PwIA" %} [Instructions](/optimize/instructions) {% endcontent-ref %} {% content-ref url="/pages/qJFTk8FE1F65nuDfeyBk" %} [Custom Bots](/bots/custom-bots) {% endcontent-ref %} # Connect Apps Dashworks integrates with dozens of work apps. Connect all the apps you use so it can search for the relevant information when answering your questions. Dashworks mirrors all access control permissions from your connected applications, ensuring you and your team members can only search information that you already have access to.
Asana **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches tasks.
Azure DevOps **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches code, work items and wikis.
BambooHR **Setup** * *Auth type*: `Org-wide` * Requires "Company Administrator" role with the ability to create an API token. **Search** * *Search type*: `Limited sync` * Searches employee name, email, title, department, location, and manager name for active employees.
Bitbucket **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches code.
Box **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches files, folders and bookmarks.
Canva **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches designs and brand templates.
Coda **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches document titles. Cannot search document content. You can export documents as PDFs and[ import them as a file](/knowledge/other-sources) to search their content.
Confluence **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches pages and blogs.
Darwinbox **Setup** * *Auth type*: `Org-wide` **Search** * *Search type*: `Limited sync` * Searches employee name, email, title, department, location, and manager name for active employees.
Document360 **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches project articles.
Docusign **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches envelopes.
Dropbox **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches files, folders, and Paper docs.
Figma **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches Figma design and FigJam files.
Freshdesk **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches tickets, contacts, companies and solution articles.
Freshservice **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches tickets and solution articles.
Front **Setup** * *Auth type*: `Individual` * Personal OAuth connection. Requires "Administrator" role. **Search** * *Search type*: `Real-time` * Searches conversations.
GitBook **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches documents.
GitHub **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches code, issues, pull requests, and repos, from repositories owned by the user or the organizations that they're a part of.
GitLab **Setup** * *Auth type*: `Individual, Org-wide` * Personal OAuth connection for Cloud (GitLab.com). Requires "Administrator" role for Org connection (GitLab Self-managed). **Search** * *Search type*: `Real-time` * Searches code, issues, merge requests, milestones, projects, and wikis from groups they're a part of.
Gmail **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Super Admin" role for Org connection with Delegated Access. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches emails from all inboxes except Spam and Trash folders.
Gong **Setup** * *Auth type*: `Individual` * Personal OAuth connection (required admin permission). **Search** * *Search type*: `Real-time` * Searches call recordings and transcripts.
Google Calendar **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Super Admin" role for Org connection with Delegated Access. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches events across your primary calendar. It cannot search non-primary calendars yet.
Google Drive **Setup** * *Auth type*: `Individual` * Requires "Super Admin" role for Org connection with Delegated Access. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches files of various formats such as docs, slides, sheets, PDFs, and more.
Google Sites **Setup** * *Auth type*: `Org-wide` * Requires export of Google Site: 1. Go to [Google Drive](https://drive.google.com/) and create a top-level My Drive folder to export the site from 2. Move or add the new Google Site you want to export to the top-level folder created for the export (alternatively you can add the site to multiple folders - see [Add a site to multiple Google Drive folders](https://www.steegle.com/google-products/google-drive-faq/file-multiple-folders)). 3. Go to [Google Takeout](https://takeout.google.com/) at [takeout.google.com](https://takeout.google.com/). 4. Under the Select data to include use the Deselect all option. 5. Scroll down to the Drive section and then check/tick to include. 6. Use the All Drive data included option and then Deselect all. 7. Select (check/tick) the folder created for the export and use the OK button. 8. Scroll down and use the Next step button. 9. Choose your Customise archive format (in Export type you can schedule exports every 2 months for a year if you want an export every 2 months). 10. Use the Create archive button and Google Takeout will notify you when your export is ready. #### Notes: * Takeout will only allow you to select top-level My Drive folders to export, so the sites you want to export need to be in one of those folders. * You can only use Takeout on sites in My Drive: if the site you want to export is on a Shared drive you cannot export from a shared drive and need to move the site to a top-level My Drive folder. Warning: Moving the site from the Shared drive to My Drive will unpublish the site. * You can use Takeout to export every 2 months so you can use this as a very infrequent backup of your new Google Sites. **Search** * *Search type*: `Full sync` * Searches pages.
Guru **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Search cards, collections, folders, and templates.
Gusto **Setup** * *Auth type*: `Org-wide` * Requires "Full Administrative" permission. **Search** * *Search type*: `Real-time` * Searches employee name, email, title, department, location, and manager name for active employees.
Helpjuice **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Administrator" role. **Search** * *Search type*: `Real-time` * Searches articles.
Help Scout **Setup** * *Auth type*: `Individual` * Personal API key and OAuth connection. **Search** * *Search type*: `Real-time` * Searches articles and conversations.
Highspot **Setup** * *Auth type*: `Individual` * Personal API key connection. Requires [API access](https://app.highspot.com/settings/company/api_access). **Search** * *Search type*: `Real-time` * Searches content and spots.
HiBob **Setup** * *Auth type*: `Org-wide` **Search** * *Search type*: `Real-time` * Searches employee name, email, title, department, location, and manager name for active employees.
HubSpot **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Search contacts, companies, deals, calls, emails, meetings, and notes.
Intercom **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches articles, contact, conversations, and tickets.
Jira **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches issues and projects.
Linear **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches issues, projects, and documents.
Lucidchart **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches Lucidchart diagrams and Lucidspark boards.
Microsoft Teams **Setup** * *Auth type*: `Individual` * Personal OAuth connection. To search messages in channels, an admin of Microsoft Teams needs to first connect the integration and grant permission on behalf of the organization. **Search** * *Search type*: `Real-time` * Searches messages.
Miro **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches boards.
Monday **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches Board Items and Updates.
Mural **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches murals, rooms and custom templates.
Notion **Setup** * *Auth type*: `Individual` * Personal OAuth connection. Requires Chrome extension. **Search** * *Search type*: `Real-time` * Searches pages.
OneDrive **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Admin" role for Org connection. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches files.
Outlook **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Admin" role for Org connection. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches emails, excluding shared and public folders.
Paylocity **Setup** * *Auth type*: `Org-wide` * Requires "Company Administrator" role. **Search** * *Search type*: `Limited sync` * Searches employee name, email, title, department, location, and manager name for active employees.
Pipedrive **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches leads, deals, products, files, organizations, and people.
Productboard **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches notes.
Quip **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches files.
Rippling **Setup** * *Auth type*: `Org-wide` * Requires all permissions under "Company Permissions" and "Employee Permissions" for API key. **Search** * *Search type*: `Limited sync` * Searches employee name, email, title, department, location, and manager name for active employees.
Salesforce **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches accounts, contacts, knowledge articles, leads, opportunities, cases, and various custom objects.
ServiceNow **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches knowledge base articles.
SharePoint **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches documents, sites, pages, lists, and list items.
Shortcut **Setup** * *Auth type*: `Individual` * Personal API key connection. **Search** * *Search type*: `Real-time` * Searches epics and stories.
Simpplr **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches intranet sites and site content.
Slab **Setup** * *Auth type*: `Org-wide` * Requires Slab Bot API token. **Search** * *Search type*: `Real-time` * Searches across topics and posts (except comments) to which the Slab Bot has access.
Slack **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches messages and files across channels and DMs. * Search will mirror the in-app filters e.g. if you've selected `Exclude automations` in Slack, then search would exclude automations as well
Smartsheet **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches sheets, dashboards, discussions, reports, attachments and folders.
Stack Overflow for Teams **Setup** * *Auth type*: `Individual, Org-wide` * API key connection. **Search** * *Search type*: `Real-time` * Searches questions, answers, and articles.
Trello **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches cards and boards.
Website **Setup** * *Auth type*: `Individual, Org-wide` **Search** * *Search type*: `Real-time` * Searches public and searchable pages from websites.
Workday **Setup** * *Auth type*: `Org-wide` * [Connection guide](https://support.tryfinch.com/hc/en-us/articles/26242318065684-Workday-Add-an-Integration-System-User) **Search** * *Search type*: `Limited sync` * Searches employee name, email, title, department, location, and manager name for active employees.
Zendesk **Setup** * *Auth type*: `Individual, Org-wide` * Requires "Admin" role for Org connection. Personal OAuth connection is also available. **Search** * *Search type*: `Real-time` * Searches tickets, articles, and posts.
Zoho CRM **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches leads, accounts, contacts, deals and events.
Zoho Projects **Setup** * *Auth type*: `Individual` * Personal OAuth connection. **Search** * *Search type*: `Real-time` * Searches tasks and projects.
# Other Sources ## Files [Admins](/faqs/user-roles) can upload files in various formats from the [Files tab](https://web.dashworks.ai/files). All workspace members can see the files, but only Admins have permission to upload or delete them. File uploads can be useful when you need Dashworks to process large files. Dashworks can handle files from connected apps (such as Google Drive and OneDrive) that are up to 10 MB. However, in the Files tab, you can upload files as large as 1 GB. If you have documents in your connected apps that exceed 10 MB, you can upload them as Files instead. ## Answers If you want to teach Dashworks to provide specific answers to questions, you can add them in the [Answers](https://web.dashworks.ai/answers) tab. When asked similar questions in the future, Dashworks will prioritize Answer matches over other content it finds in connected apps. Using Answers is an effective way to build an FAQ knowledge base for your team. If you have a list of Answers you'd like to import into Dashworks, please get in touch with for assistance. {% embed url="" %} ## Web Dashworks can search the web to surface up-to-date information from the internet. To use it, select the "Web" mode from the Dashworks input box. The web integration can be used to get the latest data, statistics, current news, and developments related to your question. For example, you can ask "Give me the latest news and updates from Acme" to get the latest news about a customer.
How is the Web mode different from AI only mode? Web mode searches the internet for real-time information and is best suited for questions that require factual answers grounded in search results from the \ \ Whereas AI only mode directly lets you interact with the underlying [AI model](/optimize/ai-model) without searching. It is faster and more creative since it is not constrained by search results, making it better suited for creative tasks, brainstorming ideas, or reformatting previous answers in the same topic using a different tone or structure.
## Connector API The Connector API allows you to seamlessly integrate custom data sources into Dashworks, enabling your organization to search and retrieve information from tools and platforms not natively supported. With this API, you can programmatically add internal tools, databases, or any other external sources to Dashworks, ensuring that your team has access to a unified knowledge base tailored to your unique needs. Whether it's syncing with your internal systems or connecting to specialized applications, the Connector API empowers you to expand Dashworks' capabilities and enhance your team's productivity. # Engineering ## **1. Debug Errors and On-Call Issues** Quickly troubleshoot failing tests, development errors, and configuration issues. **Examples:** * "What does this error message \[error message] mean in the context of \[project name]?" * "How do I resolve a failed deployment for \[environment name]?" * "What are the steps to debug a memory leak in \[specific framework]?" * "What does the log entry \[log snippet] indicate?" *** ## **2. Review and Optimize Code** Get instant feedback on code quality and learn best practices to improve code performance. **Examples:** * "Can you review this code snippet for potential issues?" * "What are the best practices for writing secure code in \[programming language]?" * "How can I optimize this SQL query for better performance?" * "What are common pitfalls in implementing \[specific algorithm]?" *** ## **3. Write SQL Queries** Find product log events, database tables, and fields, and write SQL queries based on them. **Examples:** * "Write a SQL query to find all users who signed up in the last 30 days." * "What are the column names in the \[table name] table?" * "How do I join \[table A] and \[table B] to get \[specific data]?" * "What are the most common errors in our database logs?" *** ## **4. Understand the Codebase** Quickly locate code and repositories, and get summaries of implementation decisions. **Examples:** * "What does the function \[function name] do in the \[repository name] repository?" * "Who wrote the \[specific module] and when?" * "What are the dependencies for \[specific service]?" * "Summarize the purpose of \[specific repository]." *** ## **5. Research Past Projects** Get summaries of past RFCs, initiatives, KPIs, and next steps. **Examples:** * "What were the key decisions made in the \[project name] RFC?" * "Summarize the goals and outcomes of the \[initiative name] project." * "What were the KPIs tracked for \[specific feature]?" * "What are the pending tasks for \[project name]?" *** ## **6. Find Experts in the Team** Identify team members with domain-specific knowledge for guidance on projects or issues. **Examples:** * "Who worked on the \[specific feature] implementation?" * "Who can help with debugging \[specific issue]?" * "Who has experience with \[specific framework or tool]?" *** ## **7. Troubleshoot Deployment Issues** Resolve deployment roadblocks by accessing internal documentation, runbooks, and cloud provider resources. **Examples:** * "What are the steps to deploy to \[environment name]?" * "What does the error \[error code] mean in our deployment pipeline?" * "Where can I find the runbook for \[specific service]?" * "What are the rollback procedures for \[specific deployment]?" *** ## **8. Automate Repetitive Tasks** Streamline workflows by automating common engineering tasks. **Examples:** * "Generate a boilerplate code for \[specific use case]." * "Write a script to automate \[specific task]." * "What are the steps to set up a CI/CD pipeline for \[project name]?" * "How do I configure \[specific tool] for our project?" *** ## **9. Onboard New Engineers** Help new hires ramp up quickly by providing access to documentation and key resources. **Examples:** * "What is the branching strategy for our Git repositories?" * "Where can I find the documentation for \[specific service]?" * "What are the coding standards for our team?" * "What are the key tools and technologies used in our projects?" *** ## **10. Improve Code Quality** Maintain high standards of code quality by accessing best practices and conducting code reviews. **Examples:** * "What are the best practices for writing unit tests in \[programming language]?" * "How do I refactor this code to improve readability?" * "What are common security vulnerabilities in \[specific framework]?" * "What are the guidelines for writing maintainable code?" # Customer Support ## **1. Resolve Customer Issues Faster** Quickly locate accurate information to troubleshoot and resolve customer queries. **Examples:** * "How do I reset a customer’s password?" * "What does the error message \[specific error] mean?" * "What are the steps to connect a wireless headset to its base station?" * "How do I troubleshoot a failed payment issue?" *** ## **2. Understand Product Functionality** Provide clear and accurate explanations of product features and integrations. **Examples:** * "How does feature X work in our product?" * "Can you explain how our integration with \[partner software] works?" * "What are the key differences between our pricing plans?" * "What are the known limitations of \[specific feature]?" *** ## **3. Draft Help Articles and Responses** Create detailed and user-friendly documentation to assist customers. **Examples:** * "Write a step-by-step guide for setting up \[specific feature]." * "Draft a help article for troubleshooting \[specific issue]." * "What should be included in a how-to guide for \[specific process]?" * "Summarize the key points for a FAQ about \[specific topic]." *** ## **4. Manage Customer Accounts** Access and update customer information to provide personalized support. **Examples:** * "Who is the account manager for \[customer name]?" * "What is the subscription status of \[customer email]?" * "Where can I find the past invoices for \[customer name]?" * "What are the details of the last support ticket for \[customer name]?" *** ## **5. Handle Refunds and Policy Questions** Provide accurate answers to customer inquiries about company policies. **Examples:** * "What is our refund policy for \[specific product]?" * "How does the 14-day free trial work?" * "What are the steps for processing a refund request?" * "What is our policy on subscription cancellations?" *** ## **6. Collaborate with Other Teams** Work seamlessly with engineering, sales, and product teams to resolve complex issues. **Examples:** * "What is the status of the bug reported in ticket \[ticket ID]?" * "Who can help with a technical issue related to \[specific feature]?" * "What are the upcoming product updates that might affect customers?" * "What is the escalation process for unresolved issues?" *** ## **7. Onboard New Support Agents** Help new hires ramp up quickly by providing access to training materials and resources. **Examples:** * "What are the steps for handling a refund request?" * "Where can I find the training materials for new support agents?" * "What are the most common customer issues and how do we resolve them?" * "What are the key features of our product that customers ask about?" *** ## **8. Automating Responses to FAQs** Save time by automating answers to frequently asked questions. **Examples:** * "What is the process for resetting a password?" * "How do I update my billing information?" * "What are the steps to enable two-factor authentication?" * "What is the warranty policy for \[specific product]?" # Sales ## **1. Find Sales Enablement Collateral** Quickly locate sales decks, one-pagers, and other resources to tailor pitches for prospects. **Prompt Examples:** * "Where can I find the latest sales deck for \[industry]?" * "Do we have a competitive analysis document for \[competitor]?" * "What are our key differentiators for \[specific product]?" * "Find a one-pager for \[specific feature]." *** ## **2. Prepare for Customer Calls** Get a comprehensive view of a prospect’s history and key pain points to prepare for meetings. **Prompt Examples:** * "Summarize my past communications with \[prospect name]." * "What are \[prospect name]’s key use cases and challenges?" * "What is the status of the deal with \[company name]?" * "What are the next steps for \[opportunity name]?" *** ## **3. Draft Personalized Pitches and Emails** Create tailored communication for prospects to improve engagement and conversion rates. **Prompt Examples:** * "Draft a follow-up email for \[prospect name] after our meeting." * "Write a personalized email introducing our new feature to \[prospect name]." * "Create an outbound email sequence for a product launch." * "Draft a LinkedIn message for \[prospect name] about our partnership opportunities." * "I need a \[type of email] that will tell a story about \[service] and how it has helped \[client] achieve \[goal] in a relatable and engaging way." * “Write me an email to catch up with \[contact] while including recent news about \[their company].” *** ## **4. Answer Technical Questions** Provide accurate and instant answers to technical queries during sales calls or demos. **Prompt Examples:** * "How does our product integrate with Salesforce?" * "What are the technical requirements for deploying \[specific feature]?" * "Can a customer upgrade to the Enterprise tier from the app?" * "What are the API capabilities of \[product]?" *** ## **5. Fill Out Security Questionnaires** Streamline the process of responding to RFPs and InfoSec questionnaires. **Examples:** * "Are we SOC-2 Type 2 compliant?" * "What encryption standards does our software use?" * "What is our data retention policy?" * "Provide answers to the security section of this RFP." *** ## **6. Research Prospects** Gather insights about prospects to tailor pitches and build stronger relationships. **Prompt Examples:** * "What is \[prospect company]’s annual revenue?" * "Who are the key decision-makers at \[company name]?" * "What recent news is available about \[prospect company]?" * "What are the main competitors of \[prospect company]?" *** ## **7. Handling Objections** Equip sales reps with the right information to address objections confidently. **Examples:** * "How do we compare to \[competitor] on pricing?" * "What is our policy for bulk purchase discounts?" * "What are the benefits of our product over \[competitor]?" * "How do I handle objections about implementation time?" *** ## **8. Onboard New Sales Reps** Help new hires ramp up quickly by providing access to training materials and key resources. **Examples:** * "What is the sales process for \[specific product]?" * "Where can I find training materials for new sales reps?" * "What are the most common objections and how do we handle them?" * "What are the key features of our product portfolio?" # Marketing ## **1. Create Content** Generate high-quality marketing content tailored to your audience and brand voice. **Examples:** * "Draft a blog post about the benefits of using our product for \[specific industry]." * "Write a LinkedIn post announcing our new product launch." * "Create ad copy targeting \[specific persona] with a focus on \[specific feature]." * "Generate a nurture email for a new feature launch." *** ## **2. Social Media Management** Brainstorm and draft engaging social media posts for various platforms. **Examples:** * "Write a Twitter thread about the latest trends in \[specific industry]." * "Draft an Instagram caption for our upcoming event." * “Suggest a catchy caption for my social media post about \[topic].” * "What are some creative ideas for a TikTok campaign about \[specific product]?" * "Generate hashtags for a campaign targeting \[specific audience]." *** ## **3. Market Research and Competitive Analysis** Gather insights on competitors, industry trends, and customer preferences. **Examples:** * Generate a fact sheet on \[company] and include their headcount, office locations, recent news, leadership team, and top competitors. * "What are the latest trends in digital marketing for \[specific industry]?" * "What features have our competitors recently launched?" * "Summarize customer feedback about \[specific feature]." * "What are the top-performing campaigns in \[specific industry]?" *** ## **4. Draft Marketing and Enablement Collateral** Create polished materials for campaigns, product launches, and events. **Examples:** * "What metrics can I use to demonstrate ROI from \[Feature]?" * "Write a one-pager summarizing the benefits of \[specific product]." * "Draft a press release for our new feature launch." * How can I pitch \[product] to clients in \[region]? * "Create a product comparison sheet for \[specific competitors]." * "Generate a case study based on this customer interview transcript." *** ## **5. Synthesize Customer Feedback** Analyze customer feedback to identify trends and inform marketing strategies. **Examples:** * "What are the most common pain points mentioned in customer feedback?" * "Summarize the top feature requests from last quarter." * "What are customers saying about \[specific product] in reviews?" * "What are the recurring themes in feedback from \[specific audience]?" *** ## **6. Personalized Customer Outreach** Create tailored messaging for specific customer segments or personas. **Examples:** * "Draft a personalized email for \[specific persona] about \[specific feature]." * "Write a follow-up email for attendees of our recent webinar." * "Generate a welcome email sequence for new customers." * "Create a pitch deck for \[specific audience] highlighting \[specific benefits]." *** ## **7. Event Planning and Promotion** Streamline the planning and promotion of webinars, conferences, and other events. **Examples:** * "Write an email invitation for our upcoming webinar." * "Draft a social media post promoting our presence at \[specific event]." * "What are some creative ideas for engaging attendees at \[specific event]?" * "Generate a checklist for planning a product launch event." *** ## **8. Repurposing Existing Content** Reformat and adapt existing content for different platforms and audiences. **Examples:** * "Turn this blog post into a LinkedIn article." * "Rewrite this technical whitepaper for a general audience." * "Summarize this case study into a one-pager." * "Translate this blog post into Spanish." *** ## **9. Plan High Impact Campaigns** **Examples:** * What are effective landing page ideas for a campaign targeting \[audience]? * Find me the google sheet with the social media ad performance from last quarter * What are the best-performing keywords in our recent PPC campaigns? *** ## **10. Uncover Customer Insights** **Examples:** * What are the common characteristics of our top customers? * What are the most frequently asked questions by our customers in demo calls? * Summarize customer feedback from the last quarter # Product Management ## **1. Answer Product Questions** Dashworks integrates with tools like Slack, Jira, Confluence, and Google Drive to provide instant answers to product-related queries, reducing the time spent searching for information. **Examples:** * "What are the key features of \[specific product/feature]?" * "What integrations are available for \[tool]?" * "What is the pricing structure for \[product/service]?" *** ## **2. Synthesize User Feedback** Dashworks aggregates and analyzes feedback from sources like Zendesk, Intercom, and surveys, helping product managers identify trends and prioritize features **Examples:** * "What are the top complaints from users about \[feature]?" * "Summarize customer feedback from the last quarter." * "What are the most requested features in our product roadmap?" *** ## **3. Manage and Prioritize Product Roadmaps** Dashworks pulls data from Jira, Confluence, and other project management tools to provide a unified view of roadmaps and dependencies, ensuring alignment across teams. **Examples:** * "What are the upcoming milestones for \[project]?" * How does the development of \[feature] align with our long-term company goals? * "What is the current status for \[project]?" *** ## **4. Conduct Competitive Analysis** Dashworks searches internal and external sources, such as competitor websites, news articles, and internal knowledge bases, to provide comprehensive insights. **Examples:** * "Who are the main competitors for \[product/service]?" * "What are the strengths and weaknesses of \[competitor product]?" * "What features does \[competitor] offer that we don’t?" *** ## **5. Draft and Refine Product Documentation** Dashworks assists in creating and maintaining consistent documentation, ensuring all stakeholders have access to up-to-date information. **Examples:** * "Draft an RFC for \[new feature]." * "What should be included in the release notes for \[version]?" * "Summarize the key points of the product strategy document." *** ## **6. Onboard New Team Members** Dashworks provides a centralized knowledge base, enabling new hires to quickly get up to speed by accessing relevant resources and asking questions in natural language. **Examples:** * "What is the company’s product strategy?" * "What are the key performance indicators for product managers?" * "Who are the stakeholders for \[specific project]?" *** ## 7. Research Past Projects Learn about historical projects by analyzing project updates, RFCs, and internal conversations. **Examples:** * What were the key challenges and solutions in \[project]? * What was the timeline and budget for \[project] and how did it compare to initial projections? * Who worked on \[project]? Can you give me a brief summary of the goals, timeline, and outcome? # Human Resources ## **1. Streamline Onboarding** Provide new hires with instant access to company policies, processes, and resources to ensure a smooth onboarding experience. Create a [Custom Bot](/bots/custom-bots) or [Managed Bot](/bots/managed-bots) for oversight over Dashworks answers. **Examples:** * "What are the steps to set up my company email?" * "Where can I find the employee handbook?" * "What is the process for submitting expense reports?" * "Who should I contact for help with \[specific onboarding task]?" *** ## **2. Manage Employee Policies** Quickly access and share up-to-date information on company policies and procedures. **Examples:** * "What is our remote work policy?" * "How many vacation days do employees get per year?" * "What is the process for requesting parental leave?" * "Where can I find the travel reimbursement policy?" *** ## **3. Automate Repetitive HR Tasks** Save time by automating responses to frequently asked questions and routine HR tasks. **Examples:** * "How do I update my personal information in the HR system?" * "What are the steps to enroll in the company’s health insurance plan?" * "How do I reset my password for the payroll portal?" * "What is the process for submitting a time-off request?" *** ## **4. Support Learning and Development** Provide employees with access to training materials and resources to support their growth. **Examples:** * "Where can I find training materials for \[specific skill]?" * "What are the available courses for leadership development?" * "How do I register for the upcoming \[specific training session]?" * "What are the best practices for creating a \[type of training material]?" *** ## **5. Synthesize Employee Feedback** Analyze employee feedback to identify trends and improve workplace policies. **Examples:** * "What are the most common concerns raised in employee surveys?" * "Summarize the feedback from the last all-hands meeting." * "What are the recurring themes in exit interviews?" * "What are the top suggestions for improving the onboarding process?" *** ## **6. Manage Compliance and Legal Requirements** Ensure compliance with labor laws and company policies by accessing accurate and up-to-date information. **Examples:** * "What are the legal requirements for terminating an employee in \[specific location]?" * "What is the process for conducting a workplace investigation?" * "What are the GDPR compliance requirements for employee data?" * "Where can I find the company’s anti-harassment policy?" *** ## **7. Improve Employee Engagement** Provide employees with quick answers to their questions and improve their overall experience. **Examples:** * "How do I nominate a colleague for the employee recognition program?" * "What are the benefits of the employee wellness program?" * "Where can I find resources for mental health support?" *** ## 8. **Communicate Policy Updates** **Examples:** * How do I communicate \[Policy Update] to employees? *** ## 9. Welcome New Employees **Examples:** * "What should I include in an email welcoming a new employee?" *** ## 10. Write Employee Feedback **Examples:** * Can you help me write constructive feedback for \[name] / \[role] who consistently meets deadlines but struggles with team communication? * Help me write a performance review summary for \[role]. *** ## **11. Promote Events and Activities** **Examples:** * Write an announcement for a company's annual team-building event happening today. Express excitement about seeing employees in person and highlight the main aspects of the event, such as engaging conversations, fun activities, and leadership connections. # Talent ## 1. Create Job Descriptions **Examples:** * "Write a job description for a \[specific role]." * "What are the key responsibilities for a \[specific position]?" * "What are the top skills to look for in a \[specific position]?" * Can you draft a job description for a Senior Lunar Rover Engineer, focusing on experience with autonomous navigation systems and radiation-hardened electronics? * Draft a job rec for a Martian Habitat Systems Architect, emphasizing experience in closed-loop life support systems and Martian environmental simulations. ## 2. Draft Interview Questions **Examples:** * What are good interview questions for hiring \[Specific Role]? * Generate a set of technical interview questions for a Quantum Communication Specialist position, focusing on entanglement-based data transmission in space. * Create behavioral interview questions for a Spacecraft Recycling Systems Engineer role, emphasizing problem-solving in resource-constrained environments. * Draft scenario-based interview questions for a Space Tourism Safety Officer position, addressing emergency protocols and passenger management in suborbital flights. # Legal & Compliance ## **1. Verify Compliance with Regulatory Standards** Quickly verify whether company policies and practices align with regulatory standards, saving time during audits or reviews. **Examples:** * "What are the GDPR requirements for data retention in our industry?" * "Summarize the key points of the California Consumer Privacy Act (CCPA)." * "Are our current data storage practices compliant with ISO 27001 standards?" * "What are the legal requirements for using digital signatures in \[specific country]?" *** ## **2. Find, Draft, and Review Legal Documents** Streamline the creation and review of legal documents, ensuring accuracy and compliance with company policies. **Examples:** * "Find me our NDA template for new vendors" * "What clauses should be included in a Master Service Agreement (MSA) for SaaS companies?" * "Summarize the key terms in this contract: URL." * "What are the termination conditions in our agreement with \[vendor name]?" *** ## **3. Clarify Legal and Policy Terms** Simplify complex legal jargon for better understanding by non-legal stakeholders, enabling faster decision-making. **Examples:** * "What does 'force majeure' mean in the context of our contracts?" * "Explain the difference between 'indemnity' and 'liability' clauses." * "What is the purpose of a 'governing law' clause in contracts?" *** ## **4. Manage Compliance Documentation** Centralize and streamline access to compliance-related documents, ensuring teams always have the latest information. **Examples:** * "Where can I find the latest version of our data privacy policy?" * "List some compliance reports submitted in the last quarter." * "What are the key updates in our latest compliance audit report?" *** ## **5. Generate Compliance Reports** Automate the creation of detailed compliance reports, saving hours of manual effort. **Examples:** * "Generate a compliance report for our recent ISO 27001 audit." * "What are the key findings from our last GDPR compliance review?" * "Summarize some compliance risks identified in the last quarter." *** ## **6. Research Industry-Specific Regulations** Stay updated on industry-specific regulations to ensure the company remains compliant as laws evolve. **Examples:** * "What are the HIPAA requirements for data encryption in healthcare?" * "What are the legal implications of using AI in financial services?" * "What are the compliance requirements for cross-border data transfers in \[specific region]?" *** ## **7. Answer Security and Privacy Questions** Address security and privacy concerns raised by internal teams or external stakeholders, ensuring transparency and trust. **Examples:** * "What are the access control policies for sensitive customer data?" * "What measures are in place to prevent data leakage?" *** ## **8. Support Contract Negotiations** Provide quick insights during contract negotiations to support informed decision-making. **Examples:** * "What are the standard payment terms in our vendor contracts?" * "What liability caps do we typically agree to in SaaS agreements?" * "What are the risks of agreeing to unlimited liability in the attached contract?" *** ## **9. Train and Onboard Legal Teams** Accelerate onboarding and training for new legal team members by providing instant access to relevant resources. **Examples:** * "What are the key compliance policies new hires should know?" * "Create a training guide for understanding our contract review process." * "What are the most common security questions asked by our customers?" *** ## **10. Handle Incident Response** Ensure quick and accurate responses during compliance incidents, minimizing potential legal and reputational risks. **Examples:** * "What is our protocol for reporting a data breach?" * "Who is responsible for notifying regulators in case of a compliance violation?" * "What are the legal implications of a data breach under GDPR?" # Custom Bots Dashworks lets you create custom bots in Dashworks for different use cases, for instance: * `Support Bot` that searches the help center, past tickets, and product wikis. * `RFP Responder` that searches previously completed RFPs and questionnaires. * `Onboarding Buddy` that search HR policies and onboarding docs, and tags the HR team in its response if there's no suitable documentation. {% content-ref url="/pages/bRkaQylZkKCrMpSaIxgk" %} [Setup Bots](/bots/setup-bots) {% endcontent-ref %} {% content-ref url="/pages/M3N6i6R9HqGuQJexiCwQ" %} [Managed Bots](/bots/managed-bots) {% endcontent-ref %} # Setup Bots Bots in Dashworks use your connected apps to answer user questions. Follow these steps to set up bots quickly and effectively: ## **Step 1: Add Bot Connections** 1. Go to the [App Store](https://web.dashworks.ai/integrations). 2. Find the app connection you want the bot to use. 3. Open the app connection settings and toggle **"Mark as Bot Connection"**. * This allows the bot to search the app to answer questions. * All other connections remain private and inaccessible to the bot.
How do search permissions work for bot connections? Search permissions for bot connections depend on whether the connection is [Org or Individual](/faqs/org-vs-individual): * **Individual connection**: The account that you're logged in to the app that you're connecting determines the bot's search permissions. For instance, if you authenticate Zendesk as an Individual connection while you're logged in to Zendesk with and then mark it as a Bot connection, then the Bot can search the content that has access to in Zendesk. * **Org connection**: The account that you're logged in to Dashworks determines the bot's search permissions. For instance, if you authenticate Zendesk as an Org connection while you're logged in to Dashworks with , and then mark it as a Bot connection, then the Bot can search the content that has access to in Zendesk.
Which account should I use to setup bot connections? It's recommended to use a non-user account (ex. or ) for bot connections. This lets you restrict the information bots can search to the sources that have been shared with this account. Ensure the bot connection account has sufficient permissions to access all relevant documents, channels, projects, etc. needed to answer user questions effectively. We do not recommend using your personal account as a bot connection as this may reveal information that's private to you to bot users (ex. files in "My Drive" of Google Drive).
## **Step 2: Create a Bot** 1. Go to the [Bots page](https://web.dashworks.ai/bots). 2. Click **"Create New Bot"**. 3. Customize the bot: * **Name**: Give your bot a clear and descriptive name. * **Knowledge Sources**: Select the apps, files, or answers that the bot should search. * **Instructions**: Add any specific guidelines for how the bot should respond. * **Bot Admins and Managed Bot**: Learn more about when and how to use managed bots [here](https://support.dashworks.ai/bots/managed-bots). ## **Step 3: Test Your Bot** Use the bot in the Dashworks web app by tagging it in the input box (e.g., `@BotName`). ## **Step 4: Setup the Slackbot (Optional)** If you want to use the bot to answer questions in Slack channels, set up the [Dashworks Slackbot](/surfaces/slackbot): 1. Add a Slack connection in the App Store. 2. Mark it as a **Bot connection** and the **Primary Slackbot Connection.** 3. Invite the Slackbot to a Slack channel by typing `/invite @Dashworks` in the channel. 4. From the Slack Channels tab of the [Bots page](https://web.dashworks.ai/bots) select the Slack channel to change its bot. # Managed Bots Managed Bots lets you combine Dashworks answers with the expertise of your team's subject matter experts (SMEs), allowing for: * Real-time notifications to SMEs when the bot is tagged * Expert oversight and intervention when needed * Private conversations for sensitive topics Using bots in Slack channels with the [Dashworks Slackbot](/surfaces/slackbot) is the way to go for most use cases that require a combination of Dashworks answers and expert oversight. Managed Bots on the web app can be useful in the following scenarios: * Questions from users may include sensitive or private info, such as HR-related questions about benefits, compensation, or policies * You want to reduce the notification overload for everyone in Slack channels * Your team doesn't use Slack Here are some example use cases for managed bots: * **HR Support**: Bot Admins are the HR team, and knowledge sources are the existing HR knowledge base, such as a space in Confluence, drive in Google Drive, or teamspace in Notion. * **IT Support**: Bot Admins are the IT team, and knowledge sources are the IT knowledge base or historical tickets. * **Product Support:** Bot Admins are product managers or engineering leads, and knowledge sources are product wikis, support help center, Slack conversations, and project management tool. * **Sales Enablement:** Bot Admins are the sales enablement team or sales leaders, and knowledge sources are SFDC, Slack conversations, and enablement KB in Drive or HighSpot / Seismic. ## Setting Up Managed Bots 1. Go to the [App Store](https://web.dashworks.ai/integrations) and mark [relevant app connections as "Bot Connections"](https://support.dashworks.ai/bots/setup-bots). 2. Create a new bot from [Bots page](https://web.dashworks.ai/bots) and specify it as a Managed Bot during setup. 3. Designate the subject matter experts who will oversee the bot as Bot Admins. ## How to Use Managed Bots ### **For End Users**: * Tag the bot with your question in the input box using "@BotName" * Receive instant AI-powered answers * The SME will be instantly notified in real-time and provide additional context on the topic if necessary. You can also tag them in the topic using "@AdminName". ### **For Bot Admins**: * Receive notifications when the bot is tagged * Monitor bot interactions in real-time * Step in to provide additional context or help when necessary * Resolve unanswered queries as needed # Slackbot As your team grows, the number of Slack channels for employee questions also increases (like #sales-questions, #technical-support, and #ask-product). The volume of weekly questions can be overwhelming for channel managers, leading to long wait times for employees seeking help. The Dashworks Slackbot can automatically address up to 87% of questions asked in Slack. This allows channel managers to concentrate on more important matters, while providing instant answers to unblock the rest of the team. ## 1. Slackbot in Channels Once you've [set up Bots](/bots/setup-bots), you can invite the Dashworks Slackbot to a Slack channel: Invite the Slackbot "APP" to the channel by typing "/invite @Dashworks." This will allow the Slackbot to respond to questions asked in the channel. Once the Slackbot has been added, the Dashworks Slackbot will automatically detect and respond to questions asked in new threads.
How can I customize the Slackbot? You can customize the Slackbot from the [Bots page](https://web.dashworks.ai/bots). Create a new Bot and specify the sources to search, AI model to use, and instructions to follow. Then, switch over to the Slack Channels tab on the same page and select the Slack channel to specify the Bot from the dropdown.
How does the Slackbot decide which questions to automatically respond to? The Slackbot will automatically respond to all messages that contain a question, as long as question isn't directed towards a specific user or group. Additionally, if you have [selected "Reply only if answer found"](https://share.cleanshot.com/g7WxG6WPx0r1G1DNTn7l), Dashworks will ignore questions that it can't find an exact answer to.
Can I stop the Slackbot from automatically responding to questions? By default, the Slackbot will automatically respond to new questions asked in Slack channels. You can disable this by [unselecting the Autorespond setting](https://share.cleanshot.com/m8f5HKYrN2Bvv8H2nfc8). If you disable auto-responding, you can still trigger the Slackbot by tagging it in your question with "@Dashworks".
Can I ask follow up questions to the Slackbot in a thread? Yes, you can ask follow up questions to the Slackbot by tagging it with "@Dashworks" in your question. Note that auto-responding doesn't work inside threads to reduce noise.
What are the "Yes / No" buttons and the "Train Dash AI" buttons for? Click the "Yes" button to mark the question as resolved. Once resolved, Dashworks will add a :white\_check\_mark: emoji to the parent message in the thread to indicate it doesn't require a follow up. Use the Train Dash AI buttons to give [feedback to Dashworks](/optimize/feedback) to improve its responses.
## 2. Slackbot in DMs If you have questions that you don't want to ask in a public or shared channel, you can use the Slackbot to send a direct message (DM) instead. This way, you can ask questions privately without sharing them with your team.\ \ To access your DMs in Slack, go to the 'Apps' section in your individual Slack instance and find the Dashworks app. You don't need to tag anyone in your message to get a response from the Slackbot. All responses will be private, and you can access all the information you have permission to see in your company's knowledge base.\ \ To start a DM, open a direct message with the Slackbot, just like you would with a teammate, and ask any work-related question.
## 3. Other ways to use the Slackbot If you prefer not to have Dashworks respond automatically to questions in the channel, you can adjust this setting on the [Bots tab](https://web.dashworks.ai/bots). Here are some other ways you can also use Dashworks in channels: {% tabs %} {% tab title="Slack Workflows" %} Dashworks can be combined with [Slack Workflows](https://slack.com/features/workflow-automation) for powerful customization, such as structured form inputs, or trigger multiple actions after a question is asked in the channel. Here are the steps to creating a workflow: 1. Go to the "Integrations" tab on the channel's top and select "Add a Workflow". 2. Select "Create Workflow' and then "From a link in Slack". 3. As the first step in this workflow, select "Forms" -> "Collect info in a form" on the right side. You can customize this form per your requirements. Include a "Long Answer" field with a descriptive name, such as "What is your question?". This field will send the user's question to Dashworks. Mark this step as required. 4. As the second step, select "Messages" -> "Send a message to a channel". Select the channel where you want to add the Slackbot. Under "Add a message," add "`@user-who-asked-the-question: @dashworks {user question}`", replacing \[Variable X] with the appropriate variable by clicking "Insert variable". 5. Add any additional actions you want to take, then publish the workflow. 6. Copy the link to the workflow and add it as a bookmark in the Slack channel. 7. Users will be directed to the form created in Step 3 when they click on the bookmark. After submitting the form, a new thread will be created with the question, and Dashworks will respond. {% endtab %} {% tab title="Tag @Dashworks" %} You can trigger a response from Dashworks by tagging it with "@Dashworks" in your question. {% endtab %} {% tab title=""Ask Dash AI" menu" %} You can also trigger the Dashworks Slackbot when another team member asks a question by selecting "Ask Dash AI" from the message actions menu.
{% endtab %} {% endtabs %} # Chrome Extension The Dashworks Chrome extension simplifies access to Dashworks in one click. Once installed, you can access Dashworks in a few different ways from your browser: 1. Open Dashworks as a side panel on any page 2. Use Dashworks from your new tab page 3. Ask Dashworks from your address bar 4. Click the Dashworks icon in your browser toolbar {% embed url="" %} ## Side Panel Your can access Dashworks side-by-side on any page in Chrome. This makes it easier than ever to get the answers you need, right where you’re working. Here are some example workflows it can help with: 1. **🛃 Reply to support tickets**: Find answers to respond to support tickets in Salesforce Cases, Intercom, or Zendesk, without leaving the page. 2. **📧 Draft email replies**: Quickly create draft responses while in Gmail or Outlook. 3. **✍️ Create draft documents**: Start drafting a doc while working in Google Docs or Confluence.
## New tab page Once the extension is installed, simply open a new tab to access Dashworks. You can configure this setting [here](https://web.dashworks.ai/browser-extension). You can customize the new tab page with bookmarks and a background image. Bookmarks allow you to easily access your most-visited websites in one click. There are two types of bookmarks: * Personal Bookmarks: specific to your own Dashworks homepage and are only visible to you. * Company Bookmarks: created by your Dashworks admin.
Can I keep the Chrome extension but disable the new tab page? Yes, absolutely. Just toggle the setting to Set Dashworks as your homepage [here](https://web.dashworks.ai/browser-extension).
## Address bar Additionally, you can also use Dashworks from the address bar by starting your query with "dash \" and pressing enter. {% embed url="" %} # Improve Answers ### Step 1: Check your app connections Make sure you've connected all the applications for Dashworks to search from the [App Store](https://web.dashworks.ai/integrations), and the [correct accounts for each of the applications](https://share.cleanshot.com/75P8HrphxJxvvkdyhz75). ### Step 2: Check content permissions within app connections Please read [this section](https://support.dashworks.ai/bots/search-permissions) to ensure you're familiar with how search permissions work across surfaces. Confirm if the app account you've connected to Dashworks has access to the required file, folder, project, channel, or other specific content that you want it to search. This is specially important while using the Slackbot or Bots, since they rely on the permissions of the app connections for the Bot Account. Please review [this section](https://support.dashworks.ai/bots/setup-bot-account#id-5.-connect-bot-company.com-to-the-apps-it-should-search) for details on how to configure the Bot Account with appropriate search access. A rule of thumb here is that the bot can only search for information in an app that you can find after logging in to that app using the app connection email. Here's an example: Say you have connected the Bot Account to a Google Drive account with the email . Now login to the Google Drive web app ([drive.google.com](https://drive.google.com/)) with the same email. Anything you can find in web app will also be searchable in Dashworks, as long as it is one of the supported object types. If you can't find something while logged in to the app itself using the connection email, then Dashworks won't have the permissions to search for it either. The supported object types for each application are listed [here](https://support.dashworks.ai/knowledge/apps). ### Step 3: Check if it's a known limitation Here are some of the known limitations of Dashworks that we're working hard to improve: 1. **Questions with search filters**: Dashworks doesn't reliably understand search filters yet. For instance, for the question `give me any unread emails from John from last month`, you'd want Dashworks to use the Gmail search query `from:john is:unread older_than:1m`. However, Dashworks cannot always apply such filters accurately. Other examples: `summarize the last thread from Macy in the #general channel`, `what's on my calendar for next week?` 2. **Multi-hop searches**: When you're looking for information manually, sometimes you might decide to do a search and then based on what you find in one of the documents of the search results, do another search with a different query. For instance, for the question `can you help me resolve support ticket X`, you would first search for the ticket X, and then based on the contents of the ticket perform another search to find information related to it. These kinds of two-hop (or more generally, multi-hop) searches aren't supported yet. Dashworks instead runs multiple searches parallelly but in a single hop. 3. **Analytical questions**: Dashworks cannot reliably perform numerical calculations or analysis on spreadsheets or other data just yet. Example: `what was the total revenue closed in North America region in Q2?`. ### Step 4: Rephrase your question and apply filters Here are some suggestions for how to improve your questions: * **Include all relevant keywords**: Dashworks uses keywords and phrases related to your question when searching in your connected apps. For example, if you ask, `what is our refund policy`, it will look for terms like `refund policy`, `customer refunds`, or `billing policy`. Adding more relevant keywords to your question increases the likelihood that it will find the correct content. * **Reduce ambiguity**: The more specific and well written your question is, the better response Dashworks can provide. Phrase your question as a well-formed sentence instead of simply entering keywords like we're used to in Google.\ For example, ask, `Can you give me a history of the deal with Acme?` instead of just querying `Acme`. As another example, instead of asking something like `what's our deck?`, make it more specific like `can you find me our latest sales deck from 2024?`. \ A helpful analogy here is to think of Dashworks as a new intern who's joined your team. The more context you can provide in your question and clearly specify the task, the better the performance can be. * **Tell Dashworks which app to search:** You can include the app name, file name, and file type in your question. These signals help Dashworks focus its search and surface the correct results. For instance, you can ask, `Give me a link to the RFC for the slack autoresponder. It's a notion doc I saw in Slack last week.` You can also specify apps to search from the Apps dropdown in the [input box on the web app](https://share.cleanshot.com/3BkJzmQJ1QFBzG2cw7nt), or by [configuring bots](https://share.cleanshot.com/QqC84cQskZ7xyySB3HNV) on the [Bots page](https://support.dashworks.ai/optimize/www.web.dashworks.ai/bots).
* **Specify the type of answer in the question**: You can ask Dashworks to return links to docs, summarize docs, write emails, write blog posts, and more. For instance, if you ask Dashworks `summary of the latest sales deck` it will return a summary of the deck, and if you ask it `link to the latest sales deck` it will return a URL for it instead. ### Step 5: Add Instructions Instructions are the best way to teach Dashworks where to look for specific information, what information to prioritize, and what to ignore. Learn more about adding [Instructions here](/optimize/instructions). If you're still running into an issue after adding instructions, please contact our team from the in-app support chat to help debug it! {% embed url="" %} # Prompting While Dashworks can answer open ended questions, prompting it with an overall structure like this can improve its responses by providing it helpful context: 1. **Task:** What you need from Dashworks 2. **Context**: Background info or motivation behind what this is for 3. **Response format**: How should it format its response to be most effective 4. **Search focus**: Are there specific information sources it should focus on? ### Task Ask it to answer a direct question, find some docs, fix a bug, summarize notes, write an email, rephrase content for clarity, and more. ### Context Provide background on what this task is for as this can help Dashworks look for related information and focus the response on the key points based on the context. Please see the examples below for inspiration. ### Response format State the tone you want (ex. professional email, casual message), the response length (ex. short answer, one pager, report with max 3 paragraphs), and structure (blog outline, Twitter thread, bulleted list). ### Search focus Mention specific app names to search or specific files, folders, or project names in them. You can also add up to five URLs for some apps (like Google Drive and OneDrive) and Dashworks will use them as context to respond to the question. ## Try it yourself with these examples
Find a case study * **Task**: `find a case study with a fintech customer` * **Context:** `to share with Stripe's CMO who is interested in our omnichannel marketing platform` * **Response format**: `link` * **Search focus**: `Google Drive, Slack, website blog` **Putting it together**: `Do we have any case study links with fintech customers? I'd like to share them with Stripe's CMO who is interested in our omnichannel marketing platform. It'll likely be in GDrive, shared in Slack, or on our website blog.`
Fix a bug * **Task**: `fix the rate limit error for the analytics dashboard` * **Context:** `console log: 429 Too Many Requests while deploying Lambda` * **Response format**: `causes, solutions` * **Search focus**: `Github backend code, Confluence docs from Infra team, Slack threads` **Putting it together**: `Running into a rate limit error for the analytics dashboard, seeing this console log: 429 Too Many Requests while deploying lambda. Give me some likely causes and possible solutions. Check github backend code, confluence docs from the Infra team, and slack threads.`
Summarize a product document * **Task**: `summarize a PRD` * **Context:** to catch up on upcoming initiatives from the Billing team * **Response format**: `include 3 main pain points, proposed solutions, and next steps` * **Search focus**: **Putting it together**: `Summarize this PRD to help me catch up on the upcoming initiatives from the Billing team:` [`https://docs.google.com/document/d/1qWyV2FDYwytJCNohRVVYfXb9BHkIF52sIiZD-ZPotTA/edit?usp=sharing`](https://docs.google.com/document/d/1qWyV2FDYwytJCNohRVVYfXb9BHkIF52sIiZD-ZPotTA/edit?usp=sharing)`. include the 3 main pain points, proposed solutions, and next steps.`
Learn about a project * **Task**: `overview of AWS to GCP migration` * **Context:** `planning for 2025 OKRs` * **Response format**: `motivations, key people involved, learnings, and follow ups` * **Search sources**: - **Putting it together**: `Can you give me a detailed overview of the AWS to GCP migration project that the Infra team worked on last year? This will be helpful to plan for 2025 OKRs. I'm looking for their motivations, the key people involved, learnings, and follow ups.`
Debug a support ticket * **Task**: `debug ticket #4321` * **Context**: `from Acme about integration issue with Airbnb` * **Response format**: `possible explanations, resolutions, and feature owner` * **Search focus**: `help center articles, Jira issues, Confluence docs, and Github pull requests in the integrations repo` **Putting it together**: `can you help me debug ticket #4321 from Acme about integration issues they're running into with Airbnb? Include possible explanations, resolutions, and the feature owner so I can reach out to them for further help if needed! Search help center articles, Jira issues, Confluence docs, and Github PRs in the integrations repo.`
Prepare for a customer meeting * **Task**: `summarize ongoing deal with Acme` * **Context**: `prepare for a meeting with their CTO to discuss the Europe rollout plan` * **Response format**: `3-5 bullet points` * **Search focus**: `Salesforce notes, Slack conversations, Google Docs, and emails` **Putting it together**: `can you summarize the ongoing deal with Acme to help me prepare for a meeting with their CTO to discuss the Europe rollout plan? Please respond in 3-5 bullet points so I can get up to speed quickly! Look for information in Salesforce records, Slack conversations, Google docs, and emails.`
Write a blog post * **Task**: `write a blog post about the new API V2 release` * **Context:** `geared towards engineering leaders at small and medium enterprises` * **Response format**: `include the motivations behind shipping the API, example use cases this unlocks for engineering leaders, and a CTA for how to` `get started. Optimize for conversion.` * **Search focus**: `Confluence PRD, API developer docs` **Putting it together**: `Write a blog post about the new API V2 Release geared towards engineering leaders at small and medium enterprises. Include the motivations behind shipping the API, example use cases this unlocks for engineering leaders, and a CTA for how to get started. Optimize for conversion. Use the info in Confluence PRDs and our API developer docs available at docs.acme.com.`
# Instructions Instructions let you customize the behavior of Dashworks. They can help improve the accuracy of responses, add custom fallbacks for cases where Dashworks cannot find an answer, or change the length and tone of the response. You can customize instructions at the workspace level and for each Bot. This article includes some examples of instructions you can add to optimize Dashworks. {% hint style="info" %} Dashworks is trained to automatically detect the correct source-of-truth resource to reference when answering questions based on automated signals such as semantic relevance, authorship, popularity, and recency.\ \ At times, Dashworks can get confused due to conflicting or outdated information that it finds across apps. Dashworks is continuously being upgraded to make it work smarter out-of-the-box. You can also teach it to identify the correct source-of-truth resources in your company's apps using Instructions. {% endhint %} ## Types of Instructions ### Bot Instructions Bot instructions apply to Dashworks responses for [specific bots](/bots/custom-bots) and the [Slack channels](/surfaces/slackbot) that they're added to. The Bot's creator and workspace Admins can add and edit instructions for a bot. #### Learned Instructions (Beta) You can provide natural feedback to bots when upvoting or downvoting their responses. We recommend providing feedback in either of these formats: * *For questions related to X, respond with "Y"* * *X means the same as Y in search results* Learned instructions can be viewed, edited, or deleted from the Bot's tab. ### Org Instructions Org instructions apply to all interactions with Dashworks across surfaces. Admins can edit them from the[ AI Controls tab](https://web.dashworks.ai/admin/ai-controls). Dashworks prioritizes Org instructions over Bot instructions in case of conflict. ## General Guidelines Here are some examples of instructions that you can provide for Bots or org-wide. ### Applications Used Every company's knowledge is organized differently. Provide Dashworks context on where to look for different information - similar to how you might provide a new hire context about different tools and internal resources during onboarding. * `Salesforce cases and knowledge articles contain the most relevant information to help answer new support tickets. Notion docs contain the most up to date information for HR processes and policies.` ### Handling Different Use Cases Help Dashworks prioritize information from different sources and respond differently based on their * `For customer support related questions, prioritize answers from Salesforce Knowledge Articles.` * `For HR related questions, prioritize information from the People wiki space in Confluence.` * `Give preference to documents created by John when responding to cybersecurity related questions.` ### Ignore Stale Information Dashworks will automatically deprioritize information that has not been created, modified, or referenced recently. You can provide it additional context on what information to ignore by explicitly adding it as an instruction. * `Your response must only include citations to documents without "Draft", "WIP", or "Archived" in the title.` * `When asked about a policy or deck, ignore any results from 2022 or earlier.` * Labels in wikis and docs like [Confluence](https://support.atlassian.com/confluence-cloud/docs/use-labels-to-organize-your-content/) can be used with Instructions to improve Dashworks' accuracy. For instance, if you have a label for Archived documents, you may add an instruction like `Ignore any Confluence pages with "Archived" label unless explicitly requested.` ### Acronyms and Company Lingo * `Here are some terms you should know about Acme: ABC means Always Be Cool.` ### Route Questions to Users and Teams * `If you don't know the answer to a question about HR or People related topics, ask the user to reach out to <@U12345678> for help.`\ In the above example, please use the user's Slack member ID instead of their username or email for the Slackbot to correctly tag and notify them. You can [get the user's Slack member ID from their profile](https://share.cleanshot.com/lV9Mnnlk1zSGsDKJSy8f). * `For security questions, ask the user to reach out to for help.`\ Here's how you can get the [user group ID in Slack](https://share.cleanshot.com/wNQfdndvFdkb453rfCNg). ### Response Format and Tone * `Always use a formal tone when generating customer facing emails.` * `When generating marketing content, never include the word "delve" or its derivatives in your response.` ### Disambiguate Terms * `Certain events are specific to the office in London or Paris. If you're unsure about which office the user is referring to in their question, ask the user to clarify.` * `If the user is asking about the Grid feature, they're likely referring to the latest version Grid V6. If you're unsure, then ask the user to confirm.` ### Ignore Sensitive Information * `Never include any information related to salary or compensation of employees in your response.` * `Never give advice related to health or legal benefits to users.` ## Known Limitations Currently, URLs added to Instructions are currently not processed. For example, if you include an instruction such as: `Please prioritize answers related to feature requests and product roadmap from this link: https://dashworks.ai/product-roadmap`, Dashworks will be unable to recognize and provide the required response. Optimizing instructions can require some experimentation. We suggest iterating on instructions as and when you notice Dashworks respond in a way that is not intended. If you're looking for suggestions of Instructions for your specific use case or need help optimizing them, please don't hesitate to contact our team at [support@dashworks.ai](mailto:undefined). # Feedback {% hint style="info" %} Any feedback you share with Dashworks is only used to improve responses to questions asked in your workspace. In no case is your content or feedback shared with any other Dashworks customer. {% endhint %} When you ask Dashworks a question, it searches through all the apps you have connected to it to find relevant documents that might have the answer. It then ranks these sources using various signals such as the recency of the information, the source's authority, its relevance to the question, and more.\ \ However, sometimes Dashworks may get confused if the search results are similar or if the information is out of date or conflicting. In such cases, it may prioritize or deprioritize incorrect search results. To rectify this, you can use the thumbs up and thumbs down buttons below each response to give an upvote or downvote on specific references. This will let Dashworks know which sources are most helpful or least helpful. Dashworks will use this feedback to prioritize or deprioritize similar references for future questions. # AI Model Dashworks supports the following LLMs. You can choose the LLM for each question from the toolbar in [Dashworks'](https://web.dashworks.ai/dash-ai) input box, set the default for your use [here](https://web.dashworks.ai/my-ai-controls), and set the default for the entire workspace as an Admin [here](https://web.dashworks.ai/admin/ai-controls). Here is a general guideline on when to use: * **ChatGPT-4o-latest**: Default model, best overall balance of accuracy, speed, instruction following, response length, and response tone. Use this for most tasks. * **o1**: Excels at understanding, debugging, and writing code. * **Claude Sonnet 3.5**: Has a natural sounding tone which sounds less like an AI, use this when drafting content like emails, blog post, or social media posts.
ModelAccuracySpeedComplex InstructionsNatural Sounding
ChatGPT-4o-latestHighHighHighMedium
OpenAI o1HighHighHighMedium
GPT-4-TurboMediumMediumHighLow
Claude Sonnet 3.5MediumHighHighHigh
Claude OpusHighLowHighHigh
Gemini Pro 1.5MediumMediumHighMedium
Meta Llama 3MediumHighLowHigh
# Launch Guide ## 1. Setup workspace * [ ] [**Connect Applications**](/knowledge/connect-apps): Add org-wide connections for relevant applications. * [ ] [**Personalize Workspace**](/admin/homepage): Add your company’s logo, name, and bookmarks so users see a familiar interface. Tip: Ensure your homepage highlights frequently used docs or links (e.g., onboarding pages, key internal sites). * [ ] [**Configure SSO**](/admin/sso) (if applicable): Connect your SSO provider, like Okta or Azure AD, so users can log in with existing credentials. * [ ] [**SCIM Provisioning**](/admin/scim) (if applicable): Automate user lifecycle management by syncing Okta, Azure AD, or Google directory. * [ ] [**Verified Domains**](/admin/verified-domains) (if applicable): Approve relevant domains so colleagues from other branches or sub-domains can join Dashworks automatically. * [ ] [**Add Bot Connections**](/bots/setup-bots): This allows your team to create and manage specialized bots (e.g., an HR bot, a Support bot) and use them on the web app or invite them into Slack channels. ## 2. Onboard the team * [ ] [**Announcement**](/admin/announce-dashworks): Craft a short email or Slack announcement letting everyone know Dashworks is live and why it’s being rolled out. * [ ] **Share Use Cases & Best Practices:** Share common questions for different roles from the [Use Cases section](https://support.dashworks.ai/use-cases/engineering#:~:text=Other%20Sources-,USE%20CASES,-Engineering) and share the [prompt guide](https://support.dashworks.ai/optimize/prompting) and best practices to [improve answers](https://support.dashworks.ai/optimize/improve-answers). * [ ] **Team Trainings**: Schedule department-level training sessions (Engineering, Sales, CS, etc.). Here's a [template onboarding deck](https://pitch.com/v/dashworks-onboarding-yvdsye). If you’re an Enterprise customer, your Dashworks POC can host these sessions—please reach out to them to coordinate. * [ ] **Identify Slack Channels**: Look for Slack channels like #ask-, #help-, #qa-, or #questions in their name or other popular help channels. Invite the [Dashworks bot ](/surfaces/slackbot)to these so it can auto-respond to routine queries. * [ ] [**Org-Wide Chrome Extension**](/admin/chrome-extension-setup): Work with your IT team to push the Chrome extension to all employees or specific Organizational Units. Or encourage individual users to [add the extension](/surfaces/chrome-extension) for quick access to answers. * [ ] **Shared Channel:** Invite the team to a shared Slack or MS Teams channel with your Dashworks POC for faster support and updates. ## 3. Monitor & optimize * [ ] [**Analytics & Insights**](/admin/analytics): Track usage metrics by department and monitor Dashworks’ performance. * [ ] [**Customize Instructions**](/optimize/instructions): Refine or add org-wide instructions to tune Dashworks' behavior. * [ ] **Regular Check-Ins**: Every 3–6 months, reconnect with your Dashworks POC to share feature requests and feedback or to plan advanced training. ## 4. Drive **adoption** * [ ] **Showcase Key Wins**: Let your team know how many questions were answers and other success metrics. * [ ] **Team Spotlights**: Recognize individuals or departments who are strong adopters. * [ ] **Gather Testimonials**: Encourage “power users” to share their stories, for instance by sharing a short blurb on “how Dashworks helped me do X faster”. Following this plan ensures your team understands the “why” and the “how” behind Dashworks, leading to better engagement and long-term success. If you need more detailed instructions on any step (e.g., setting up Slackbot, refining instructions, or handling advanced SSO/SCIM scenarios), please contact your Dashworks POC or reach out to . # Announce Dashworks Hey everyone, We’re excited to introduce you to Dashworks, our new AI search assistant. Dashworks connects with our company’s internal knowledge to find answers, search docs, and more. **What can Dashworks help me with?** 1. **Summarize**: *Tell me about the Phoenix project* 2. **Search**: *Do we have any decks for Fintech industry?* 3. **Answer**: *How can a customer upgrade their plan?* 4. **Create**: *Write a blog post about our upcoming launch in Australia* Learn about other use cases of Dashworks for your role [here](https://support.dashworks.ai/use-cases/engineering#:~:text=Other%20Sources-,USE%20CASES,-Engineering). **How** **do I get started?** 1. Sign up at [web.dashworks.ai/signup](https://web.dashworks.ai/signup) with your work email. 2. Connect all the apps you use daily from the [App Store](https://web.dashworks.ai/integrations). 3. Start asking questions from the [homepage](https://web.dashworks.ai/). 4. Optionally, connect Slack to DM Dashworks, or install the Chrome extension to access it from anywhere. If you have any questions or feature requests, please feel free to contact us or the Dashworks team via the in-app chat. # SSO Currently Dashworks supports Google SSO, Microsoft Azure SSO, and Okta SSO. If you would like to request additional providers, please reach out to . {% tabs %} {% tab title="Okta" %} ### The first steps should be taken within the Okta Admin Panel: 1. Go to **Applications** under **Applications**
2. On the Applications page, select **Browse App Catalog**
3. Search for **Dashworks** App and add it
4. Add an Application label and click **Done**
5. User must specify the Initiate Login URI in the sign-on settings. In most cases this will be [https://apigw.dashworks.ai/v1/google/auth-url?origin=web.dashworks.ai](https://api.dashworks.ai/v1/google/auth-url?origin=web.dashworks.ai). For on-prem deployment, please contact [**support@dashworks.ai**](mailto:support@dashworks.ai) for the Initiate Login URI.
6. Once the App is added, you will have to assign users to the app under the **Assignments** tab. This will enable to users to log into Dashworks app using Okta. To add users, navigate to the **Assign to People** option under **Assign** option on **Assignments** Page. If you already have a group you can choose the **Assign to Groups** option and assign the entire group.
7. You can add people by clicking the **Assign** option next to their name. After you have all the people click the **Done** button
Note: Make sure all the user profiles have these fields populated: * **Username** * **First Name,** * **Last Name** * **Primary Email** * **Display Name.** These fields are required to create profiles in Dashworks. Below is a sample user profile with all required attributes.
### **Now you're ready to open the Dashworks App:** 1. Log into Dashworks and navigate to Settings -> Security under Workspace settings. Click on **Configure** next to OIDC.
2. You will require **Client ID, Client Secret, and Issuer URL**
**Issuer URL** will be of the format for example [*https://dashworks.okta.com*](https://dashworks.okta.com). You can get this from the Okta browser tab.
Also if URL has **-admin** suffix for example , just remove the suffix and only use (**https\://** is required). 3. Fill in the Client ID, Client Secret, and Issuer URL and click **Submit**
4. On successfully applying the changes, you should see the following message:
{% endtab %} {% tab title="Azure AD" %} ### The first steps should be taken within the Azure Portal. 1. Go to *Azure portal* > *Azure Active Directory* 2. In your Active Directory, click **+Add** option and then click App registration
3. In the app registration form, give a unique name to your application and keep the default option for Supported account types. For Redirect URI, please set Redirect type as **WEB** and value as
4. Click on Register and the application will be created. Save the Client ID and Tenant ID (highlighted below) for the newly created app, **this will be required in the SSO creation process on Dashworks app**
5. On the left window, select Certificates and Secrets to create a client secret
6. Click on **+New Client Secret and** fill in the relevant details in the client secret form.
Recommended expires value is 24 months, to avoid creating the SSO registration again for 24 months. Add the secret key after filling in the details in the form.
7. Copy the **Value** of the newly created secret key, **this will be required in the SSO creation process on Dashworks app** ### **Now you're ready to open the Dashworks App:** 1. Navigate to Settings --> Security in the navigation bar.
2. Input the information below and configure the SSO 3. **Client Id**: Noted in Step 4 above 4. **Client Secret:** Noted in Step 7 above 5. **Issuer Url:** [**https://login.microsoftonline.com/**](https://login.microsoftonline.com/)**\/v2.0,** replace \ with your org tenant id noted in Step 4 above. 6. Sign out of Dashworks, then click "Sign in with SSO" to sign in with Azure AD. {% endtab %} {% tab title="Google" %} Google SSO does not require additional setup. You can simply select Google as your SSO provider in the “Single sign-on” page within Dashworks. If you have a Google Workspace you will be prompted with Google SSO both when you first create an account:
You will also be prompted to use SSO if you are logging back in after logging out:
{% endtab %} {% endtabs %} # SCIM ## Managing Members In the Members section, you can manage organization-wide settings for adding members. Options include automatically inviting members to Dashworks or using a signup link for invitations. You can manually invite users by entering their email addresses in the invite modal and monitor if they have accepted your invitation. You can also view who from your organization has not been invited, and who is blocked from accessing Dashworks. Here's a quick video that reviews how to manage members and sync your directory: {% embed url="" %} ## Directory Sync When you sync your company directory, new users will be automatically added to Dashworks upon joining your organization. This means Dashworks is one less tool you must remember to provide access to for new hires - they will have access as soon as they are added to your directory. Remember to enable the “Automatically Invite Team Members” option in the Admin Settings. This ensures that all team members can access Dashworks as long as they are active in your organization. Moreover, you can easily manage your directory within Dashworks. Regularly reviewing your 'Invited' users will reveal those who have been invited but have not yet activated their Dashworks subscription. A recommended practice is to select "Resend invite" for these users, accompanied by a personal message from you as an Admin. This way, these users are notified of their invitation and can start using Dashworks immediately.
## SCIM Setup {% tabs %} {% tab title="Okta" %} For provisioning and deprovisioning users automatically, Dashworks supports a SCIM integration with Okta. #### Requirements 1. Set up Okta SSO with Dashworks following the instructions at [SSO](/admin/sso). 2. Reach out to for the SCIM base URL and OAuth Bearer Token for your organization. #### Step-by-Step Configuration Instructions 1. Log into your Okta Admin account and add Dashworks app from the Application Catalog. The Dashworks app may already be present if Okta SSO is set up for your organization. 2. In the Application, click on Provisioning tab and then click the Configure API integration. 3. Fill in the details for SCIM base URL and OAuth Bearer Token and click on Test API Credentials and click save.
4. In the Provisioning **To App** Settings, enable the following: * Create Users * Update User Attributes * Deactivate Users and click **Save**. 5. For newly created app, Click on Assignments tab in the Application and assign users to your application. In order to assign groups to sync group memberships, navigate to Push Groups tab, from the "Push Groups" dropdown, select: "Find Groups by Name". Search for the group you'd like to push and select it. Make sure the box is checked for "Push Immediately" and click "Save".
6. (Optional) If you have already have an app with assigned users before adding the provisioning feature, you can re-provision users by clicking on the **Provision User** option in the **Assignments** tab and then click **OK** to provision all users.
#### Application username format Please select Email for the Application Username form. {% endtab %} {% tab title="Azure (Entra ID)" %} For provisioning and deprovisioning users automatically, Dashworks supports a SCIM integration with Entra ID (formerly Azure AD). **Requirements** 1. Set up Azure SSO with Dashworks following the instructions at [SSO](/admin/sso#azure-a-d) 2. Reach out to for the SCIM base URL and OAuth Bearer Token for your organization. ### Configure your integration 1. Sign in to the Entra ID Admin Center Dashboard. Select “Enterprise applications” from the list of Azure services.
2. Click "New Application".
3. Select “Create your own application” and continue.
4. Give your application a descriptive name (such as "Dashworks-SCIM"), and select the “Integrate any other application you don’t find in the gallery (Non-gallery)” option, then click “Create”.
4. Select “Provisioning” from the “Manage” section found in the navigation menu.
4. Click the “Get Started” button.
5. Select the “Automatic” Provisioning Mode from the dropdown menu. 6. In the “Admin Credentials” section, copy and paste the Endpoint you recieved from in the “Tenant URL” field. 7. Then, copy and paste the Bearer Token you recieved from into the Secret Token field. 8. Click “Test Connection” to receive confirmation that your connection has been set up correctly. Then, select “Save” to persist the credentials.
### Set and enable Attribute mappings 1. Expand the “Mappings” section.
2. Make sure the group and user attribute mappings are enabled, and are mapping the correct fields. The default mapping should work, but your specific Azure setup may require you to add a custom mapping.
3. Make sure that you are mapping `objectId` to `externalId` within the Attribute Mapping section.
4. Make sure that the following attributes are mapped: 1. `username` 2. `displayName` 3. `jobTitle` 4. `mail` 5. `givenName` 6. `surname` 7. `objectId` 8. `employeeId` 9. `department` 10. `manager` ### Assign users and groups to your application 1. In order for your users and groups to be synced, you will need to assign them to your Entra ID SCIM Application. Select “Users and groups” from the “Manage” section of the navigation menu.
2. Select “Add user/group” from the top menu.
3. Select “None selected” under the “Users and Groups”. In the menu, select the users and groups that you want to add to the SCIM application, and click “Select”.
4. Select “Assign” to add the selected users and groups to your SCIM application.
### Turn on provisioning for your SCIM application 1. In the Provisioning menu, confirm the “Provisioning Status” is set to “On” and that the “Scope” is set to “Sync only assigned users and groups”.
Once you begin provisioning users and groups, changes will reflect in [Dashworks Members](https://web.dashworks.ai/admin/members) page within 60 minutes.
{% endtab %} {% endtabs %} # Analytics As a company Admin, you can view your team's usage, most popular queries, and top unsuccessful queries from the [Analytics tab](https://web.dashworks.ai/admin/analytics). You can also view details on connected applications at the Org and Individual levels and monitor daily and monthly usage. Here's a quick video that gives you a walk-through of the Analytics page: {% embed url="" %} # Verified Domains By default, access to a Dashworks workspace is restricted to users who have the same email domain as the first user who signed up for that workspace. To allow users from other email domains to access your Dashworks workspace, you may perform the following steps: 1. Go to Settings -> Workspace -> Security in your Dashworks workspace. 2. Under Domain Management, click 'Add Domain.'
3. Enter the desired domain to add to your workspace and click 'Next.' 4. To verify your ownership of the added domain, follow the steps below to add a TXT record with your DNS provider.
5. Click 'Verify' to complete the verification. #### Single Sign-On If you have Single [Sign-On enabled](/admin/sso) for your Dashworks workspace, you may now assign users in your SSO provider from all verified domains. The assigned users will log into your Dashworks workspace using SSO. #### SCIM/Directory Sync If you have [SCIM/Google Workspace directory](/admin/scim) connected to your Dashworks workspace, users from all verified domains will be synced (provisioned/de-provisioned) in Dashworks. You may see all synced users by navigating to Settings -> Workspace -> Members. #### Org-wide connections You may connect one or more org-wide connections from the [App Store](/knowledge/connect-apps). For Dashworks users in your workspace to get information from these apps, they must log into Dashworks using the same email they use to log in to the connected org-wide applications. #### Analytics All analytics available at [Settings -> Workspace -> Analytics](/admin/analytics) are automatically aggregated across all users and verified domains in your workspace. #### Shared topic links Users from all verified domains will be able to log in to your Dashworks workspace and access any shared topics created within it. # Schedule Training If you are still trialing Dashworks, our Product Specialist can provide one-on-one guidance during the onboarding process and throughout your trial period. You can reach out to them at . After your trial period ends, we recommend hosting a webinar or a 'Lunch and Learn' session. This is a great way to introduce your team to Dashworks. It's also an excellent opportunity for your team to meet their dedicated Customer Success Manager (CSM) and learn more about accessing support, should they need it. Depending on your team's size, we offer a few different formats. Your CSM can assist you in scheduling times and dates that work best for your team. If you're interested in hosting a webinar, please contact your CSM. # Homepage You can customize your Dashworks workspace in the Appearance tab to match your company's brand and needs. You can set your company's name, logo, homepage background, and homepage bookmarks. If you want to create a custom domain for your workspace, please get in touch with Support[.](mailto:undefined) Here's a quick walkthrough of how to customize your Dashworks experience: {% embed url="" %} {% embed url="" %} # Chrome Extension Setup Pre-install the Chrome extension as an Admin. Admins can enable the [Chrome Extension](https://chromewebstore.google.com/detail/dashworks/iecgdccnjbljdabegnogafjkkjlcpcgh) for specific teams or the entire organization. This makes it easy for team members to get started with using Dashworks, without needing to install the extension themselves. The Chrome extension can be used in a few ways: 1. As Chrome's new tab page 2. From the extension toolbar 3. From the address bar by starting a query with `dash [query]` Additionally, the extension is required for certain integrations such as Notion. The installation is "silent" since it does not automatically take over the new tab page, unlike if users are to install the extension themselves. Instead, it simply adds the extension to the extension toolbar in Chrome. Individual users can then decide to make it their new tab page from their [personal settings](https://web.dashworks.ai/browser-extension). ### Step 1 * Visit [https://admin.google.com](https://admin.google.com/) * From the sidebar on the left, navigate to Devices → Chrome → Apps & Extensions → Users & Browsers ### **Step 2** * Select an Organizational Unit to deploy the Dashworks Chrome Extension * Click the "+" button in yellow on the bottom right of the page * Select "Add from Chrome Web Store" and paste the app ID: `iecgdccnjbljdabegnogafjkkjlcpcgh` * Click Select to allow users to install Dashworks ### **Step 3** * This will now allow team members to install the browser extension * Click on the Installation policy drop-down and select "Force install + pin to browser toolbar" or "Force install" to deploy it to the users in the Organizational Unit selected above # Overview The Dashworks API empowers you to programmatically access [Dashworks Bots](/bots/custom-bots), letting you to send questions and receive AI-powered answers grounded in your company's knowledge. This opens up a world of possibilities for integrating Dashworks' intelligent capabilities into your existing workflows and internal tools. Check out some example use cases below and dive into our [API reference](/api/api-reference) to explore the available endpoints. If you have any questions or suggestions on how we can improve the API for your specific use case, we'd love to [hear from you](mailto:undefined)! # Authentication The Dashworks API uses API keys for authentication. This page explains how to use API keys, how to obtain them, and best practices for managing them securely. ## Using API Keys All API endpoints require authentication using an API key. To authenticate your requests: 1. Include an `Authorization` header in your HTTP request. 2. Set the value to `Bearer {api_key}`, replacing `{api_key}` with your actual API key. Example: ```http Authorization: Bearer your_api_key_here ``` If you send an incorrect or deleted API key, you will receive a 401 Unauthorized response. ## Obtaining API Keys To generate API keys for your workspace: 1. Log in to your Dashworks account. 2. Navigate to [Settings > API Keys](https://web.dashworks.ai/admin/api-keys). 3. Click on the "New API Key" button. Only Admins can create and manage API keys. API keys are long-lived and do not expire automatically. You can delete API keys at any time by going to Settings > API Keys. {% hint style="info" %} If you encounter any issues with authentication or have questions about API key management, please contact our [support team](mailto:undefined). {% endhint %} # Rate Limits To ensure fair usage and maintain the quality of our service, the Dashworks API implements rate limiting. This page explains our rate limit policies and how to handle them in your applications. ## Rate Limit Details The following are key points about our rate limits: * **Endpoint Limit**: * The `/v1/answer` endpoint is limited to 1 request per minute. * The `/v1/documents` endpoint has different limits based on the method used. * `PUT:` 20 requests per minute. * `GET:` 60 requests per minute. * `DELETE:` 60 requests per minute. * **Reset Interval**: Rate limits reset on the minute mark, regardless of when the request was made within that minute. * **Limit Exceeded**: A 429 (Too Many Requests) response is sent when you hit the rate limit. * **Scope**: Rate limits apply at the Dashworks workspace level, shared across all API keys and bots. ### Reset Timing Example * If you make a request at 10:14:01, the next available request slot will be at 10:15:00. * If you make a request at 10:14:59, the next available request slot will still be at 10:15:00. We may adjust the reset timing in the future. Always refer to the latest documentation for the most up-to-date information. ### Workspace-Level Limits It's important to understand the implications of workspace-level rate limits: * All API keys associated with your workspace share the same rate limit. * Creating additional API keys will not increase your request throughput. * The same limit applies to all bots within your workspace. ### Best Practices To make the most of the Dashworks API while respecting rate limits: 1. Implement retry logic with exponential backoff for 429 responses. 2. Consider caching responses where appropriate to reduce API calls. 3. Design your application to distribute requests evenly over time. 4. Monitor your API usage to stay within the limits. ### Need Higher Limits? If you require higher rate limits for your use case, please contact our support team to discuss your needs and potential solutions. {% hint style="info" %} [Reach out to our team](mailto:undefined) for questions about rate limits or to request an increase. {% endhint %} # API Reference {% content-ref url="/pages/uAzOOjzxZq2X4QJelQ0L" %} [Answer API](/api/api-reference/answer-api) {% endcontent-ref %} {% content-ref url="/pages/HbP6SPxbn2JbOrP0ULYg" %} [Connector API](/api/api-reference/connector-api) {% endcontent-ref %} # Answer API {% openapi src="/files/8BPUuWuUj5pqjSi1kuoH" path="" method="post" %} [answer-api-20250217.json](https://426524836-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F48ZJSsUfoeTy0eGVWSPU%2Fuploads%2FU4J9wO7FazX74gL6JWg0%2Fanswer-api-20250217.json?alt=media\&token=17ec8bcf-c8ea-4bec-aa40-df4f936fd66c) {% endopenapi %} # Connector API {% openapi src="/files/UDeg8UR7Wlfj8608G2y7" path="/v1/documents" method="put" %} [documents.json](https://426524836-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F48ZJSsUfoeTy0eGVWSPU%2Fuploads%2Fd5TdEJATgyuChpj4KDRW%2Fdocuments.json?alt=media\&token=d1397f08-995a-41b6-af96-4d5d876067bd) {% endopenapi %} {% openapi src="/files/wmhJExOokBwX1xeVJzUP" path="/v1/documents" method="get" %} [documents.json](https://426524836-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F48ZJSsUfoeTy0eGVWSPU%2Fuploads%2FYkXdLbL1luCMSSm7uvQy%2Fdocuments.json?alt=media\&token=e8a803ea-998b-4f46-84f2-0a6c98b09152) {% endopenapi %} {% openapi src="/files/Jp6X2FVNVjvBlEtxW0Nb" path="" method="delete" %} [documents.json](https://426524836-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F48ZJSsUfoeTy0eGVWSPU%2Fuploads%2FBR64v0YBgVTlVCRkTtAi%2Fdocuments.json?alt=media\&token=96e9f302-d294-4b0c-ae9f-b4eaff0a8c89) {% endopenapi %} # Zapier Integration Dashworks' API can also be accessed from its Zapier integration: {% embed url="" %} # Examples
Automate RFPs and Security Questionnaires Here's an [example Zap](https://zapier.com/shared/automate-google-sheets-questionnaire-with-dashworks/14c2f453fe8b44f45bf324df22d9053fd84d5e76) to automatically create answers for questions in a Google Spreadsheet.
Draft Support Replies Here's an [example Zap](https://zapier.com/shared/dashworks-zendesk/f040ab179639a050bec6ea65af3cbe6887893133) to automatically create draft replies for new support tickets created in Zendesk.
Sales Enablement on Customer Calls Equip your sales team with up-to-the-minute competitive intelligence, product details, and pricing information during customer calls. Dashworks Answer API ensures that your reps have the right data at their fingertips, enabling them to close deals faster and with greater confidence.
Embed in Your Intranet Transform your company intranet into a powerful knowledge hub. With Dashworks Answer API, employees can instantly access company policies, HR documents, and project updates, no matter where the information is stored.
Incident Resolution and On-Call Issues Resolve critical incidents faster by providing your on-call teams with instant access to relevant suggestions based on internal wikis, code snippets, and past issues.
# Pricing ## Answer API The [Answer API's](#answer-api) pricing is determined based on the AI model used for the Bot corresponding to the `bot_id` parameter used in the API request. Admins can track API usage from the API tab in the[ Analytics dashboard](https://web.dashworks.ai/admin/analytics). | Tier | AI Models | Price Per Request | | ------ | ---------------------------------------------------------------------------------------- | ----------------- | | Tier 1 | o1, GPT-4 Turbo, Claude Opus, Claude 3.7 Sonnet Thinking | $2.5 | | Tier 2 | ChatGPT-4o, GPT-4o, o1-mini, Claude 3.7 Sonnet, Claude 3.5 Sonnet, Llama 70B, R1, Grok 2 | $0.75 | | Tier 3 | o3-mini, Gemini 1.5 | $0.25 | | Tier 4 | Gemini 2.0 Flash | $0.10 | ## Connector API The [Connector API ](#connector-api)is currently free to try during early access. # Search Permissions Dashworks automatically respects document-level permissions from app connections. Here's how it determines which app connections to use for search permissions:
SurfacePermissions
Web app when no bot is taggedDefault behavior of using the permissions of the app connections for the user who is asking the question
Web app when a bot is tagged with "@Bot"Permissions of the app connections for the Bot
Slackbot in DMsDefault behavior of using the permissions of the app connections for the user who is asking the question
Slackbot in channelsPermissions of the app connections for the Bot
# Search Modes Dashworks four three powerful search modes to help you find the right information quickly and efficiently. Whether you're searching across your work apps, analyzing specific files, searching the web, or just need creative AI assistance, Dashworks has you covered. | Mode | Best For | Example | | ----------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------- | | **Apps** | Finding internal documents, tasks, and conversations across your work apps. | *“What pitch deck should I use for prospects in healthcare?”* | | **Attach** | Working with files that are from an unsupported source or on your desktop | *"Can you redline this contract document"* | | **Web** | Searching for real-time information from the internet. | *"What are the latest AI trends?"* | | **AI Only** | Brainstorming, content generation, or creative tasks without searching apps. | *“Help me rewrite this email to be more professional: <>“* | # User Roles Your workspace has two user roles - **Member** and **Admin.** Here are the additional features and permissions available to Admins:
FeatureMemberAdmin
Workspace SettingsNo accessFull access
AnalyticsNo accessFull access
Org InstructionsNo accessFull access
Member ManagementInvite membersInvite members, block members, and change member roles
Bot AccountCannot change Bot Account or its connectionsCan setup and edit Bot Account and its connections
BotsCreate bots and edit bots that you've createdCreate bots, and edit or delete any bot
App ConnectionsCan add Individual connectionsCan add Org and Individual connections
FilesCan access any files in search resultsCan upload and delete files, and access in search results
AnswersCan create new answers and edit themCan create new answers, and edit or delete any answer
AI ModelCan set individual AI model defaultCan set org-wide AI model default
BillingNo accessFull access
# Org vs Individual Set yourself up for success by taking these steps before integrating your organization-level apps with Dashworks Dashworks allows users to connect apps at Org-wide and Individual levels, depending on the availability of APIs. Individual connections can be established by any user in the workspace, connecting the app solely for their own use. Information within these Individual connections is not shared with anyone in the workspace who does not have access.\ \ On the other hand, Org connections can only be set up by Admins, and the app can be connected for everyone in the workspace at once. Dashworks uses "delegated access" for Org connections, ensuring that all individual-level permissions from the connected app are respected. As a result, individuals can only access content they have permission to view in the connected app. Under no circumstances can individuals who do not have access to a document, message, task, etc., see it in their Dashworks responses.
Are individual permissions respected for Org-wide connections? Yes, Org-wide connections use user-level delegated access so that individual permissions are still respected based on the logged in user's email. For instance, say you have setup an org-wide connection for Google Drive and a user with email signs up to Dashworks and asks a question. Dashworks will then check if the Google Drive has a seat assigned for , and if it does, it will only return search results that the email has access to.
Is there ever a reason to have both an org-level and an individual level connector for the same source? There are two cases when you may want to add an individual connection in addition to the org-wide one:\ \ 1\) To search additional accounts: For instance, say you have a support inbox called . You would want to add it as an individual connection since the org-wide connection will only let you search the inbox for your primary email that you use to sign in to Dashworks. \ \ 2\) To give the [Bot Account](/bots/setup-bots) access to a connection which has a different email: Say you have a bot account setup with the email but you want it to connect with the Zendesk seat for . In that case, you would add this Zendesk seat as an individual connection.
# Real-Time vs Full Sync Dashworks uses two methods for searching content from connected apps, depending on the app's APIs. For all apps except HRIS and Google Sites, Dashworks makes real-time search API calls to find relevant information based on the user's question instead of pre-indexing data from these apps. HRIS apps do not support real-time search APIs, and hence, Dashworks syncs specific fields for active employees from HRIS apps: employee name, email, title, department, location, and manager name. No other content or fields are synced. The sync can take up to 24 hours and refreshes every 24 hours after connection. Google Sites does not support API access so Dashworks relies on exports with a full-sync. # Workflows Dashworks lets you create customizable templates called Workflows that can be used to save, reuse, and share prompts for frequent tasks. Workflows also help your team discover new use cases for Dashworks. To access workflows, navigate to the ["Workflows" tab](https://web.dashworks.ai/workflows). You will find a library of pre-created templates that you can use immediately. You can also create additional templates and share them with your team. Each template can be customized with variables to suit your specific needs. {% embed url="" %} # Referrals Dashworks' Customer Referral program lets you share your love for Dashworks with your friends and network for rewards! Know someone who could benefit from an AI search and knowledge assistant? If they become a Dashworks customer, we'll send you both a **gift card worth 20% of their first year's subscription value**! To refer your connections, please connect them with us at .