User and Team Entities
User and team management is the area of Microsoft Dynamics CRM where you can create and maintain user accounts and profiles.
A user is any person who works for a business unit who uses Microsoft Dynamics CRM. Each user has a user account. All users must be associated with only one business unit. This association controls which customer data the user will have access to. Included in the user's account is information such as the user's telephone numbers, email address, and a link to the user's manager. Each user has privileges and rights to manage their own personal settings. Each user corresponds to a user in the Active Directory for that organization. When you create a user, you must assign the user to at least one security role. Even if the user is part of a team that has assigned roles, the user should be assigned to a role. For more information about access levels and roles, see How Role-Based Security Can Be Used to Control Access to Entities in Microsoft Dynamics CRM.
A team is a group of users. This organizational structure enables groups of users across an organization to share information. Each team must be associated with only one business unit. A team can include users from any business unit, not only the business unit with which the team is associated. Users can be associated with more than one team.
Users and teams can own records if the OwnershipType is set to OwnershipTypes.UserOwned. You can use the ReassignObjectsOwnerRequest message or the ReassignObjectsSystemUserRequest message to do bulk reassignment of all records for an owner.
The following illustration shows the entity relationships for users and teams.
Users
In Microsoft Dynamics CRM 2011, users can be disabled but they cannot be deleted. To find the user who is currently logged on or who is impersonated, call the WhoAmIRequest message.
The following table provides details about the significant attributes for the system user entity. For a complete list of attributes for this entity, see SystemUser (User) Entity Metadata.
| Attribute name | Description |
|---|---|
|
AccessMode |
Specifies the type of access that this user has to Microsoft Dynamics CRM. This is sometimes referred to as the type of user.
|
|
CalType |
Specifies the user’s license type.
|
|
IsDisabled |
Specifies whether the user is disabled. Only licensed users or users who have an access mode of support or non-interactive can be enabled. Support users cannot be disabled. |
|
IsLicensed |
Specifies whether the user is licensed. This applies to customers who access Microsoft Dynamics CRM Online through the Microsoft online services environment. This attribute is read-only, and is updated by the system. |
|
IsSyncWithDirectory |
Specifies whether the user is synchronized with the Office 365 directory. This applies to customers who access Microsoft Dynamics CRM Online through the Microsoft online services environment. This attribute can only be set on create and is otherwise read-only. |
|
QueueId |
Specifies the default queue for the user. |
For more information about how users are provisioned in and synchronized with Microsoft Office 365, see Synchronized Users in Microsoft Dynamics CRM Online and Office 365.
Non-interactive users are often used when writing service-to-service code because they do not use up a license. Microsoft Dynamics CRM Online allows for five free non-interactive users. To disable a non-interactive user, update the user record changing the accessmode value to any other value. The user will be disabled automatically.
Note |
|---|
| If your organization has been updated to Microsoft Dynamics CRM Online Fall ’13, please use the latest version of the SDK. Download the updated SDK package for Microsoft Dynamics CRM 2013 and CRM Online Fall ‘13. |
Teams
In Microsoft Dynamics CRM 2011, teams can be deleted using the DeleteRequest message or IOrganizationService.Delete method. The use of teams is optional in Microsoft Dynamics CRM.
Access checks are additive. You can access entities based on the roles assigned to the user plus the roles assigned to the team that a user is a member of. This allows a user to have privileges outside their business unit.
Note |
|---|
| A user's set of privileges is a union of privileges from the user's roles and privileges from all teams’ roles in which the user is a member. |
See Also
Tasks
Sample: Assign a Record to a TeamSample: Create an On-Premises User
Sample: Disable a User
Sample: Share Records Using GrantAccess, ModifyAccess and RevokeAccess Messages
Concepts
Synchronized Users in Microsoft Dynamics CRM Online and Office 365Team Entity Messages and Methods
Team Entity Metadata
SystemUser (User) Entity Messages and Methods
SystemUser (User) Entity Metadata
SystemUser (User) Entity OptionSet Attribute Metadata
UserSettings Entity Messages and Methods
UserSettings Entity Metadata
UserSettings Entity OptionSet Attribute Metadata
Other Resources
Administration and Security Entities (Organization, Business Unit, User, Team, Privilege, Role, Field Security)Blog: Service Accounts – Non-Interactive Users
Whitepaper: Scalable Security Modeling with Microsoft Dynamics CRM 2011
Microsoft Dynamics CRM 2011
Send comments about this topic to Microsoft.
© 2013 Microsoft Corporation. All rights reserved.
Note