1. Connect your CRM
Your CRM is the first system to connect. It gives Doris the companies, people, deals, stages, owners, and pipeline structure it needs before meetings and follow-up work can be tied to the right opportunities.CRM setup is organization-wide and must be completed by a Doris admin. Open Sources in the sidebar, then choose the CRM card.
Connect Salesforce
Create a Salesforce External Client App, add the required OAuth scopes, then connect from Sources > CRM > Salesforce.
Connect HubSpot
Install the Doris HubSpot OAuth app from Sources > CRM > HubSpot and approve the requested CRM scopes.
1
Choose the CRM
Doris supports one primary CRM connection per workspace. Disconnect any old CRM connection before connecting a new one.
2
Use the right admin account
The person connecting the CRM should be a Doris admin and have enough CRM permissions to approve the integration, read pipeline data, and write back the fields or notes your team wants Doris to update.
3
Follow the provider guide
Salesforce requires a customer-owned Connected App before OAuth. HubSpot uses Doris’ managed HubSpot app. Use the guides above before starting the connection flow.
4
Import and verify records
After OAuth completes, select tracked reps if needed, click Import Data, then confirm companies, people, and deals appear under Records.
2. Connect calendars
Calendar access tells Doris which meetings belong to each rep and gives the native Doris notetaker the schedule it needs.If your team uses Outlook, start with the Microsoft 365 admin connection. A Microsoft 365 admin can consent once, then a Doris admin chooses the reps whose Outlook calendars and inboxes Doris should track.
Microsoft 365 / Outlook
Use the admin-consented Microsoft 365 connection for Outlook teams, with individual Outlook Calendar as the fallback.
Google Calendar
Personal Google Calendar connections are available today. Managed Google Workspace calendar setup is coming soon.
1
Connect Microsoft 365 for Outlook teams
Open Settings > Admin > Data Sources, then connect Microsoft 365 under Global Microsoft 365 Integration. This requires a Microsoft 365 admin account and creates the admin-consented connection Doris uses for Outlook calendar and inbox subscriptions.
2
Choose tracked Outlook users
In Settings > Admin > Data Sources, open Track inboxes & calendars and select the Doris users whose Outlook activity Doris should subscribe to.
3
Use individual calendar connections when needed
The separate Sources > Calendar card is for individual calendar connections. If your team is not using the admin Microsoft 365 connection, each rep can connect their own Outlook Calendar or personal Google Calendar from Sources > Calendar or Settings > Calendar. Managed Google Workspace calendar setup is coming soon.
3. Capture meetings
Doris Notetaker is the default meeting capture path. If Gong is not connected, Doris uses the native notetaker for meetings it can see from connected calendars.Doris Notetaker
The native notetaker is available by default. Admins only need to set the auto-join policy.
Gong
Connect Gong only if your team already records meetings in Gong and wants Doris to ingest those transcripts.
1
Review the default Doris notetaker
Go to Settings > Admin > Notetaker. With no third-party notetaker connected, Doris Notetaker is active by default.
2
Set the join policy
Choose whether Doris joins All Meetings, External Only, or Manual meetings. Most sales teams start with External Only.
3
Connect Gong only if needed
If Gong is your team’s recording system, open Sources > Meeting Intelligence > Gong or enable Gong from Settings > Admin > Notetaker. When Gong is active, Doris disables native notetaker auto-join and uses Gong transcripts instead.
4. Start from verified records
After CRM, calendar, and meeting capture are connected, use Doris from the records it has assembled.Deals
Review synced opportunities, qualification evidence, risks, and next steps.
Meetings
Open transcripts and summaries after Doris processes recorded meetings.
Home
Ask Doris questions about deals, companies, meetings, and pipeline context.