Skip to main content

Data Controls

Controlling What Data Samepage Uses

You have granular control over what data Samepage accesses and analyzes.
​

Integration-Level Controls

You choose which integrations to connect. If you don't want Samepage to access a particular tool, simply don't connect it. You can disconnect any integration at any time.
​

Object-Level Controls (CRM)

For CRM integrations (Salesforce, HubSpot, Zoho CRM), you can select which objects to import — for example, only Accounts and Opportunities, but not Contacts. This controls what data enters Samepage at the integration level.
​

Signal-Level Filters

When creating or editing a Signal, you can narrow the scope of data it analyzes:

  • Slack: Select specific channels (e.g., only analyze #product-feedback and #bugs, not all of Slack)

  • Jira/Linear: Select specific projects or teams

  • CRM: Focus on specific deal stages, account segments, or time periods

  • Analytics: Select specific events, features, or metrics to track

Time Range Controls

Each Signal has a configurable time range that controls how far back it looks (e.g., last 7 days, last 14 days, last 30 days). This limits the volume and recency of data analyzed.
​

Personal vs. Shared Data Boundaries

Personal integrations (Gmail, Google Calendar, Granola, Zoom) create a hard privacy boundary — the data from these integrations is only visible to and usable by the individual who connected them. Other workspace members cannot see or query personal integration data.
​

Example: Minimal Data Setup

A user who wants to limit data exposure could:

  1. Connect only 2 Slack channels (not the full workspace)

  2. Connect only one Jira project

  3. Create Signals scoped to just those sources

  4. Use web Signals for competitive tracking (no internal data needed)

This gives them valuable insights while keeping data access minimal.
​

Did this answer your question?