Skip to main content

Activity Capture Configurations: Modes, Teams and Enrolment

What an Activity Capture configuration is, the fully automated, hybrid and manual logging modes, and how teams and users are enrolled in each.

An Activity Capture configuration is a set of logging rules applied to a group of users: what Weflow logs, to which Salesforce objects, and what it leaves out.

You can run as many configurations as you have teams or regions, so a sales team and a customer success team can log to different objects without one team's rules leaking into the other's. Each user belongs to exactly one configuration.

What an Activity Capture configuration controls

Each configuration has nine tabs under Admin Console > Activity Capture:

Tab

What it decides

General settings

Email and calendar logging, logging object

Users & teams

Who the configuration covers

Exclude emails

Internal and external domains left out

Object management

Objects activity can log to

Contact creation

Whether and when contacts are created

Expert settings

Delays, matching and add-in behaviour

Custom rules

Addresses and records blocked

Tracking

Email open tracking

Configuration

Deleting the configuration

Learn more about each setting in the Admin Guide to Setting Up Activity Capture.

Activity Capture modes: fully automated, hybrid and manual

Every configuration runs in one of three modes. The mode decides what your reps can do, and most customers run hybrid.

Mode

How emails are logged

Typical team

Fully automated

Server-side, no rep action

Individual contributors

Hybrid

Server-side, reps see and adjust

Most teams

Fully manual

Only what a person logs

Leadership

  • Fully automated: Email Background Logging in General settings is on, and Weflow logs every matching email and meeting from the mail server.

  • Hybrid: background logging stays on, and reps use the Outlook Add-In or Chrome Extension. The add-in shows which record a message is about to log to, lets the rep re-map it, and carries a tick that switches logging off for that thread.

  • Fully manual: background logging is off. A rep opts a thread in from the Chrome Extension, and from then on Weflow logs every message in that thread. With Unchecked by default in Expert settings, the add-in's Log to Salesforce option starts unticked, so an email is logged only if the rep ticks it before sending.

Email and calendar are separate switches: a team can turn email logging off and keep logging its meetings and creating contacts from meeting attendees.

How Activity Capture configurations use teams

A configuration covers teams or individual users, and teams are the practical unit: a person added to a team picks up that team's configuration.

  • Manual selection: you add and remove people one by one.

  • Dynamic selection: filters and conditions build the team from Salesforce, by manager, role or a field condition. A rep who moves team in Salesforce moves in Weflow automatically. A team can follow a checkbox on the Salesforce user record, so you switch Activity Capture on or off for a person in Salesforce, and Weflow picks it up within the hour.

  • Admin-only team: a team hidden from end users and used only to scope configurations.

How to enrol users in an Activity Capture configuration

Enrolling a user is what starts capture: Weflow reads no mailbox until a user is in a configuration.

  1. Go to Admin Console > Activity Capture and open the configuration.

  2. Select the Users & teams tab.

  3. Choose Teams or Users in the selector.

  4. Click the plus button next to each team or user. They appear in the Active column.

  5. Click Save changes.

Users & teams tab of a Weflow Activity Capture configuration: the Teams list with plus buttons and the Active column of covered users
  • No sign-in needed: an enrolled user is captured whether or not they ever sign in to Weflow. A user shown as Pending in the user list is still captured.

  • One Salesforce user per mailbox: Weflow pairs each mailbox with one Salesforce user, on the email address of the Salesforce user record. A mailbox with no Salesforce user behind it is not synced.

  • Licences: Activity Capture licences are assigned here, inside Activity Capture, not from the main user list.

Note: the user must also be inside the scope of the Weflow Activity Capture app in Google Workspace or Microsoft Entra ID. A user outside it shows a warning icon and logs nothing.

How Activity Capture applies rules across several configurations

When an email or meeting involves users from several configurations, Weflow logs it under the most permissive of their rules.

  • Executives: a configuration for leadership can be set to manual logging, or block contacts of a given role or investor domains. When an executive emails a customer together with sales reps, the sales configuration applies and the thread is logged.

  • Support teams: with Case logging on, a matching Case takes priority over an opportunity or account. Giving support its own configuration keeps a sales team's emails on the deal.

Frequently asked questions about Activity Capture configurations

Do users in an Activity Capture configuration need to sign in to Weflow?

No. Capture connects to the mailbox server to server, so enrolled users are captured without a Weflow login. Signing in is needed only for what they use in the app.

What happens to logged activity when I remove a user from a configuration?

It stays in Salesforce. Adding the user back, or running a historical sync-back, does not create duplicates.

Does a historical sync-back follow the configuration?

Yes. A sync-back runs for users enrolled in a configuration and applies its exclusions, custom rules and object settings, so finish the configuration before it starts.

Can Microsoft 365 and Google Workspace users share one Activity Capture configuration?

No. Each mail provider needs its own configuration. A company with users on both Microsoft 365 and Google Workspace runs two configurations, one per provider, in the same Weflow workspace and connected to the same Salesforce org.

Can one Weflow workspace cover two Salesforce orgs?

No. A workspace connects to one Salesforce org, so two production orgs need two Weflow workspaces, with the teams split between them.

Did this answer your question?