Changelog

The Site.nu top bar now shows who is active in your workspace. Open it to see who is online, who is on the same page and who is working elsewhere.

One teammate with several browser tabs appears once, so the list reflects people instead of open connections. When someone goes offline, their last-seen time remains available for handoffs.

Enough context to coordinate

Presence shows whether someone is online and which area of Site.nu they are working in. The exact record or open route stays private. This tells you who to contact when you need to coordinate, without Site.nu tracking every step your teammates take.

Live workspace presence is available in the Site.nu app for workspace members.

The Site.nu Shopify app brings commerce context into the CRM without flattening it into generic contacts and notes.

Commerce data that stays recognizable

Customers, orders, order lines, products and sync runs remain recognizable Shopify records. Identity review helps connect them to the right people and companies, while uncertain matches wait for someone to check them.

• Imports can resume after an interruption, and sync history shows where a connection needs attention.
• Shopify products can be selected in Campaigns with their image, price and destination.
• Marketing consent received from Shopify is added to the consent history of the matching email address.

The app is available from Site.nu Applications. The records and actions it can access depend on the permissions granted by the connected Shopify store.

Start an Agent, then close the tab. The run keeps going and stays visible in Agent activity while the work progresses.

Runs can start manually, on a schedule, from a record event or inside a Workflow. Each one keeps its own state, can be cancelled or retried, and records the Agent revision and authority used for the assignment.

A clear place to intervene

Longer work needs a clear status and a way back in when something needs attention. A run can pause before a consequential action, wait for human approval and continue after the decision. Research and recommendations stay separate from changes to CRM data.

Durable Agent runs are currently in a controlled pilot. Access and supported specialists are enabled per workspace while the remaining rollout checks are completed.

One person can have several email addresses, and each address can have a different consent history. Site.nu now checks the address that will receive the campaign instead of relying on one generic subscribed field on the person.

Permission follows the inbox

Accepted and withdrawn consent is recorded against the exact address involved. The history keeps the source, timestamp and the form or provider that supplied the signal. If conflicting events share a timestamp, a withdrawal takes precedence.

This makes campaign eligibility easier to explain and prevents permission for one inbox from carrying over to another. It also gives teams a direct answer when someone asks what they agreed to and where that evidence came from.

Address-level consent is active across Site.nu CRM and Campaigns. Existing consent records still contribute to eligibility while teams add more explicit evidence.

Campaign work tends to move back and forth between the message, audience rules and delivery checks. The revised workspace keeps those parts close instead of making you rebuild the context at every step.

Overview, Audience and Editor give each stage a clear place. The campaign library is easier to scan, while the editor keeps content tools and validation beside the message you are building.

• Start with a branded template and assemble the message from reusable email blocks.
• Preview responsive output, send a test and resolve validation issues before approval.
• Review the audience and delivery settings without losing your place in the editor.

The updated workspace is available in Site.nu Marketing. Sending still follows workspace permissions, consent eligibility and the configured email delivery setup.

Every workspace now has a private Asset Library for images, documents and other approved file types. Upload a file once, find it through its metadata and reuse it wherever Site.nu accepts an asset.

Use the same asset where the work happens

• Pick workspace assets from Campaigns, Brand Profiles, record attachments and Agent chats.
• Check where a file is used before moving it to Trash, and restore it when needed.
• Upload large files in resumable parts instead of starting over after an interruption.

Private by default

Assets stay private until a channel needs a published rendition. PDFs remain in quarantine until malware scanning is complete, and removed files remain recoverable. That gives each file a clear lifecycle without treating every upload as public.

Asset Library is available from the Site.nu sidebar. Access follows workspace membership and the permissions of each destination.

A CRM day often starts with orientation: what needs attention, where is the right record and which tool should open next? Home now puts that starting context in one place.

Upcoming calls, connected apps and suggested actions sit alongside a direct place to ask Site.nu for help. The useful next step is closer, without turning Home into another dashboard to manage.

Navigation that matches the workspace

Each workspace can choose which product areas and CRM objects appear in the sidebar. Search opens from there or with the command shortcut, so records and tools remain quick to reach even as the workspace grows.

The refreshed Home, customizable navigation and sidebar command menu are available in the Site.nu app.

Page views show what was seen. Website Analytics now adds the journey around them: how someone arrived, what they did next and where the visit converted or stopped.

Follow the whole visit

• Explore pages, sources, locations, realtime activity, individual visits and journeys across several pages.
• Define conversion goals and compare first-touch with last-touch attribution.
• Inspect form funnels, interactions and Core Web Vitals alongside traffic.

Anonymous visits stay in analytics. Identified form submissions and other explicit handoffs can continue into the CRM when appropriate, without turning every tracking event into a CRM record.

The expanded views are available for connected Site.nu websites. Results depend on the tracking setup, selected period and configured goals.