View source for Users

'''Settings > Administration > Users'''
__NUMBEREDHEADINGS__
A ''user'' is a person who can access the platform, run applications, and view or modify data, as specified by their ''privileges''.

==About Users==
A User has a login identity, password, email address, and other descriptive attributes. That information is stored in a User record. You create such a record when you add a user. 

The assignments made in the User record determine the user's privileges:
:* The [[Team]] a user belongs to determines which data is shared with other users.
:* A user's [[Access Profile]] specifies global privileges for viewing and modifying data that is available to them. It also specifies administrative privileges.
:* [[Application Access]] settings determine which applications the user can run, and which Roles they can assume in those applications.
:* A user's [[Role]] determines their ability to view and modify data for individual application [[Object]]s. If a user has multiple Roles available, they choose which one is in force at any given time.

:''Learn more:'' [[User, Team and Role Guidelines]]

==Working with Users==
{{PermissionRef|User Management|add new users in the platform}}
:''Learn More: [[Available Permissions]]''

===Add a User===
To Add New Users:
#Click '''Settings > Administration > Users'''
#Click the  '''[New User]''' button
#Fill in the [[#User Settings|User Settings]].
#* Note that some fields are [[Required Field |required]]. 
#* See this information about selecting a [[User Name]].
#Click '''[Save]'''
# In the [[Application Access]] page, specify the applications the user can access and the roles they can assume in those applications.

===Edit a User===
<!--[[File:user.gif|right|thumb]]-->To Edit User Information:
#Click '''Settings > Administration > Users'''.<br>The default view displays all Active Users. You can select another type of user, if required, from the Views icon.
#Click the ''Edit'' link next to the name of the user you want to edit.
#Modify the [[#User Settings|User Settings]]. Note that some fields are [[Required Field |required]].
#Click '''[Save]'''
#In the [[Application Access]] page, make changes to the list of applications the user can access and the roles they can assume in those applications.
#Optionally, choose one of the following actions:
#:*[[#Proxy Login as this User|Proxy Login as this User]]
#:*[[#Manage Proxy Login Permissions|Manage Proxy Login Permissions]]

{{Note|The ability to edit users is subject to the [[Permissions Hierarchy]] restrictions.}}

===Reset a User Password===
{{:Reset a User Password}}

===Customer Support Login===
{{:Customer Support Login}}

=== Proxy Login as this User ===
{{:Proxy Login as this User}}

=== Manage Proxy Login Permissions ===
{{:Manage Proxy Login Permissions}}

===Deactivate a User===

When a user leaves your organization, you manage the change by Deactivating that user. That action frees up a License that can be applied to a new user, while preserving the former user's history of record ownership, activities, tasks, and so on. (The delete operation is not allowed, for reason.

{{Tip|In a large organization, it is good practice to create a team to hold deactivated users.}}

To deactivate a user:
#Remove the user from all but one team - see [[Remove Team Members]]
#Deactivate the User
#*Click '''Settings > Administration > Users'''
#*Open the user record, and deselect (uncheck) the Active checkbox. (Verify that the Active checkbox is not checked).

This user is now deactivated, and the License is now free to assign to another user.

;Tips:
*Deactivating a user will not change your Subscription Plan
*To change the number of licenses in your subscription, modify your [[Subscription Summary|Subscription Plan]]

''See also:'' Customize the [[Users Object]]

==User Settings==
{{Note|<br>
:* Empty fields are not shown when viewing user settings. They appear only when editing.
:* For a user who is recognized via [[LDAP Configuration]], only the user's [[Team]] membership, initial [[Application]], and application [[Role]] can be changed. All other information comes from the LDAP directory, where it can be modified.}}

===Basic Information===
:{| border="1" cellpadding="5" cellspacing="1" 
|-
|'''First Name''' || The first name of the user
|-
|'''Last Name''' || The last name of the user
|-
|'''Company''' || The company where the user is employed
|-
|'''Title''' || The professional title of the user
|-
|'''User License Type''' || License Type; choose ''Site User'' or ''Platform User''<br> (This option appears only in a tenant-management domain.)
|-
|'''Reports To''' || The person on your team to whom this new user reports to
|-
|'''Access Profile''' || Select an [[Access Profile]] from the lookup window
|-
|'''Employee Number''' || The user's work or sales territory and employee number; if a user supports multiple territories, include each territory, separated by commas
|}

===Locale Information===
:{| border="1" cellpadding="5" cellspacing="1" 
|-
|'''Time Zone''' || Time Zone, based on [[Time Zone Codes]]
|-
|'''Date Format''' || Choose a [[Date Format]] from the drop-down list.
|}

===Login Information===
:{| border="1" cellpadding="5" cellspacing="1" 
|-
|'''Email''' || The email address to use for sending and receiving email through the platform
|-
|'''Username''' || {{:username}}
|-
|'''Active''' || Makes this User's account active
|-
|'''Single Sign-On''' || 
If [[Single Sign-On]] is enabled, one of the following options is displayed, depending on the configuration:
:*'''Single Sign-On - Pass Thru'''
::Supply address information for a custom authentication server.
:*'''Single Sign-On - Delegated Authentication'''
::*Checkbox
::*If checked, Single Sign-on is enabled for this user
:*'''Single Sign-On - SAML'''
::*Either a ''Federation Id'' or platform ''User Id'' field is displayed.
:::*If blank, Single Sign-on is disabled for this user
:::*Enter a value to enable Single Sign-On for this user
::::*UserId is the [[Record Id]] of the user that is logged in
::::*Federated Identity acts as a user's authentication across multiple IT systems or organizations
|}

===Team Membership Information===
:{| border="1" cellpadding="5" cellspacing="1" 
|-
|'''Primary Team''' || {{:Primary Team}}
|}

===Address and Contact Information===
:{| border="1" cellpadding="5" cellspacing="1" 
|-
|'''Phone''' || The user's telephone number, including area code
|-
|'''Mobile Phone''' || The user's mobile phone number, including area code
|-
|'''Fax''' || The user's fax number, including area code
|-
|'''Street Address''' || The user's street address
|-
|'''City''' || The user's city
|-
|'''State''' || The user's state or province
|-
|'''Postal/Zip Code''' || The user's postal or zip code
|-
|'''Country''' || The user's country
|-
|'''Receive Newsletter''' || Get emailed newsletters from the company, whenever they are sent
|-
|'''Send Welcome & Login Information by Email''' || Notify the user by email of changes in their account
|}

When a User is added, the record remains in the database, and the tasks and activities associated with that user are tracked in the [[Audit]] log.

===For Developers===
When using the [[REST API]] to Add a User, the ''password'' is optional, and not required. Password policies are implicit and are applied automatically when a new user record is created.
:''Learn more: [[Record_Resource#Add_a_Record|Add a User (Record)]]''
<noinclude>

[[Category:Administration | 12]]
</noinclude>