CRM COLLABORATION
Put the right colleagues around the customer record.
Review account-team assignments for contacts, companies and deals, with explicit lead, collaborator and read-only roles.
Account team · Studio Nord
Review changes at the level where the membership is assigned.
Customer collaboration needs more than a name in the owner field
One colleague may lead the relationship, another prepares a proposal and a third only needs to read the background. A single ownership label does not describe those differences. Tsumira’s account-team surface makes record-specific collaboration visible and gives authorized managers a review step when assigning or removing members. It helps the team understand who is involved without treating every participant as having the same role.
Choose a role that fits the person’s involvement
The account-team roles are lead, collaborator and read-only. They distinguish responsibility from participation and reading. The surface is available for supported contact, company and deal records, keeping the collaboration connected to the actual customer work. Before assigning someone, consider whether they are leading the account, actively helping or simply need context. Organization membership by itself is not a substitute for reviewing the relevant record role.
- Lead, collaborator and read-only roles
- Contact, company and deal targets
- Record-specific team membership
See inherited membership as well as direct assignments
The account-team view distinguishes a direct assignment from membership inherited through a company. This explains why a person appears on a related record and avoids presenting every seat as if it had been independently added there. Inherited members are not removed through the same local control as a direct assignment. Review the company context when the displayed membership comes from that level, rather than trying to solve it on the wrong record.
- Visible company-inherited membership
- Direct assignments kept distinct
- Changes made at the appropriate level
Review changes at the level where the membership is assigned.
Review changes before applying them
Managing account teams requires the relevant permission. The interface first prepares an assignment or removal for review, shows the selected person and role, and asks for confirmation before applying it. A lead-role change deserves particular attention because it affects account responsibility. The same business boundary applies when AI proposes a team change: a proposal should be reviewed instead of becoming an unnoticed access or responsibility update.
- Separate management permission
- Review and confirmation step
- Visible effect of lead-role changes
A concrete workflow
Open the relevant record
Choose the company, contact or deal whose team needs to change. Read the existing members and any inherited assignments.
Select the intended involvement
Choose an eligible member and the lead, collaborator or read-only role that fits the work.
Review the proposed change
Check the person, record and role, including the responsibility effect of a lead assignment.
Confirm and verify
Apply the reviewed change with the appropriate permission, then inspect the resulting account team.
An illustrative working example
Illustrative workflow: bring a specialist into a proposal
An account lead asks a specialist to help scope a customer proposal. The authorized manager opens the relevant company or deal, checks the existing account team and prepares the specialist’s collaborator assignment. Another colleague who only needs background is considered for read-only involvement. The manager reviews the intended roles before confirming, while a company-inherited member is recognized as coming from the wider company context.
Questions about this topic
Which roles are available?
The supported account-team roles are lead, collaborator and read-only. Select the role that corresponds to responsibility, active participation or reading.
Is the record owner the complete account team?
No. Ownership and account-team membership describe related but distinct information. The team surface shows additional participating members and their roles.
Why can a member be marked as inherited?
Their involvement comes through the company context. The interface distinguishes it from a direct assignment so changes can be considered at the appropriate level.
Can AI silently add someone to an account team?
Team changes are permission-controlled business actions. Proposed assignments should go through review before application; asking AI does not create a new right to manage access.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Microsoft Teams
Workflow concept: Prepare an account handover naming the lead and responsible collaborators.
Slack
Workflow concept: Review who needs an account update without expanding CRM access implicitly.
Salesforce
Workflow concept: Map exported account-team responsibilities to explicit Tsumira team roles.