Release 2.7.6
This release is about seeing what your advocates see and moving the right signals to where your teams work. Admins get a one-click lens into any advocate’s live portal, community rewards reach Discord, referenceability search finally shows per-activity eligibility, and two more objects — references and nominations — can flow out through Data Sync. Plus five quality-of-life touches that clear up everyday friction.
See the portal exactly as an advocate sees it
From an advocate’s info card or their row on the Advocates dashboard, admins can now choose View portal as advocate and land in that advocate’s portal in a new tab — their asks, points, rewards balance, level, leaderboard position, and your branding and language, rendered exactly as they see it. No logging in as them, no asking for a screenshot.
Admins configure asks, rewards, and portal branding for different segments of advocates — but had no way to confirm what any one advocate actually sees. The workarounds were clumsy: invite yourself in as a fake advocate, or ask the customer to send screenshots.
Targeting and personalization are only as good as what actually renders on the advocate’s screen. A one-click lens into any advocate’s real portal turns “I think this segment sees the right asks” into “I can see exactly what they see” — faster QA, more confident configuration, and sharper support conversations.
Open any advocate’s info card — or their row on the Advocates dashboard — open the actions menu, and choose View portal as advocate. The portal opens in a new tab with a banner across the top; click Exit view to end it. Your own admin session in the original tab is untouched.
It’s read-only by design: every action is turned off, so nothing you click can submit an ask, redeem a reward, or send the advocate a notification. The advocate is never told they were viewed, and the visit leaves no trace in your reports — no view counts, no last-seen change, no engagement movement (the one record is an Audit Log entry noting who viewed whom). Community and Halo rewards show but can’t be entered in view mode, since they open as authenticated exits.
Re-add an advocate to the reference pool after they’ve declined
On an advocate’s Activities consents, the Join reference pool toggle is usable again after the advocate declined. An admin can switch it back on — behind a confirmation step — to add that advocate into the reference pool once more.
Once an advocate answered “No, thanks” to the join-the-reference-pool ask, that choice was treated as final: the toggle greyed out permanently, with no way to reverse it — even when the advocate later changed their mind, or the “No, thanks” was a misclick. It was also inconsistent — advocates you removed or paused could already be re-added; only the advocate’s own refusal was stuck.
People change their minds, and mistakes happen. Admins should be able to honor an advocate’s updated decision without opening a support ticket — while still respecting that joining the pool is a consent action.
On the advocate’s Activities consents tab, switch Join reference pool on. A confirmation appears — confirm to re-add them using the standard frequency selection, and they reappear in the reference pool and reference locator like any other member. Cancel, and nothing is written.
The confirmation is deliberate: joining the pool means the advocate can be surfaced as a sales reference, so the guardrail stays — it just no longer blocks a legitimate re-add. The existing permission rule is unchanged; admins without update permission still can’t change it.
Reward community engagement in Discord
Discord joins Base as a native community integration. Connect a Discord server, and advocates earn the points you set when they engage there — posting, replying, reacting, or being mentioned — using the same rewards model and configuration as your existing community integration.
Community rewards only worked for one community tool. Teams running their community in Discord had no native way to recognize that activity in Base — it lived entirely outside the advocate’s points and engagement.
Discord is where many customer communities actually happen. Rewarding real participation there — not just showing up — pulls that engagement into the same advocacy program you run everywhere else, so your most active community members are recognized wherever they contribute.
Under Settings → Integrations, connect your Discord server, choose the contact attribute that holds each advocate’s Discord username, then turn each action on and set its points. When a matched advocate performs a supported action in the connected server, they earn the configured points wherever community points already appear.
Advocates are matched by the Discord-username attribute you map (Discord doesn’t expose email), so anyone with no value there simply isn’t matched — and nothing errors. The same action never earns points twice, even across a brief interruption in the connection. Joining the server isn’t rewarded, matching community rewards today.
See consent, frequency, and availability per activity
When you filter the Referenceability Search to specific activity types, the results now show three columns for each activity — whether the advocate consented to it, their personal frequency for it, and whether they’re available for it right now. The data already existed per advocate; now it’s on screen where you choose.
Filtering by an activity type only narrowed the pool to advocates “involved with” it — you couldn’t tell from the results whether a person actually opted in, how often they’re willing, or whether they were simply asked once. Consent only surfaced as a soft warning after someone had already been picked.
Choosing a reference is a judgment call you want to make up front, not after. Seeing consent, cadence, and current availability directly in the results means you pick someone genuinely eligible the first time — fewer awkward asks, and more respect for each advocate’s stated preferences.
Filter the Referenceability Search to one or more specific activity types. The three columns appear for each selected activity and behave like the report’s other columns — sortable, show/hide via the Columns control, and included in the CSV export.
Columns appear based on what each activity requires — consent for activities that need it, frequency for those with a cadence, and availability once consent applies. When an advocate isn’t available yet, the column indicates when they’re due again.
Two more objects flow out through Data Sync
The references your advocates deliver and the nominations your team submits can now sync from Base to your destination — each source-only, one row at a time, exactly like Activities.
Sync delivered references to your destination
References Provided — the delivered-reference and reference-call records — is now a source-only Data Sync object. Push each delivered reference out to your warehouse or CRM, one row per reference, mirroring how Activities syncs today.
Delivered references are among the highest-value signals in advocacy — proof that an advocate actually took a sales call. Getting them into your CRM or warehouse lets revenue and ops teams tie advocacy directly to pipeline and closed deals.
When Base is the source, add References Provided as an object to a sync job. Each row carries the reference’s name, status, contact/meeting date, and lead-became-customer outcome, plus links (by id) to the advocate, opportunity, opportunity contact, account, reference type, and the matching Reference Request.
It’s source-only — read out of Base, never written back or offered as a destination object. Linked records carry as identifiers; their names come from the Advocate, Opportunity, and Account objects you’re already syncing.
Sync nominations to your destination
Nominations is now a source-only Data Sync object. Every nomination — who was put forward, by whom, and where it stands — can flow out to your destination, one row per nomination, the same way Activities does.
Nominations are where advocacy begins — a salesperson flagging a happy customer. Syncing them out means the whole lifecycle, from nomination to delivered reference, is visible in the systems your teams already live in.
When Base is the source, add Nominations to a sync job. Each row carries the nominated person (by advocate id) and their account, who nominated them (name and email), the reason, current status, type and source, the related ask where present, and the created / updated / status-changed dates.
Source-only, like Activities — never written back into Base. The nominated advocate’s name and email come from joining to the Advocate object you already sync, so no new data points are introduced.
Quality-of-life improvements
Five smaller changes that take friction out of everyday work — from filtering and editing asks, to reports that search and explain themselves, to pulling Salesforce in on demand.
Filter by more than one status at once
The status filter on the Asks dashboard is now multi-select — pick any combination of Active, Pending, Draft, and Archived and see (and total) them together. It now matches the ask type, tags, and audience filters on the same panel, which were already multi-select.
Open the status filter and check any combination of statuses. It defaults to Active on first load — the same view as today — and clearing it shows asks of every status.
Edit and Clone open in a new tab
From a row’s actions menu, Edit and Clone now open the ask editor in a new browser tab instead of replacing the dashboard. Your list — filters, search, sort, and scroll position — stays exactly where you left it.
Choose Edit or Clone from any row’s actions menu. The editor opens in a focused new tab; close it to return to your dashboard, untouched. Open as many asks as you like, each in its own tab.
Search now matches every column you can see
On the Referenceable content and Marketing Requests reports, the search box now matches any text or category column shown in the table — so a value that’s visible on screen actually returns a result. Previously each search only looked at a subset of columns (searching an Ask name in Referenceable content, for instance, returned nothing).
Just search as before. On Referenceable content, Ask name now matches consistently (regardless of filter or sort), alongside Classification, Content ranking, and Seniority level; on Marketing Requests, Activity name, Request details, Status, and Assigned to are all searched.
A clearer message when a date range returns nothing
When an Ask report comes back empty because the selected date range excluded everything, it now says so plainly — “No results match your current filters. Try adjusting the date range to see results.” — instead of a bare “No data available” that read like the report was broken.
Nothing to configure. When a report loads with zero results for the chosen dates, the new message points you at the date range rather than leaving you to guess.
Pull Salesforce changes in on demand
The Salesforce / CRM panel now has a Sync now button. The Salesforce sync already runs automatically every few hours; Sync now lets an admin pull accounts and advocates in early — right after making a change in Salesforce — instead of waiting for the next scheduled run.
On the Salesforce / CRM integration panel — visible when a CRM is connected — click Sync now. The sync starts in the background (“Sync started — your data will refresh shortly”) without freezing the page.
It’s limited to once every 24 hours across the whole account; within that window the button is disabled and shows when it’s next available. Admins without the right permission don’t see it.