# Account Scoring (Beta) Source: https://hc.starbridge.ai/account-scoring Score every account in your market on ICP fit and buying signals, powered by your Market configuration, Vendor Presence bridges, and an Account Scoring bridge. Account Scoring is currently in **beta**. If you'd like access to this feature, please reach out to your Starbridge contact or [support@starbridge.ai](mailto:support@starbridge.ai). ## Why Account Scoring Prioritizing your accounts is harder than it should be. You probably already have a gut sense of how you'd rank your accounts — but that logic usually lives in someone's head or a spreadsheet that goes stale the moment a new signal comes in. Account Scoring fixes that. Every buyer in your market gets one clear, explainable **account score (1–100)**, combining how well they fit your ideal customer profile with how active their buying signals are right now. With Account Scoring, you can work your territory with intent — pulling up the accounts that match a specific play you're running, or simply working down your list starting with your hottest account. Getting Account Scoring up and running takes two setup steps, followed by building your scoring logic: Image22 Your organization's Market — buyers, customers, products, competitors, and complementary vendors — is already configured by default. Review it, especially your Buyers definition, since that's the buyer pool Account Scoring runs against. Image 15 2 Run vendor presence searches across your Market so competitive and complementary vendor data is ready to feed into scoring. Start from scratch, or migrate an existing buyer bridge you've already been using for scoring. Once buyers are scored, you'll see account scores on feed cards, on buyer pages, and throughout the new Territory and Total Market Buyers views. *** ## Step 1: Confirm your Market Market is the org-level configuration that describes how your organization sells, so Starbridge can tailor scoring, signals, and the broader product experience to your business instead of a generic template. Market is configured by Admins. A default Market should already exist for your organization — this step is about **reviewing and confirming it's accurate**, not building it from zero. Your Market is made up of five parts: * **Buyers** — the accounts you sell to, defined using buyer filters. This is the most important part to get right, since it directly defines your organization's total addressable market (TAM) — the buyer pool that both Account Scoring and Vendor Presence bridges run against. * **Customers** — who your current customers are, what your ideal customer profile (ICP) looks like, and the target job titles you typically sell to. * **Products** — the product categories or problems your organization solves, rather than a catalog of individual SKUs or product names. * **Competitors** — the vendors you compete against, tied to the specific products they compete on. * **Complementary vendors** — vendors you sell or work alongside, but don't compete with (for example, a CRM provider like Salesforce). Before moving on, double-check each of these — particularly your **Buyers** definition. If it's too broad, too narrow, or out of date, both your Account Scoring bridge and your Territory/Total Market views will inherit that mistake. Market isn't just an input to Account Scoring — it also tailors the Starbridge experience across the rest of the product based on the buyers, products, and vendors you've told us about. *** ## Step 2: Set up Vendor Presence bridges With your Market confirmed, the next step is setting up **Vendor Presence bridges** at the market level. A Vendor Presence bridge lets you run a vendor presence search across **every buyer in your Market at once**, checking each one for: * Any **competitor** vendors defined against your products * Any **complementary** vendors you sell or work alongside This step is highly recommended before you build your Account Scoring bridge. Vendor presence is one of the strongest available inputs into your Fit score — knowing whether a buyer already uses a competitor or a complementary vendor materially sharpens how well Account Scoring can rank them. Vendor presence data is also surfaced elsewhere in the product, including on individual buyer pages, so it's worth setting up even beyond scoring. Once your Vendor Presence bridges have run, that data becomes available as a column option when you build your Account Scoring bridge in the next step. *** ## Step 3: Build your Account Scoring bridge With your Market confirmed and Vendor Presence bridges in place, you're ready to build your **Account Scoring bridge** — a single, org-level bridge that scores every buyer in your Market. Account Scoring bridges are set up by Admins. Building your Account Scoring bridge follows six steps: Decide whether to build your Account Scoring bridge from scratch, or migrate an existing buyer bridge you've already been using to score accounts. Image 16 2 Double-check that the Buyers defined in your Market are accurate — this is the buyer pool your Account Scoring bridge will run against. Image 17 2 Add the buyer attributes, vendor presence, and AI Analysis columns you want to count toward Fit. If you migrated an existing bridge, confirm the Fit attributes that came over are correct — you can review everything that migrated in the scoring migration report we provide once migration is complete. Image 18 2 Add the bridges you want to count as signal sources. Only include bridges that represent actionable buying signals — exclude one-off analyses or bridges that don't reflect an active buying opportunity (for example, a bridge that looks for dissatisfaction with your own product). Image 19 2 For each fit attribute you've included, define what value indicates a strong buyer fit. For each signal type, define what indicates a strong buying signal. For both Fit and Signals, you can optionally add a prompt describing how different attributes or signal types should be weighed against and prioritized relative to one another (for example, "an RFP is the strongest signal, even without an accompanying meeting"). If you migrated an existing account scoring bridge, your original scoring prompt is migrated in under each fit attribute for you to review and confirm. Image 20 2 Run scoring on the first 5 buyers in your bridge to confirm everything is set up correctly, making edits as needed. Once you're happy with the results, run scoring for every buyer in your Market. This produces one overall **account score (1–100)** per buyer, made up of: * A **Fit score**, shown as a band of **Weak, Moderate, Strong,** or **Ideal** — reflecting how well a buyer matches the strong-fit definition you set for each included attribute, shaped by your overall Fit prompt if you provided one. Image 21 2 * A **Signal score**, shown as a band of **Ice Cold, Cool, Warm,** **Hot,** or **Burning Hot** — reflecting how active and timely a buyer's included signals are, shaped by your overall Signal prompt if you provided one, along with a short explanation of the opportunity it represents.
Fit and Signals then combine into the overall score with a few consistent principles: a strong-fit account with no active signals can still score highly on fit alone; among similar-fit accounts, hotter signals move a buyer higher; and a weak-fit account can get a lift from a hot signal but can't be pushed all the way into your best-fit tier. Scores refresh daily as underlying signals refresh, but you'll need to manually re-run scoring after changing your Fit or Signal configuration. Any column added to the bridge after initial setup is excluded from scoring by default until you opt it in. *** ## Where scores show up Once your Account Scoring bridge has run, scores surface throughout the product: * **On feed cards** — each account update in your feed now shows the buyer's account score alongside the change. * **On the buyer page** — see the overall score plus the underlying Fit and Signal explanations for any buyer. * **In the new Territory and Total Market Buyers views** — the Buyers page now has three tabs: * **Territory** — scoped to a rep's own territory. Sort and filter by account score and by every underlying input that feeds into it (Fit attributes, vendor presence, signal types, and more). * **Total Market** — the same functionality as Territory, scoped to every buyer in your organization's Market. * **All Buyers** — the existing view you have today, unchanged. No account score or score-input columns appear here. Buyer List configuration and management has moved to **Settings**, where it's accessible to Builders and Admins. You can still apply Buyer Lists as a filter on all three Buyers view tabs. If your organization hasn't finished confirming its Market or hasn't set up a territory yet, the Total Market and Territory tabs will prompt you to do so rather than showing an empty view. *** ## FAQ No — a default Market already exists for your organization. This is a review-and-confirm step, especially for your Buyers definition, not a build-from-zero step. Yes, they're optional, but strongly recommended. Vendor presence is one of the strongest Fit inputs, and the data is also useful on its own — for example, on buyer pages. No — when you build your Account Scoring bridge, you can choose to migrate from an existing buyer bridge instead of starting from scratch. Compatible fit attributes and your existing scoring prompt are brought over for you to review, and you'll get a scoring migration report summarizing exactly what came across. AI Analysis and custom web agent columns keep their existing values so you don't spend extra credits re-running them. Account scores range from 1–100, blending a Fit band (Weak, Moderate, Strong, or Ideal) with a Signal band (Ice Cold, Cool, Warm, Hot, or Burning Hot). A top score generally means both strong ICP fit and an active, timely signal. Market, Vendor Presence bridges for Market, and the Account Scoring bridge are configured by Admins. Buyer List management in Settings is available to both Builders and Admins. *** Have questions or feedback on the Account Scoring beta? Reach out to your Starbridge contact or [support@starbridge.ai](mailto:support@starbridge.ai). # Set up users, roles, and teams Source: https://hc.starbridge.ai/admins/adding-new-users-configuring-roles-and-teams-s Once your Bridges are set up, add users, assign their roles, create teams, and subscribe them to the right Bridges. ## User roles There are 3 user roles in Starbridge: * View and action signals from shared Bridges * Receive email digests * Export Bridges as CSVs * Use Ask Starbridge and Explore * Full access to RFP actions *Everything a Consumer can, plus:* * Build, configure, and share Bridges * Define buyer lists * Access all Bridges in the org *Everything a Builder can, plus:* * Add/remove users and assign roles * Create and manage teams * Set up integrations, API keys, and SSO * Configure Bridge credit limits and monitor usage * [Configure feeds on behalf of users](/builders/configuring-bridges-for-consumers) You can modify user roles at any time after initial assignment. ## Add users Go to **Settings → Organization Settings → Users**. Users settings screen Users settings screen Click **+ Add User**, then specify the user's **Role**. Add user dialog showing role selection ## Set up teams Group users into teams so Bridges can be shared with everyone at once — all team members automatically get access to any Bridge shared with their team. Go to **Settings → Teams**. Teams settings screen Click **+ New Team**, then enter a team name and add users. Create team dialog ## Configure a user's feed View and adjust any user's Bridge subscriptions and email digest settings. Go to **Settings → Organization Settings → Users**. Click the **⋯** menu next to a user → **Configure feed and digest**. Toggle Bridges on or off and set the user's email digest cadence (daily or weekly). ## Log in as a user Log in as any Builder or Consumer in your organization to see Starbridge exactly as they do. Use it to **validate a user's setup** — confirm they're subscribed to the right Bridges and getting the right digests after you configure their feed — or to **troubleshoot** an issue a user reports. Go to **Settings → Organization Settings → Users**. Click the **⋯** menu next to the user → **Log in as user**. You'll be taken into Starbridge acting as that user. Click **Exit** in the banner to end the session and return to your settings. While you're in a session, a banner at the top of the screen reads **"You are signed in as \[user's name]"** so it's always clear whose account you're acting in. Sessions expire automatically after **20 minutes**. A countdown appears in the final few minutes before you're returned to your own settings. Only Admins can log in as other users in their organization. ## Related articles See the full admin checklist demo'd in the platform.  Once users are set up, learn how to share Bridges with your team. # Configure single sign-on (SSO) Source: https://hc.starbridge.ai/admins/configuring-sso ## Overview SAML SSO lets your organization centrally manage authentication and user access. Once enabled, users will authenticate through your identity provider, such as Okta, Azure AD, OneLogin, Ping, or any SAML-compatible system. Starbridge supports both **SP-initiated** and **IdP-initiated** login: * **SP-initiated login** — Users start at the Starbridge login page and are redirected to your identity provider to authenticate. * **IdP-initiated login** — Users start from your identity provider's app portal (for example, the Okta dashboard or Azure My Apps) and are signed directly into Starbridge without visiting the login page first. No additional configuration is required to enable IdP-initiated login. Once SSO is configured, both login flows work automatically. You'll be asked to copy values from your identity provider (IdP) into Starbridge. After you save the configuration, Starbridge will display the remaining values you need to paste back into your IdP to complete the connection. In **Authentication Mode**, choose how your users should authenticate going forward: Users sign in using only their Starbridge password. SSO is disabled. Everyone must log in through your identity provider. * Password logins will be disabled * Ensures centralized access control and improved security Users can choose whether to log in with SSO or with their Starbridge password. This mode is helpful for testing before enforcing SSO, and for phased rollouts. Your IdP will provide two pieces of information that must be entered into Starbridge. **Sign-in URL** This is your IdP's SAML login endpoint (often called the "SSO URL," "Login URL," or "Identity Provider SSO URL"). Paste the full URL from your identity provider. **X.509 certificate** Paste the X.509 certificate provided by your IdP. This certificate is used to verify signed SAML responses returned by your identity provider. Copy only the certificate text, including the `----BEGIN CERTIFICATE-----` and `----END CERTIFICATE-----` lines. If your IdP provides multiple certificates, use the active signing certificate. After pasting your Sign-in URL and X.509 certificate, click **Save**. If the settings validate successfully, Starbridge will display the remaining values your IdP needs to complete the SSO connection. Starbridge will display your application-specific SAML details, including: * Domain * **Entity ID** * **SSO URL** Copy these values into your identity provider's SAML configuration, then follow your IdP's prompts to finalize. Test logging in with SSO. If your IdP supports IdP-initiated login, also verify that clicking the Starbridge app tile in your IdP's portal signs you in successfully. We strongly recommend testing before enforcing SSO for all users. ## Need help? If you need assistance configuring your identity provider or troubleshooting SSO, contact [**support@starbridge.ai**](mailto:support@starbridge.ai) and include: * Your IdP (Okta, Azure AD, etc.) * A screenshot of your SAML configuration * The error message seen during login (if any) ## Related articles Add users, assign roles, and create teams after enabling SSO. Configure your org context so Starbridge personalizes signals and AI features correctly. # Connect your CRM Source: https://hc.starbridge.ai/admins/connecting-your-crm Authenticate Salesforce or HubSpot and configure the objects and fields Starbridge can access. Connecting your CRM is the first step in the CRM integration setup. Once connected, Starbridge can match your accounts to Starbridge buyers, sync territories, and push and pull data through lookup and sync columns in your Bridges. This step requires Starbridge Admin access. To integrate your CRM to Starbridge, you must first add the following custom fields to your CRM Account and Contact objects: * **Starbridge Account ID** (text) — Starbridge's unique identifier for every account. Enables lookups by Starbridge account identifier and helps admins identify which accounts were created or modified by Starbridge. * **Starbridge Contact ID** (text) — Starbridge's unique identifier for every contact. Enables lookups by Starbridge contact identifier and helps admins identify which contacts were created or modified by Starbridge. * **Starbridge Is Active** (boolean) — whether Starbridge considers the contact currently active. Defaults to `true` for active contacts; set to `false` when Starbridge detects the contact is no longer employed at the account. These fields significantly improve deduplication accuracy and let Starbridge maintain accounts and contacts up to date in your CRM over time. **Account field: Starbridge Account ID** Before connecting Starbridge to Salesforce, you need to create a custom field on the Account object to store Starbridge data. 1. In Salesforce, click the **Gear icon (⚙)** → **Setup** Salesforce Setup menu 2. In the left sidebar, search for **Object Manager** and open it, or directly click **Objects and Fields** → **Object Manager** Object Manager in sidebar 3. Click **Account** → **Fields & Relationships** → **New** Screenshot 2026 06 15 At 6 20 04 PM 4. Create the field — **Starbridge Account ID**: | Setting | Value | | ---------------------- | ------------------------------------------------- | | Field Type | Text | | Field Label | `Starbridge Account ID` | | Length | `25` | | Description (optional) | `The unique ID for this account from Starbridge.` | | Unique | ✓ Checked | | External ID | ✓ Checked | Screenshot 2026 06 15 At 6 21 31 PM Click **Next** → **Next** → **Save**. Salesforce automatically appends `__c` to custom field API names (e.g. `Starbridge_Account_ID__c`). This is expected. Before connecting Starbridge to HubSpot, you need to create a custom property on the Company object to store Starbridge data. 1. In HubSpot, go to **Settings (Gear icon ⚙)** → **Properties** HubSpot Settings - Properties 2. In the **Select an object** dropdown, select **Company properties**, then click **Create property** (top right)\\ Screenshot 2026 06 15 At 6 26 07 PM 3. Create the property — **Starbridge Account ID**: | Setting | Value | | ---------------------- | ------------------------------------------------- | | Property label | `Starbridge Account ID` | | Description (optional) | `The unique ID for this company from Starbridge.` | | Field type | Single-line text | | Unique | ✓ Require unique values for this property | Screenshot 2026 06 15 At 6 26 52 PM
Click **Create**. Do not delete this property after creation. HubSpot will not allow you to recreate it with the same configuration. **Contact fields: Starbridge Contact ID and Starbridge Is Active** Before connecting Starbridge to Salesforce, you need to create two custom fields on the Contact object to store Starbridge data. 1. In Salesforce, click the **Gear icon (⚙)** → **Setup** Salesforce Setup menu 2. In the left sidebar, search for **Object Manager** and open it, or directly click **Objects and Fields** → **Object Manager** Object Manager in sidebar 3. Click **Contact** → **Fields & Relationships** → **New** Fields and Relationships - New 4. Create the first field — **Starbridge Contact ID**: | Setting | Value | | ---------------------- | ------------------------------------------------- | | Field Type | Text | | Field Label | `Starbridge Contact ID` | | Length | `25` | | Description (optional) | `The unique ID for this contact from Starbridge.` | | Unique | ✓ Checked | | External ID | ✓ Checked | Screenshot 2026 06 15 At 6 03 33 PM 1
Click **Next** → **Next** → **Save & New** 5. Create the second field — **Starbridge Is Active**: | Setting | Value | | ---------------------- | ----------------------------------------------------------------------------- | | Field Type | Checkbox | | Field Label | `Starbridge Is Active` | | Default Value | Unchecked | | Description (optional) | `Whether this contact is actively employed at this account, from Starbridge.` | Screenshot 2026 06 15 At 6 05 51 PM Click **Next** → **Next** → **Save**. Salesforce automatically appends `__c` to custom field API names (e.g. `Starbridge_Contact_ID__c`). This is expected. Before connecting Starbridge to HubSpot, you need to create two custom properties on the Contact object to store Starbridge data. 1. In HubSpot, go to **Settings (Gear icon ⚙)** → **Properties** HubSpot Settings - Properties 2. In the **Select an object** dropdown, select **Contact properties**, then click **Create property** (top right) Select Contact properties and Create property 3. Create the first property — **Starbridge Contact ID**: | Setting | Value | | ---------------------- | ------------------------------------------------- | | Property label | `Starbridge Contact ID` | | Description (optional) | `The unique ID for this contact from Starbridge.` | | Field type | Single-line text | | Unique | ✓ Require unique values for this property | | Click **Create** | | Starbridge Contact ID property settings 4. Create the second property — **Starbridge Is Active**: | Setting | Value | | ------------------------- | ----------------------------------------------------------------------------- | | Property label | `Starbridge Is Active` | | Description (optional) | `Whether this contact is actively employed at this company, from Starbridge.` | | Field type | Single checkbox | | Click **Create property** | | Starbridge Is Active property settings Do not delete these properties after creation. HubSpot will not allow you to recreate them with the same configuration. The Salesforce or HubSpot account used to connect Starbridge to your CRM determines who owns the integration. **Salesforce:** We strongly recommend creating a dedicated API-only integration user rather than connecting as a personal admin account. This keeps your audit trail clean (all Starbridge writes are attributed to one system user, not a person), limits permissions to only what Starbridge needs, and ensures the connection isn't disrupted by team changes. **HubSpot:** HubSpot's OAuth model ties the connection to the account rather than an individual user, so there's no equivalent integration user setup. We strongly recommend connecting Starbridge using a dedicated API-only integration user rather than a personal admin account. This allows you to easily track Starbridge's changes, retain the ability to roll back changes easily, and scope permissions to only what Starbridge needs. Most Salesforce Enterprise, Unlimited, and Performance orgs include up to 5 free Salesforce Integration user licenses. 1. In Salesforce, click the **Gear icon (⚙)** → **Setup**\\ Screenshot 2026 06 16 At 9 47 34 AM 2. Navigate to **Users** → **Users** → click **New User** and fill in the required fields:\\ Screenshot 2026 06 16 At 9 48 52 AM | Field | Value | | ------------------------ | ---------------------------------------------------------------------------------------- | | First Name | `Starbridge` | | Last Name | `Integration` | | Alias | `Starbrdg` | | Email | Your email address (used to receive the Salesforce verification email) | | Username | `starbridge@yourcompany.com` (replace yourcompany.com with your organization's domain) | | Nickname | `Starbridge` | | User License (IMPORTANT) | Salesforce Integration | | Profile (IMPORTANT) | Salesforce API Only System Integrations *(or "Minimum Access – API Only" in newer orgs)* | Screenshot 2026 06 16 At 10 04 04 AM
Click **Save**. Check your email and verify the new integration user account in the Salesforce verification email. Screenshot 2026 06 16 At 10 05 03 AM 3. Create a Permission Set for the integration user: * Go to **Setup** → **Permission Sets** → **New** Screenshot 2026 06 16 At 10 10 10 AM * Label: Starbridge API Integration * License: **Salesforce** API Integration * Click **Save** Screenshot 2026 06 16 At 10 12 29 AM 4. In the Permission Set named Starbridge API Integration, open **Object Settings** and enable at minimum: Screenshot 2026 06 16 At 10 13 33 AM | Object | Object Permissions | Field Permissions | | ------------- | ------------------------------------ | ------------------------ | | Accounts | Read, Create, Edit, View All Records | Read Access, Edit Access | | Contacts | Read, Create, Edit, View All Records | Read Access, Edit Access | | Leads | Read, Create, Edit, View All Records | Read Access, Edit Access | | Opportunities | Read, Create, Edit, View All Records | Read Access, Edit Access | | Users | Read, View All Records | Read Access | Screenshot 2026 06 16 At 10 15 09 AM Screenshot 2026 06 16 At 10 22 56 AM * To grant object access, click **Edit** and check the checkboxes listed above under **Object Permissions**. * To grant field access, check the **Read Access** and **Edit Access** checkboxes to select all fields at once under **Field Permissions**. In the Permission Set named Starbridge API Integration: * Open **System Permissions** Screenshot 2026 06 16 At 10 46 26 AM * Click **Edit** Screenshot 2026 06 16 At 10 47 20 AM * Scroll down to **Approve Uninstalled Connected Apps** and check the checkbox Screenshot 2026 06 16 At 10 48 31 AM * Scroll back up and click **Save** Screenshot 2026 06 16 At 10 48 46 AM 5. Assign the Permission Set to the integration user: * Go to **Setup** → **Users** * Click the integration user's name (go to the letter 'I' for `Integration, Starbridge`) Screenshot 2026 06 16 At 10 37 54 AM * Assign the **Starbridge API Integration** permission set: * Hover over **Permission Set Assignments** * Click **Edit Assignments** Screenshot 2026 06 16 At 10 39 40 AM * Scroll down and select **Starbridge API Integration** from the **Available Permission Sets**, then click **Add** Screenshot 2026 06 16 At 10 40 21 AM * Click **Save** Screenshot 2026 06 16 At 10 40 50 AM 6. Log in as the integration user before connecting to Starbridge: * Log out of your current account in Salesforce * Log in to Salesforce using the Starbridge API Integration user username (**not** your personal email) and password * Once you log in, you will not be able to access the Salesforce UI, since you are logged in as an API only integration user. This is expected. **Don't have a password?** Check your email for a verification email from Salesforce. Verify your integration user account to create a password. Save this password in a secure place. 7. Proceed with the steps described below in Starbridge. Starbridge uses OAuth and does not store your Salesforce username or password. Unlike Salesforce, HubSpot doesn't have a dedicated integration user concept — the connection is made via OAuth and persists at the account level. Any admin with sufficient permissions can connect Starbridge. We recommend connecting as an admin or Super Admin with access to at minimum the **Company**, **Contact**, **Owner**, and **Deal** objects. 1. Log into HubSpot as an admin or Super Admin 2. Proceed with the steps below. Starbridge uses OAuth and does not store your HubSpot username or password. Go to [**Settings → Integrations**](https://dashboard.starbridge.ai/settings/integrations), click **Create**, and select **Salesforce** or **HubSpot**. If you want to connect a sandbox before connecting production, connect to a sandbox instance first. Starbridge supports separate sandbox and production connections. Log into your Salesforce or HubSpot account when prompted. The user you connect must have permission to read and write the objects you want Starbridge to access. Most teams use an admin user or a dedicated integration user to keep audit trails clean. See the instructions above under **Choose who will connect your CRM > Step-by-step instructions for Salesforce**. **Salesforce only:** Salesforce has introduced stricter controls on uninstalled connected apps. The authenticating user must have the **Approve Uninstalled Connected Apps** (or **Use Any API Client**) system permission to authorize Starbridge for the first time. After a successful OAuth, the app appears under Connected Apps OAuth Usage where you can manage policies and assign it to additional users. See the instructions above under **Choose who will connect your CRM > Step-by-step instructions for Salesforce**. After connecting, open your CRM integration and click **Objects & fields**. Screenshot 2026 06 08 At 4 03 08 PM Use the **CRM Configuration Guide** panel on the right to review field recommendations by use case. For each use case you want to enable, click **Enable all recommended fields** — Starbridge selects the recommended objects and fields in one click. Enable all the use cases you expect to need before saving. Each save triggers a resync, which can take a few minutes or a few hours depending on the amount of data being synced — selecting everything upfront means one resync instead of several as you add use cases over time. The **Account categorization** use case is strongly recommended. When enabled, reps can see account context from your CRM directly in Starbridge. Select the account field that best represents account type; by default we recommend Salesforce's **Account Type** field or HubSpot's **Lifecycle Stage** field, and this is included when you click **Enable all recommended fields**. Screenshot 2026 07 28 At 1 49 11 PM Review the selected fields, adjust if needed, then click **Save changes**. Starbridge will only access, edit, or create data within the objects and fields you explicitly select here. Starbridge will never modify or overwrite data in your CRM without your explicit approval. This step does **not** modify or overwrite any data in your CRM; it only connects your CRM to Starbridge so Starbridge can access its data moving forward. You'll see a **Refreshing** status while Starbridge saves your changes and pulls the latest data from your CRM — duration depends on the size of your CRM. When complete, the status updates to **Connected**. ### Reauthenticating your CRM connection Use **Reauthenticate** when you need to refresh or swap the CRM credentials Starbridge is using, without disconnecting or reconfiguring your integration from scratch. Screenshot 2026 07 23 At 9 59 24 AM 1 **When to reauthenticate:** * **Your integration status shows "Reauthentication required."** This happens infrequently, typically when an access token is refreshed on the CRM side. * **You want to switch the connected user.** Common reasons: the original user left the company and their CRM access is expiring, or (Salesforce and Salesforce Sandbox only) the original connection used a personal user profile and you want to switch to a dedicated integration user as a best practice. **How it works:** Click **Reauthenticate** on your CRM integration. This opens the OAuth window for Salesforce or HubSpot, where you log in as the user you want connected going forward. **What to expect:** Reauthenticating has no effect on account matching, CRM lookup and sync columns, or contact sync, *as long as the new user has equivalent permissions to the previous one.* If the newly connected user has **fewer permissions** — for example, no read or write access to an object or field Starbridge was previously using — those objects or fields may disappear from CRM columns, account matching, or contact sync. This won't delete or change any data in your CRM; the affected lookups and syncs will simply stop working until permissions are corrected on the new user. ## Next steps With your CRM connected, the next step is account matching — mapping your CRM accounts to Starbridge buyers. This is required before territories, CRM-synced buyer lists, and lookup and sync columns will work. Map your CRM accounts to Starbridge buyers. # Setting up your Organization Profile Source: https://hc.starbridge.ai/admins/organization-business-context Configure your Organization Profile to personalize signals, scoring, and AI-generated content across Starbridge. Your Organization Profile is one of the most important things to get right in Starbridge. It's the business context layer that powers how Starbridge understands your company - and it feeds directly into signals search and scoring, Ask Starbridge, AI-generated column content, and any emails or summaries Starbridge drafts on your behalf. Starbridge auto-generates an Organization Profile when your account is created, but the generated content is only a starting point. **You should review it before using Starbridge in earnest, and keep it updated as your business evolves.** Only Admins can view and edit the Organization Profile. Navigate to **Settings → Organization Profile** to get started. ## Why it matters Every AI-powered feature in Starbridge uses your Organization Profile to contextualize its outputs. Concretely, that means: * **Signals search & scoring** - Starbridge scores buyer signals against what's relevant *for your business*. If your ICP, competitors, or use cases are missing or wrong, signals get misfiled and buyers get mis-scored. * **Ask Starbridge & Slackbot** - When you ask questions like "Who are our best-fit accounts in the mid-market?" or "Summarize why this account is a good fit," the answer is grounded in your Organization Profile. Thin or inaccurate context produces generic answers. * **AI-generated columns** - When you create a column with AI (e.g., "Does this account show signs of legacy infrastructure?"), the prompt is enriched with your company context so the output reflects your positioning, not a generic tech company's. * **AI-generated emails and content** - Starbridge-drafted emails and summaries reference your products, value props, and differentiators. Without accurate context here, generated content will read as off-brand or vague. The downstream impact of a stale or incomplete Organization Profile is real: insights feel off, answers feel generic, and it erodes trust in the platform. Spending 10–15 minutes here pays dividends across everything else. ## Sections at a glance The Organization Profile is organized into four main sections. Each field has an info tip explaining what to include — read them before filling in a section, especially for fields like "Core Problems We Solve" and "Product Experience & Value Narrative" that are easy to get wrong. ### Company & Product Overview The foundational layer. This is where Starbridge learns what your company actually does. | Field | What to include | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **Company Name** | Your legal or DBA name | | **Company URL** | Your primary public-facing URL | | **Company Overview** | 2–4 sentences on what your business does. Be specific — say what you sell and who you sell it to, not just a mission statement. | | **Core Problems We Solve** | The actual problems your buyers experience before finding you. Frame these from the buyer's perspective, not your feature list. | | **Products and Services** | The key things you sell. Include product names if you have them — Starbridge will use these when scoring and summarizing. | | **Product Experience & Value Narrative** | What it's actually like to use your product. How do different personas — an admin vs. an end user, a VP vs. an IC — experience value differently? | The **Core Problems We Solve** and **Product Experience & Value Narrative** fields have the biggest impact on Ask Starbridge quality. Generic filler here (e.g., "we help companies be more efficient") produces generic answers. Be specific about your buyers' pain and how your product addresses it. ### Customers & Competitors This section anchors Starbridge's understanding of your market — who you sell to, who you beat, and why you win. | Field | What to include | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Ideal Customer Profile** | Key segments, org types, headcount ranges, geographies, and budget indicators you target. The more specific, the better. | | **Customers** | A handful of real, named customers — especially well-known logos. Starbridge uses these to find similar accounts. | | **Buyer Personas & Target Titles** | Who actually buys and who champions the product internally. Include specific titles, not just "decision-maker."

Starbridge will tag any contacts with these titles as **ICP** (ideal customer profile) or **Target** contacts. | | **Competitors & Incumbents** | Tools and vendors you most commonly replace or compete against. Include the status quo (e.g., "spreadsheets" or "manual research") if that's a common competitor. | | **Why Customers Choose Us** | Your differentiation in plain terms. Why do buyers choose you over the alternatives listed above? | A common mistake is listing competitors without context. "We compete with Salesforce" is less useful than "We compete with Salesforce's native activity tracking — we win when teams need deeper intent signal coverage without a custom data team." Give Starbridge the reasoning, not just the name. ### Customer Use Cases & Outcomes This section helps Starbridge surface relevant signals and frame value in the context of what your customers actually achieve. | Field | What to include | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Key Outcomes/Results** | Quantified or qualitative results your customers consistently achieve. E.g., "25% increase in outbound response rate" or "reduced time-to-close by identifying intent earlier." | | **Customer Use Cases & Case Studies** | Real examples of how customers use your product and what they got from it. Reference specific segments or company types if you have them. | ### Additional Information An open-ended field for anything that doesn't fit elsewhere — niche market context, regulatory environment, go-to-market nuances, etc. Leave it blank if you don't have something specific to add; don't pad it with generic information. ## Regenerating your profile If you've made significant changes to your business and want to start fresh, you can regenerate your Organization Profile by clicking **Generate with AI** on the Organization Profile page. Regenerating will **overwrite all manual edits** you've made. Starbridge will prompt you to confirm before proceeding. If you want to preserve specific customizations, copy them elsewhere before regenerating, then paste them back in afterward. ## Keeping it accurate Your Organization Profile should reflect how you'd describe your company to a new hire on their first day - specific enough to be useful, accurate enough to trust. A few situations that should prompt a review: * You've launched a new product or expanded into a new segment * Your ICP or pricing has shifted * You've entered (or exited) a competitive market * You've accumulated a set of new reference customers worth naming * Ask Starbridge answers are starting to feel off or overly generic There's no automated reminder to update your Organization Profile, so we recommend making it part of your quarterly GTM hygiene review. ## Frequently asked questions Admins have access to view and edit the Organization Profile under **Settings → Organization Profile**. The clearest signal is Ask Starbridge. Ask a question like "Why would a \[your ICP] care about \[your product]?" - if the answer is accurate and specific to your business, your profile is in good shape. If it's generic or wrong, find the relevant section and update it. No, but the more complete your profile, the better Starbridge's outputs will be. At minimum, we recommend filling in **Company Overview**, **Core Problems We Solve**, **Ideal Customer Profile**, and **Competitors & Incumbents** before building your first Bridge. # Overview guide - start here! Source: https://hc.starbridge.ai/admins/overview-guide Everything you need to configure Starbridge for your team. As a Starbridge admin, you're responsible for setting up the workspace, onboarding your team, and connecting Starbridge to your CRM so every rep sees the right signals for their accounts. This guide covers what to set up, in what order, and where to go for the details. New to Starbridge? Watch the [Admin Training Walkthrough](/admins/video-walkthrough) first — it covers org setup, user management, and platform configuration end to end. ## What admins set up **Organization profile:** Starbridge uses your org description and business context to generate sharper outbound emails, RFP responses, and AI analysis across every bridge your team builds. Set it once and everything downstream benefits. **Users, roles, and teams:** Three roles — Admin, Builder, and Consumer — control what people can do in Starbridge. Teams control which Bridges people see. Getting this right means reps only see what's relevant to them, and admins can manage permissions at scale instead of one user at a time. **Territories:** Every user should have a territory that reflects their book of business. Territories filter feeds, email digests, and bridges by default — so reps aren't looking at signals for accounts that aren't theirs. Territories can be synced automatically from your CRM. **CRM integration:** Connecting Salesforce or HubSpot unlocks the most powerful parts of Starbridge: account matching, CRM-synced buyer lists and territories, and the ability to push enriched contacts, account scores, and signals back into your CRM. ## Recommended setup order This is a high-level description. Specific articles document each step in detail. Go to **Settings → Organization Profile** and fill in your Organization Description and Organization Business Context. This is the foundation for all AI-generated content in Starbridge. Go to **Settings → Integrations** and connect Salesforce or HubSpot. Select the objects and fields you want Starbridge to access. The **Objects and fields** experience recommends objects and fields to enable for various use cases, like account scoring or contact enrichment. See [Connect your CRM](/admins/connecting-your-crm) for setup guidance. Map your CRM accounts to Starbridge buyers. This is the foundation for CRM-synced territories, buyer lists, and pushing data to and from your CRM in bridges. See [Account matching](/integrations/account-matching) to get started. Add your users, assign roles, and organize them into teams. Builders can create and edit bridges; Consumers can view and action signals. Teams make it easy to subscribe groups of reps to the right bridges in one step. See [Users & roles](/admins/adding-new-users-configuring-roles-and-teams-s) for setup guidance. Many teams prefer to build out their key bridges and populate signals in the feed before adding reps to the platform — so there's something to see on day one. [Chat with your CSA](mailto:support@starbridge.ai) about the right time to bring your team on. Assign a territory to every user so their feed and email digest are filtered to their book of business from the start. See [Set up territories](/admins/setting-up-your-workspace/setup-territories) for guidance on territories and how to sync them from your CRM. ## Monitoring your team Once your team is live, the [Usage Dashboard](/admins/usage-dashboard) gives you a view of who's active, how many signals are being reviewed and acted on, and how individual users are contributing — filterable by team, role, and date range, and exportable as CSV. ## Next steps Fill in your org business context to customize Starbridge's AI-generated content and analysis for your team\` Watch the admin training walkthrough to see platform configuration end to end. # Example Organization Business Context Source: https://hc.starbridge.ai/admins/setting-up-your-workspace/example-organization-business-context-to-fill-out This page is a template. Copy it into your organization profile (or use it as a worksheet) and replace the placeholders with your company-specific details. ## One-sentence description One sentence describing what the company does, who it serves, and its core value proposition. ## The core problems we solve * Problem statement 1 * Problem statement 2 * Problem statement 3 * Problem statement 4 * Problem statement 5 * Problem statement 6 Brief paragraph describing how the company addresses these problems—mention core platform, approach, or technology differentiators. ## What it feels like to use the product ### For line-of-business / admins Describe the administrative or leadership experience—dashboards, reporting, insights, control, decision-making benefits. ### For end users / practitioners Describe the day-to-day experience of users—workflow improvements, AI tools, usability, impact on workload. ### For IT / operations Describe the technical setup and benefits—integrations, automation, compliance, interoperability. ### For support / success teams Describe support channels and resources—chat, email, help center, onboarding, training. ## Product modules and integrations ### Products * **Product name:** Short description of what it does and key differentiator. * **Product name:** Description of core purpose, audience, or outcomes. * **Product name:** Description of additional functionality or specialized use case. * **Partner products or integrations:** Summary of key partnerships or systems integrated into the platform. ### Services * **Professional learning / implementation:** Overview of onboarding, training, or coaching services. * **Customer support:** Overview of support channels and service levels. * **Materials and delivery:** Description of digital, print, or hybrid delivery options. ## Target buyer roles and contact titles * Superintendent / district leadership * Chief academic officer * Principal / school leadership * Director of curriculum * Instructional coach * Teacher * Other relevant buyer or influencer roles ## Customer use cases (real stories) ### Example 1 **Customer:** Name of organization or district **Segment:** Type of organization or grade range **Region:** Geographic area **Year:** Implementation or publication year **Product/modules used:** List of product modules **Integrations leveraged:** List of integrations or partners used **Measurable outcomes:** Quantitative or qualitative results ### Example 2 **Customer:** Additional story (if available) ## Why decision-makers choose us over the alternatives * Key differentiator or award * Validation or third-party recognition * State-level approval or certification * Integrated AI or automation features * Breadth of content or curriculum partnerships * Exceptional support or customer experience * Technical interoperability or compliance advantages ## Competitors * Competitor 1 * Competitor 2 * Competitor 3 * Competitor 4 * Competitor 5 ## Customers * Notable customer 1 * Notable customer 2 * Notable customer 3 ## Segments * **Primary vertical:** Example — K-12 Education, Higher Education, Workforce Training * **Organization types:** Example — Public schools, private institutions, districts * **Size bands:** Example — Serves districts of all sizes or specific enrollment ranges * **Geographies:** Example — United States, global, specific states or regions ## Market focus * **Fit by offering:** Overview of how the product aligns with market needs. * **Segments and size bands:** Overview of target markets and scale served. * **Operating environments:** Typical integrations and compatible systems. * **Compliance and authorizations:** Certifications, data privacy, and accessibility standards met. * **Contract vehicles and channels:** How the company sells (direct, RFP, partners). * **Geography and language:** Operating markets and language availability. * **Delivery models:** SaaS, hybrid, or print-based components. * **In-scope:** Summary of core product functions (e.g., curriculum, analytics, instruction, AI tools). ## The result Brief description of measurable or reported outcomes—include performance metrics, engagement results, or efficiency gains. ## References * Official website: \[link] * About page: \[link] * Case study or press release: \[link] * Third-party review or certification: \[link] * Partnerships page: \[link] # Set up territories Source: https://hc.starbridge.ai/admins/setting-up-your-workspace/setup-territories ## Overview A territory in Starbridge controls which buyers a user sees signals for — in their feed, their email digest, and across bridges. Every user should have a territory that reflects their book of business. Once a territory is set, Starbridge filters every view to that user's accounts by default. Their feed surfaces signals only from buyers in thier territory. Their email digest covers only their accounts. When they open a bridge, results are scoped to their territory. Reps can research or ask questions about any buyer, regardless of their territory — but the default keeps the noise out so reps start every session focused on what matters to them. There are two ways to set up territories in Starbridge, and they're not mutually exclusive. Most organizations use one or both depending on the role. ## The two approaches ### Account ownership territories Starbridge reads account ownership directly from your CRM accounts and automatically maintains a territory for each rep. When accounts are reassigned in your CRM, territories in Starbridge update automatically overnight. **Use this when** a user's territory is defined by who owns an account in the CRM — for example, an Account Owner, BDR Owner, or SDR Account Owner field on the account object. This is the right approach any time territory = "accounts where this person is listed as the owner." This approach requires account matching (linking your CRM accounts to Starbridge buyers) and user matching (linking your CRM users to Starbridge users) before territories can be generated. See [Account matching](/integrations/account-matching) and [CRM-synced territories](/integrations/crm-territories) for setup details. ### Buyer list territories Assign a [buyer list](/builders/how-to-create-a-buyer-list) to a user as their territory. **Use this when** a user's territory is best described as "a specific list of accounts" rather than "accounts assigned to them in the CRM." Buyer list territories can sync dynamically from your CRM, or can be defined geographically or in terms of buyer attributes when territory boundaries are stable or defined outside your CRM. Buyer lists come in three forms: * **Dynamic list** — built using Starbridge filters (state, buyer type, enrollment, budget, etc.). Updates automatically as Starbridge's data changes, but does not reflect CRM ownership. * **Static list** — a fixed list of accounts. Good when you know exactly what accounts should be in the list. * **CRM-synced list** — created directly from a Salesforce List View or HubSpot Segment (List). The accounts in the Starbridge list reflect the accounts in your CRM list; use the Resync button to pull in changes. Good when your territory definition already exists as a list in your CRM. See [CRM-Synced Buyer Lists](/integrations/crm-synced-buyer-lists). To assign a buyer list as a user's territory: create the buyer list, then go to [**Settings > Users**](https://dashboard.starbridge.ai/settings/users), select the user, click **Edit territory**, and select the buyer list to assign as their territory. Screenshot 2026 06 08 At 1 15 06 PM ## How to choose | | Account ownership territory | Buyer list territory | | :------------------------------------------------------------------------------ | :-------------------------- | :------------------- | | Territory is defined by CRM account ownership ('Account Owner'-type fields) | ✓ | | | Territory updates automatically when CRM changes | ✓ | ✓ | | Territory is a fixed or manually maintained list | | ✓ | | Territory is defined by region, segment, or Starbridge filters | | ✓ | | No CRM integration, or territories are defined in your CRM as lists of accounts | | ✓ | The two approaches aren't mutually exclusive — each user can only have one territory, but different users on the same team can use different approaches (account ownership versus buyer list). ## Examples **Marketing or enablement roles** often benefit from a buyer list rather than a CRM-synced territory. A marketing manager focused on a specific segment — say, higher ed institutions above 10,000 enrollment — can use a dynamic buyer list filtered by enrollment, regardless of how accounts are assigned in the CRM. **Regional sales reps** can go either way. If their CRM accounts are assigned by region and ownership is tracked there, CRM sync works well. If their territory is simply "all accounts in these states," a dynamic buyer list filtered by state is often simpler to set up and maintain. **BDRs with individually assigned accounts** are a strong fit for CRM-synced territories, especially when account assignments change frequently via round-robin or re-assignment. Since their territory is exactly "the accounts assigned to me in the CRM," syncing directly from the CRM ownership field keeps Starbridge current automatically. **Mixed teams** are common. For example: sales reps with regional territories use dynamic buyer lists filtered by state, while BDRs with individually assigned accounts use CRM-synced territories. Both approaches coexist — you just configure each user's territory the right way for their role. ## Changing a user's territory Admins can change any user's territory from the **Users** page by selecting a different buyer list or switching to an account ownership territory. Users with a Builder role can also change their own territory from their **My Territory** page. # Usage Dashboard Source: https://hc.starbridge.ai/admins/usage-dashboard ## Overview The Usage Dashboard gives you a view of how your team is using Starbridge — who's active, how many signals are being reviewed and acted on, and how individual users are contributing — all filterable by date range and exportable as CSV. The dashboard is only visible to Admins. Image ## Accessing the dashboard Go to **Usage Dashboard** in the left navigation. ## Summary tiles At the top of the dashboard, three tiles show team-wide totals for the selected date range: * **Active users** — the number of unique users who visited any page or sent a message to Ask Starbridge via Starbridge or Slack in the period * **Signals reviewed** — signals any user opened or to which they applied any status (Actioned, Starred, Not interested, Needs action); deduplicated by signal across users * **Signals actioned** — signals any user marked as Actioned, Starred, Not interested, or Needs action; deduplicated by signal across users * **Chat questions asked** — questions sent by any user to Ask Starbridge. Includes Ask Starbridge from any tab/surface in the product and Ask Starbridge via Slack integration, if installed for your organization. Use the **date range picker** in the top right to switch between **Last 7 days**, **Last 30 days**, **Last 3 months**, or **Last 6 months**. All summary tiles update to reflect the selected period. Image ## Team activity table The Team Activity table shows one row per user and includes: * **Name** — the user's full name * **Teams** — tags showing the user's assigned teams, sorted alphabetically; the role tag (Consumer, Builder, or Admin) always appears last * **Activity this week** — a day-by-day breakdown of the past 7 days showing which days the user was active, with a total count (0–7); only visible when **Last 7 days** is selected * **Last active** — the date the user was last active in Starbridge; always current and not affected by the date range filter * **Sessions** — total sessions in the selected date range; a session is defined as any signal metric produced within a 60-minute window * **Signals reviewed** — signals this user opened or to which they applied any status (Actioned, Starred, Not interested, Needs action) in the selected date range * **Signals actioned** — signals this user marked as Actioned, Starred, Not interested, or Needs action in the selected date range * **Chat sessions** — unique chat sessions initiated by this user with Ask Starbridge. E.g., each time a user starts a new chat or clicks 'New chat', this initiates a new chat session. * **Chat questions asked** — questions sent by this user to Ask Starbridge. Includes Ask Starbridge from any tab/surface in the product and Ask Starbridge via Slack integration, if installed for your organization. The table defaults to alphabetical order by first name (A–Z). ### Sorting Click any column header to sort by that column. Activating a new sort clears any existing sort. Click the same header again to reverse the direction. ### Filtering Use the **Team** and **Role** dropdowns above the table to filter the list to specific segments. Both filters support multi-select. ### Searching Use the **search field** to find a specific user by name. The search is case-insensitive and hides rows that don't match. ## Exporting data Click **Export** to download CSV files: * **Summary file** — the team-wide totals shown in the summary tiles * **Team activity file** — the full per-user table with all columns ## A note on historical data Analytics tracking begins when the dashboard goes live. Last 7 days, Last 30 days, Last 3 months, and Last 6 months will become available as your team accumulates usage history over time. ## Related articles Watch the full admin setup walkthrough in the platform. Add users, assign roles, and create teams for your organization. # Video walkthrough Source: https://hc.starbridge.ai/admins/video-walkthrough Watch this admin training walkthrough to learn how to configure organization settings, manage users, and set up the platform for your team.