Security and privacyConnectors and scopes

Connectors and scopes

The permissions each Gurusup connector asks for when you approve it, and how webhook requests can be signed.

Only admins can connect a company source. The exception is tl;dv, which each person can connect with their own key while an admin lets members do so. When you approve a connector, the app you connect shows its own consent screen with the permissions below. This page covers Slack, HubSpot, Notion, Linear, the connectors that use a key you paste, public docs and webhooks.

Slack

Gurusup asks for these bot permissions:

PermissionLets the Gurusup app
channels:read, groups:read, mpim:readList public channels, private channels and group messages
channels:history, groups:history, mpim:historyRead messages in those conversations
users:read, users:read.emailRead Slack members' profiles, including email addresses
files:readRead files shared in those conversations
chat:writePost messages
im:write, im:historyOpen and read direct messages with the app, which Gurusup's questions to a colleague use

Gurusup reads a channel only after you invite the app to it. It does not read direct messages between people. See Data we process.

Gurusup also listens for Slack events such as new messages, people joining or leaving a channel, the app being uninstalled and tokens being revoked.

HubSpot

Gurusup asks for read-only access:

PermissionLets Gurusup
crm.objects.deals.readRead deals
crm.objects.contacts.readRead contacts
crm.objects.companies.readRead companies
crm.objects.owners.readRead record owners
sales-email-readRead sales emails

Gurusup processes deals, with their linked contacts and activity.

Notion

Notion does not show a list of scopes. When you connect, Notion asks which pages or sections to share with Gurusup, and Gurusup can only read what you share.

Gurusup checks the signature of the notifications Notion sends about changes, and rejects a request whose signature is missing or wrong.

Linear

Gurusup asks Linear for read-only permissions: read, customer:read and initiative:read. The last two let it read customers and initiatives. It does not ask for admin or any permission that writes, so it cannot change anything in Linear. The app is installed for the Linear workspace as a whole (actor=app), not for the person who approves it, so it keeps working when that person leaves.

Gurusup checks the signature of the notifications Linear sends about changes, and rejects a request whose signature is wrong.

Connectors that use a key you paste

These connectors have no consent screen. You create a key or token in the app and paste it into Gurusup. Gurusup reads only what that key can reach.

ConnectorWhat you paste
HappyScribeAn API key
HoldedAn API token, with the permissions the connect dialog lists
ClickUpA personal API token
AsanaA personal access token
GranolaA workspace or personal API key
tl;dvAn API key. Admins paste one for the organization, and each person can paste one for their own account while an admin allows it. An admin cannot open a personal key or read its folders, and a personal key starts as Private.
FactorialA company API key
SesameA company API token
ZernioAn API key with permission set to Read
monday.comA personal API token
AttioAn access token

The page for each connector says which permissions to give the key. For Factorial, Sesame and Zernio you also choose which kinds of information Gurusup reads.

Public docs

Mintlify and Documentation.AI need no key. You give the address of your published docs, and Gurusup reads the pages anyone can open there.

Webhook

A webhook source has a URL that includes its access token. Anyone with the URL can send data to that source, so treat it like a password. You can replace the URL at any time by regenerating the token, and the old URL stops working.

You can also set a signing secret. If you do, sign the raw request body with HMAC-SHA256 and send the result in the X-Webhook-Signature header as sha256=<hex>. Gurusup rejects requests with a missing or wrong signature. If you leave the secret empty, Gurusup does not check a signature.