Connecting BipSync to AlphaSense

Bring your BipSync research notes and files into AlphaSense by connecting your BipSync workspace

• Before You Begin
• Step 1: Workspace Connection (Admin Setup)
• Step 2: Shared Individual Connection
• Step 3: Individual (Private) Connection
• Step 4: Selecting What to Sync
  • What Gets Synced
• Step 5: Modify or Revoke Access
  • Sync Cadence
• How It Works
• Monitoring
• Reporting
• Troubleshoot & FAQs

The BipSync integration lets you securely connect your organization's BipSync research workspace to AlphaSense, so you can search, analyze, and reference internal research notes and attached files alongside external content. The integration supports three connection styles: a workspace-wide connection (set up once by an admin and available company-wide), a shared individual connection (one user authenticates and makes content available to colleagues), and a private individual connection (your own personal scope, visible only to you).

Once connected, content is kept in sync through BipSync's GraphQL API, and AlphaSense respects BipSync's own sharing rules — only notes a user is permitted to see in BipSync will surface for them in AlphaSense.

Before You Begin

• You must have an active BipSync account on your organization's tenant (e.g. your-org.bipsync.io).
• You'll need your BipSync client identifier — the tenant subdomain that appears in your BipSync URL (e.g. your-org if your BipSync URL is your-org.bipsync.io).
• Users will only see notes and files they have permission to access in BipSync — the integration honors BipSync's sharedWith permissions (users and groups) on every document.

Step 1: Workspace Connection (Admin Setup)

A BipSync administrator initiates the workspace integration from AlphaSense. This is the recommended approach for organizations that want company-wide access to BipSync content in AlphaSense.

During setup:

• The admin enters the BipSync client identifier (tenant subdomain) so AlphaSense can connect to the correct BipSync environment.
• AlphaSense redirects the admin to BipSync's OAuth screen, where they review and approve the requested scopes (read access to research notes, files, attachments, users, and groups).
• Granting consent registers AlphaSense as an authorized application against the BipSync tenant and issues access and refresh tokens that are stored encrypted server-side.

After the workspace connection completes, the connection appears as Active in the AlphaSense integrations page, and content sync begins shortly after. The admin can sync content on behalf of individuals in the organization, making that content visible in those users' AlphaSense search.

There can be only one workspace connection per AlphaSense company.

Important:

A workspace connection synced by an admin still respects each end-user's sharedWith permissions in BipSync. Adding a workspace connection does not give every AlphaSense user visibility into every BipSync note — users will only see content explicitly shared with them in BipSync, either directly or via a BipSync group they belong to.

Step 2: Shared Individual Connection

A shared individual connection lets one user authenticate their BipSync account and make selected content available to other AlphaSense users in their company. No special BipSync role or permissions are required to create this type of connection. This is useful when:

• A team lead wants to surface a curated set of BipSync notes to their team without setting up a tenant-wide workspace connection.
• Your organization does not have admin access to install the workspace integration, but you still want broader visibility into a single user's BipSync content.

During setup:

• You enter your BipSync client identifier (the tenant subdomain your organization uses).
• AlphaSense redirects you to BipSync's OAuth screen — sign in with your normal BipSync credentials and approve the requested scopes.
• You select which notes and files to sync (see Step 4).
• AlphaSense makes the selected content available to colleagues in your company, still gated by BipSync's sharedWith rules — a colleague can only see a note if BipSync says they have access to it.

Shared individual connections respect BipSync's permission model on every document and do not bypass BipSync's own access controls.

Step 3: Individual (Private) Connection

A private individual connection lets you sync your own BipSync content into AlphaSense for your personal use only — no other AlphaSense users will see the synced notes, even if they are in the same company. Use this when:

• You only need BipSync content for your own research workflow.
• The notes you want to sync are sensitive and should not surface for colleagues, even when permitted by BipSync's sharing settings.
• You do not have admin access for a workspace setup, and do not want a shared individual connection.

During setup:

• You enter your BipSync client identifier (the tenant subdomain your organization uses).
• AlphaSense redirects you to BipSync's OAuth screen — sign in with your normal BipSync credentials and approve the requested scopes.
• You select which notes and files to sync (see Step 4).
• Synced content is scoped to you alone in AlphaSense.

Each user's private connection is scoped to their own BipSync permissions — your individual token only sees notes and files you can already access in BipSync, and AlphaSense never shows those documents to anyone else.

Step 4: Selecting What to Sync

After connecting (via any connection type), you will see the BipSync picker — a flat, recency-sorted list of every research note and file you have access to in BipSync.

In the picker:

• Notes and files are listed together, with the most recently updated items at the top.
• Each row shows the title and an icon indicating whether the item is a note or a file.
• Multi-select the items you want synced, then click Sync to confirm.

What Gets Synced

Step 5: Modify or Revoke Access

You can change your selection or disconnect at any time. Each connection type (workspace, shared individual, private individual) is managed independently from its own tile on the integrations page.

To update what's synced:

1. Go to the AlphaSense integrations page and open BipSync.
2. Re-open the picker, add or deselect items, and click Sync.

To disconnect:

1. Click Disconnect on the BipSync integration tile for the connection you want to remove.
2. AlphaSense immediately stops syncing for that connection, revokes the stored token, and removes the corresponding synced content from AlphaSense (visible only to you in the case of a private connection; visible to colleagues in the case of a shared individual or workspace connection). You will be prompted to choose whether to keep or delete the synced content.

Disconnecting one connection type does not affect the others — for example, an admin disconnecting the workspace connection does not remove an individual user's private or shared individual connections.

Sync Cadence

• Onboarding (first sync after selection): runs immediately. Large workspaces with many notes and files may take several hours to complete the initial pass, as BipSync's API enforces per-tenant rate limits.
• Incremental updates: every 15 minutes. Catches new notes, edits, and permission changes on content you have already synced.
• Recrawl (deletion detection): every 24 hours, to catch deletions and permission revocations.

How It Works

• AlphaSense syncs the items you have selected via BipSync's GraphQL API.
• Each note's HTML body, text content, and binary attachments are downloaded and indexed for full-text search.
• Sharing fidelity is preserved: AlphaSense reads each item's sharedWith users and groups from BipSync and enforces the same per-user visibility on search results. If you do not have access to a note in BipSync, you will not see it in AlphaSense.
• Group membership changes in BipSync (for example, a new teammate added to your team) are picked up on a recurring sync, so newly-shared content becomes visible without requiring a manual re-sync.
• The integration respects BipSync's API rate limits (10 requests per 10 seconds per tenant). Very large workspaces sync over the course of several hours during onboarding; incremental updates after that are fast.

Monitoring

Use the Monitoring tab to track activity and detect issues.

Information Displayed:

• File Name: Title of the note or file being processed.
• Status:
  • Processing: Item is being indexed.
  • Synced: Item is available for search.
  • Error: Item failed to sync.
• Last Activity: Timestamp of the most recent action.

Steps to Access:

1. Go to BipSync > Monitoring.
2. Review recent syncs and statuses.
3. For errors, check the Reports section for details.

Reporting

The Reports tab provides logs and diagnostics.

Report Types:

• Full Audit Log: all sync events with metadata (user, connection type, action, timestamp).
• Error Report: items that failed to sync, with the upstream cause.
• Skipped Files Report: items excluded due to size limits or unsupported formats.

Steps to Access:

1. Go to Integration Center > BipSync > Reports.
2. Choose the report type.
3. Download in your preferred format.

Troubleshoot & FAQs

What types of connections are available?

Three: Workspace (admin, tenant-wide), Shared Individual (one user authenticates, content shared with colleagues per BipSync permissions), and Private Individual (personal, visible only to you).

What are the prerequisites?

An active BipSync account on your organization's tenant and your BipSync client identifier (the subdomain in your BipSync URL). For workspace connections, the connecting user should be a BipSync administrator or have broad visibility into the content intended for tenant-wide sync.

What is the BipSync client identifier?

The subdomain in your BipSync URL. For example, if your BipSync URL is your-org.bipsync.io, your client identifier is your-org. You are prompted to enter it at connection time so AlphaSense can route API calls to the correct tenant.

How frequently does AlphaSense sync BipSync content?

Onboarding: immediately on selection. Incremental updates: every 15 minutes. Recrawl (deletions and permission changes): every 24 hours.

Why is my initial sync taking several hours?

BipSync's API enforces a per-tenant rate limit of 10 requests per 10 seconds. Large selections can take several hours to fully ingest. Incremental syncs after the initial pass are much faster.

What content gets synced?

Research notes (HTML body and text), files and binary attachments (PDFs, DOCs, and other supported formats), author info, and BipSync metadata including organizations, managers, themes, and labels. Labels carry over as searchable metadata in AlphaSense.

Can I sync labels or organize content by label?

BipSync does not use folders. Labels are surfaced as metadata on synced content and are searchable in AlphaSense, but the picker displays a flat list of items rather than a label-based hierarchy.

Why do I see notes I didn't explicitly select?

Workspace and Shared Individual connections sync the full set of content the connecting user has access to. Private connections sync only what the user explicitly picks in the picker. To narrow the scope of a Workspace or Shared Individual connection, use the picker to limit your selection to specific items.

I see "Something went wrong" when I click Sync.

Refresh the page and try again — transient network errors can interrupt the picker submission. If the error persists, disconnect and reconnect your BipSync account, then re-select your items. If the issue continues, contact AlphaSense support with the time of the attempt so logs can be traced.

Items show as "Processing" in Monitoring but never reach "Synced".

BipSync's API rate limits may be slowing the sync. Items resume processing automatically once the request budget refills. If items remain stuck for over an hour, contact AlphaSense support.

A colleague can't see content I synced via my Shared Individual connection.

AlphaSense honors BipSync's sharedWith permissions on each document. Verify that your colleague has access to the underlying note in BipSync — either directly or via a group. If not, ask the note owner to share it with them in BipSync.

What happens to my content when I disconnect?

You are prompted to keep or delete the synced content. Keeping it makes it searchable in AlphaSense but stops further syncing. Deleting removes it from the AlphaSense index (allow up to a few hours for full removal).

Can I have multiple BipSync connection types simultaneously?

Yes. An admin can maintain a Workspace connection while individual users add Private or Shared Individual connections for their personal scope. Each is managed and disconnected independently.

Are my BipSync OAuth credentials shared with anyone?

No. Tokens are stored encrypted server-side using KMS and are used only by AlphaSense sync workers to fetch your authorized content.

By following this guide, you can set up and manage your BipSync integration in AlphaSense effectively while keeping your research data secure and accessible.