Objective
Applies To
- Outreach Admins
- Outreach Users
Overview
Introduction
Setup
CRM Enablement
Outreach recommends you always select all three permissions. |
Advanced considerations
For all customers we recommend you always select permissions to create, update and delete Account Teams from Salesforce to Outreach. This ensures that your Account Teams in Outreach is always up to date with your Account Teams in Salesforce.
In specific cases you can choose to temporarily disable a combination of the three permissions but we recommend you enable the permissions again as soon as possible.
One example scenario is when your company is going through a re-organization, or you're reshuffling your Account Teams, and you have already set up Content Governance with Account Teams. In this case you might want to disable delete temporarily while you finish your re-organization to keep the content associations as-is. Make sure you check all three permissions once your re-organization is complete.
Account Object - Advanced Setting Option
Create associated contacts and account teams when syncing into Outreach: When this setting is enabled, it allows Outreach to create Contacts and Account Teams whenever an Account is Created or Updated in Salesforce.
*By Enabling this feature, it may use more API Calls. Learn More about Outreach API call usage.
Account Team Member Object Fields
| Outreach Field | Field Type | Details | Recommended | Advanced Settings Required |
| Access Level | String |
Determines the Member’s level of access to the Account *Permission Details listed in the FAQ below |
Yes | none |
| Account | Reference | Lookup field to the Account object | Yes | Yes (Enable Mapped Field and Select the Account object that field maps to) |
| Account Id | Number | Outreach Account Id | No | none |
| Created At | datetime | The date and time the account team was created | No | none |
| Id (Outreach internal) | Number | Outreach Account Id | No | none |
| Job Role Name | String |
Map to Team Role SFDC field *Job Role Picklist values will automatically be created in Outreach as members sync in on Accounts |
Yes | none |
| Title | String | The member’s title in SFDC | No | none |
| Updated At | datetime | The date and time the Account Team Member was last updated | No | none |
| User | Reference | Lookup Field to the User Object that references the Outreach User that is part of the Account Team Members | Yes | Yes (Enable Mapped Field and Select the User object that field maps to) |
| User Id | Number | Outreach User Id | No | none |
Content permissions
Content Governance
End User Experience
Account Sidebar
Assigned Collaborators
Job Roles
- For CRM users, their Job Role is equivalent to their Salesforce Account Team Membership Role. These can be different for different Account Teams.
- For Outreach users, their Job Roles are the ones explicitly assigned to them by their Admins (by going to Administration > Users & permissions > Job Roles). These users have the same Job Role across all Accounts they are assigned to.
Transferring ownership
List View Filtering
The account list view can be further filtered by Account Team and Job Role. Details on usage are available here.
FAQs
What permissions are assigned to the Account Team members?
Outreach supports Salesforce’s none, read and edit permissions assigned to Account Team members in Salesforce through Saleforce’s Field Level Security. Permissions in Salesforce can extend existing user permissions in Outreach but cannot take away permissions.
Account team members with Salesforce’s (please also check the next FAQ to fully understand more on how these permissions interplay with Outreach permissions):
- ‘None’ permission will not be able to access the record unless granted permission through Outreach. However, other members in the Account Team will be able to see that the user is associated with the record.
- ‘Read’ permission will be able to access the record, but not edit any details unless granted permission through Outreach. They can see other members associated with the record and vice versa.
- ‘Write’ permission will be able to access the record, and edit it. They can see other members associated with the record and vice versa.
The above permissions are applied to any existing Outreach users that are now associated with Account Teams. Account Team members however cannot change membership to the Account Team.
The above permissions are also applied automatically to any users who were not already using Outreach but were created via the Account Team sync. These new users are assigned the ‘Default’ Profile automatically. However, to access Outreach, these new users will need to be assigned licenses, just like you would, with any new Outreach users.
How do the Account Team permissions interplay with Profile and Multi-User Assignment permissions?
Whenever a user tries to access a record, Outreach automatically evaluates all permissions the user potentially has to the record, including through Profiles, Multi-User Assignment and Account Teams (if enabled on the instance). As a result of this evaluation, the user is then given the maximum permission afforded to them through any of these features.
The only exception is if the user’s Profile explicitly denies permission (Record permission set to ‘None’). Outreach will respect the denial irrespective of what permissions the user has via Multi-User Assignment or Account Teams.
Note that the above doesn’t include ‘Admin’ Profile which is a superseding profile and always has access to all Records.
What if I want to change the default permissions?
In this release, it is not allowed to change any default permissions including the auto-assignment of the ‘Default’ profile. You can however manually change the user Profile once they are available in Outreach
Can I create Account Teams manually inside Outreach only?
Yes. You can use Multi-User Assignment if you want to manage Account membership and Multi-User Assignment APIs to manage users automatically.
Can I manually manage Salesforce Account Team membership inside Outreach?
No. We are only supporting forward sync only at the moment. Account Team members with Edit permissions are allowed to add additional members on top of the Salesforce membership if you have enabled Multi-User Assignment. They cannot however remove any member who have been synced in as part of Salesforce Account Teams membership.
Does this replace Multi-User Assignment?
No. Existing Multi-User Assignment customers can continue to use their existing setup. However note the change in the user experience described above. New customers are encouraged to use Team Selling experience for Accounts.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article