CRM for Everyone is in the Restricted Early Access mode and is available only to a select set of users upon request. Please refrain from posting about this publicly. 

Overview

1. multiple teams can be onboarded to CRM.
2. each team can configure their processes and manage data in spaces dedicated for them.
   
3. each team can have a team module admin, who will be responsible for setting up processes and overseeing the operations of that team.

Note to central admins: How decentralization of CRM administration helps you 

1. Pay more attention to org-wide setup priorities.
   
2. Delegate responsibility to designated individuals
   
3. Also hold Team module admins accountable by awarding them the power as well as responsibility of workflows and processes in the system. The Super Admin can revoke Team module admin's access at any time in case of a need.
   

Points to Remember for Central Administrators 

1. Requesting Team Modules for your CRM account:

1. If your CRM account is a part of product suites —Zoho One or CRM Plus—then you can access the CRM for Everyone features on CRM Beta instance. Please log into your account, open a new window, and paste this on your address bar: https://crmbeta.zoho.com/
   
2. However, if you are using standalone accounts, you can access CRM for Everyone features on https://crm.zoho.com/
   
3. Once CRM for Everyone has been enabled for you, at the very first instance, click Try Now on the release banner. 
   
   You will be automatically redirected to the new version. You can switch between the Old UI and the New UI at any time. 
   
4. While the CRM for Everyone release suite can be enabled for the entire organization, the Try New version button is a user-specific function. That is, each user in their account can try the new version when they are ready and this action of trying new version or switching back to old version is not an org-wide setting. 
   
   

 

2. Familiarizing yourself with new roles and permissions:

1. Super Admin: Holds ultimate authority over the CRM account, can add/delete users in the org and also acts as the single point of contact for Zoho regarding subscription information and other updates.
   
2. Administrators: Org-wide admins who have control over all modules, and processes. The difference between Super Admin and an Admin is that, while both have all the required permissions, while the regular CRM Admin will be able to configure modules and all other settings in their account, they will not be able to add/delete users and will not be a point of contact for Zoho. These two are additional powers of a Super Admin. 
   

 With the addition of Team Modules, you need to also learn about the following new roles and their permissions.

Team Module Admin:

1. Criteria to be made a Team Module Admin:
   Any user in the CRM can be made a Team Module Admin, regardless of their existing profile permissions or role hierarchy. Once a user is made Team module admin, barring this module, the permissions for the rest of the CRM account will be dictated by their profile and role.
2. In order for a user to create a Team module, the user in question should have the Team Module permission enabled in their user profile. 

Team Module Users: Internal members

1. Managers have complete visibility and control over all records in the team module, irrespective of who has created them. In the case of a marketing team, this is ideal for the marketing manager.
   
2. Members can view all records, including theirs and others. But they cannot edit or delete others' records. They can only view all records. They can create, edit, and delete only their own records. In the case of a marketing team, this is ideal for a team member, where they need to refer to others' work but can only create or modify their own.
   
3. Participants can view, create, edit and delete only their own records. They do not have access to any other records, and cannot even view others' records. Ideal for interns. Project interns may not need access to other members' records. They can only work on what is assigned to them.

Requester: External member

3. Appointing Team Module Admins: Best practices and notes for Central Administrators.

1. What is the current role and designation of the user in the organization?
   
2. What are their team responsibilities?
   
3. Have they had at least a year's experience working with Zoho CRM?
   
4. A Super Administrator can approve or deny a user's request to be made a Team module admin. Though this action is not currently active in CRM, as a process, this is recommended for Super Admins to ensure that the right people become Team module admins. 

4. Understanding Team modules and Teamspaces: How they are related?

1. Org module— A module that is common for the entire organization. Eg: Leads, Contacts, Deals.
   
2. Team modules — A module created for the purpose of implementing a process for a specific team only.
   This need not/should not extend to the entire organization.
   

1. All modules are associated to a default Teamspace called "CRM Teamspace", when you enable CRM for Everyone in your account.
   
2. You may create different Teamspaces and associate the modules of your choice to each Teamspace.
   
3. Remember, a Team module can only be associated with one Teamspace at this point of time. If a Team module was created in the wrong Teamspace by mistake, or has been created in the default Teamspace, you need to dissociate it from Teamspace A and then associate it to Teamspace B.
   
4. Being the Admin of a Team module does not automatically add you to its Teamspace. There could be cases where you may seek the help of a Central IT team member to just configure the processes in a module, so you make them the Team Module Admin.
   Ex: the Marketing Manager may request a CRM Admin to configure their processes in the team module. So this Admin who is an outsider, need not be privy to the data of the Marketing Teamspace. Therefore they need to only set up this Team module, and not be added into its parent Teamspace. This is why users of a Team module are not synced back to the Teamspace — as this is not the requirement in all cases. If a user needs to be part of a Teamspace they should be deliberately added to the space. Just by being a part of the Team module in the Teamspace doesn't add them automatically to the space.  
5. If you have not created any Teamspace, all your modules will be listed under the default Teamspace called "CRM Teamspace". 

1. An overall CRM Super Admin — Highest level of authority in the system 
   
2. A Teamspace Admin — The department head of a particular team. 
   
3. Team module admin — The head of a specific process in a team.
   There could be multiple team modules in a Teamspace— and by extension, there could be multiple Team module admins within a Teamspace. 

Points to remember for Team Module Admins:

1. If you are made a part of the team module admin, but not a part of the Teamspace, you will not see the module in the Teamspace in the front-end interface. But any record from the module will be accessible for you if you arrive at it from a link. That is, a team module admin can continue to set up the team module's settings without being privy to the day to day activities of the team in question.
   
2. As the Team module admin, you have the responsibility to make sure you add the right users, and configure the necessary flows for your process. Any violation in terms of privacy, security might lead to your Super Admin revoking your access. A good practice would be to work with your Super Admin for dos and don'ts and operate accordingly.

Points to remember for Team Module Users

1. As the user of a Team module, you are responsible for the day-to-day activities and processes in the Team module.
   
2. Depending on your exact role in the team module — that is, manager, participant or member—you will have the ability to view, modify or delete your records and those of others.
   

Points to remember for Requesters:

1. As a Requester, by definition, you are an external member of a Team module. This means, you will not be a part of the day-to-day activities if the Team module, because of which you will not see that team module in your account in any Teamspace.
   
2. However, when you navigate to the My Requests tab, you will see all the team modules for which you have been added as a Requester.
   
3. You can start making requests and also track them from this tab.

Known Limitations of Team Modules and Roadmap 

1. Currently, you will not receive alerts within the system upon being made a Team module admin, requester, and also for request completion. The communication framework for Team modules is underway and expected to be in effect at the earliest. Note that in the current version, we do not have this.
   
2. Team modules do NOT support: workflow rules, blueprints, assignment rules, escalation rules, and review processes at this point. This is on our roadmap.
   
3. The requester of a deliverable/record is currently denoted as the owner of that record. The expected behavior is that, when a request comes in, it is typically "Unassigned". Owing to technical factors, temporarily the requester is recognized as the record owner— however, this will be addressed on our roadmap. 
   
4. We understand that once the team modules get adopted in CRM, there will be a need to convert existing modules to team modules. This is not available at the moment — however, this is on our roadmap and will be extended soon. 
   
5. Requesters cannot view existing records of a Team module while making a new request. 
   
6. Team module admins cannot view a list of organization users from Setup, but can do so from the Team module user access settings. 

Further Reading