Microsoft Dynamics CRM Online - Project Service Automation User Add-on GovernmentMFR # A8B-3BD7F5BDE155 Digital Download
Microsoft Dynamics CRM Online - Project Service Automation User Add-on Government
Microsoft Dynamics CRM Online Project Add-On is designed for professionals who manage projects and the associated customer engagement process end-to-end. This provides licensed users with capabilities required for setting up a project organization, engaging with customers, and managing and closing projects. Microsoft Dynamics CRM Online Project Service Automation Add-On will initially have limited availability, and is set up as a lead status offer. This means the business desk is required to transact it, and availability is limited to Enterprise Agreement customers only. As an add-on, this license requires each user to first be licensed with at least a CRM Online Basic USL or higher. For advanced sales, service, or other capabilities, the user may leverage this license as an add-on to the CRM Online Professional USL. Use Right Project
Frequently asked questions
How does the organizational unit entity introduced by project service automation relate to the organization entity that already exists in CRM?
The organization entity in CRM represents the name of a global CRM instance. This is usually the name of the global enterprise. The organizational unit is a group or division within the global enterprise that has a set of roles and a distinct cost price list for these roles that is different from other such divisions in the company. When project service automation is installed, a default organizational unit is automatically created based on the organization. All existing resources will get assigned to the default organizational unit. Subsequently any new Active Directory users or resources imported into CRM will be assigned to the default organizational unit in Project service automation by the user import process.
How is the Organizational Unit entity different from the Business Unit entity in CRM?
The Business Unit entity in CRM is designed as a security construct. Associating a user to a business unit will directly determine what entities and entity records the user has access to. It will also determine which permissions (Create, Read, Write, Delete, Append, Append To, Assign, and Share) the user has on those entity records. The Organizational Unit entity is designed to represent a unit or division of the company that has distinct cost rates for employees that belong to it. Associating a resource to an organizational unit will determine its cost to a project engagement. When implementing CRM, optimize security authorization for the hierarchy of business units and the assignment of users to business units. Assign all users who typically need to access the same set of records to the same business unit. The organizational unit has no impact on security authorization or access. The following example illustrates the distinction
There are no product specifications.