Employees - Revision history

Dina at 08:10, 8 July 2020

2020-07-08T08:10:12Z

← Older revision		Revision as of 08:10, 8 July 2020
Line 1:		Line 1:
	{{officemanagement}}		{{officemanagement}}
	== Introduction ==		== Introduction ==
	Employees in ~~CommitCRM~~ are unique [[Accounts\|Account]] records that use slightly different data which is specific for an Employee Account. You can view Employees as part of the Accounts list or under the Employees window which shows a list of employees only.		Employees in RangerMSP are unique [[Accounts\|Account]] records that use slightly different data which is specific for an Employee Account. You can view Employees as part of the Accounts list or under the Employees window which shows a list of employees only.

	__TOC__		__TOC__
Line 14:		Line 14:
	#Each employee user can define their own [[Email Templates#Email Signature\|Email Signature]] to be used when sending an email from within the application. Click Edit Email signature to configure the signature. You can read more about editing the signature and using it in [[Email Templates]] in the [[Email Templates#Email Signature\|Email Signature]] section.		#Each employee user can define their own [[Email Templates#Email Signature\|Email Signature]] to be used when sending an email from within the application. Click Edit Email signature to configure the signature. You can read more about editing the signature and using it in [[Email Templates]] in the [[Email Templates#Email Signature\|Email Signature]] section.
	#Note the employee is currently Active; you can change the status to Inactive by clicking the '''Make Inactive''' button. Read more about this in the [[#Make Active/Inactive\|Make Active/Inactive]] section.		#Note the employee is currently Active; you can change the status to Inactive by clicking the '''Make Inactive''' button. Read more about this in the [[#Make Active/Inactive\|Make Active/Inactive]] section.
	#To allow the employee to log in to ~~CommitCRM~~, click the '''Configure User''' button and set the employee’s password.		#To allow the employee to log in to RangerMSP, click the '''Configure User''' button and set the employee’s password.
	#Select the desired privileges group. You can read more about the employee privileges in the [[Employees#Employee_Privileges_Group\|Employee Privileges Group]] section.		#Select the desired privileges group. You can read more about the employee privileges in the [[Employees#Employee_Privileges_Group\|Employee Privileges Group]] section.
	#Click Configure Web User to add credentials for a Web user to be used in the [[Web Interface\|~~CommitCRM~~ Web Interface]].		#Click Configure Web User to add credentials for a Web user to be used in the [[Web Interface\|RangerMSP Web Interface]].
	#If this is a restricted Employee (e.g. a Subcontractor), you can restrict this employee to only specific Accounts. See more details in [[Subcontractors#Limiting_Accounts_Access\|Limiting Account Access]].		#If this is a restricted Employee (e.g. a Subcontractor), you can restrict this employee to only specific Accounts. See more details in [[Subcontractors#Limiting_Accounts_Access\|Limiting Account Access]].
	#Save the new details (click the '''Save''' button on the tool bar)		#Save the new details (click the '''Save''' button on the tool bar)
Line 38:		Line 38:

	===Employee Privileges Group===		===Employee Privileges Group===
	When creating users in ~~CommitCRM~~, you can assign predefined privilege groups (SysAdmin, Full, Partial, Limited or Subcontractos) or you can assign a privilege group you've created yourself. See complete information about Privileges Groups in [[Employee Privileges]].		When creating users in RangerMSP, you can assign predefined privilege groups (SysAdmin, Full, Partial, Limited or Subcontractos) or you can assign a privilege group you've created yourself. See complete information about Privileges Groups in [[Employee Privileges]].
	<br><br>		<br><br>
	See also the [[Privileges FAQ]] for more tips about using privileges in ~~CommitCRM~~.		See also the [[Privileges FAQ]] for more tips about using privileges in RangerMSP.

	==Deleting Employees==		==Deleting Employees==

Dina at 11:00, 24 May 2020

2020-05-24T11:00:30Z

← Older revision		Revision as of 11:00, 24 May 2020
Line 6:		Line 6:

	== Create New Employee ==		== Create New Employee ==
	#Open the Employees window and click on the New icon on the toolbar. The New Employee window will open.<br><BR>[[File:~~Commit_setup_guide_new_employee_window~~.~~gif~~\|center]]<br><BR>		#Open the Employees window and click on the New icon on the toolbar. The New Employee window will open.<br><BR>[[File:setup_guide_new_employee_window.png\|center]]<br><BR>
	#You can enter some of the details in the this window, such as name, phone numbers, and more (see more details below).		#You can enter some of the details in the this window, such as name, phone numbers, and more (see more details below).
	#Click '''OK'''.		#Click '''OK'''.
	#The employee window will open. The Employee tab will be selected, and you can now setup some more parameters:<br><BR>[[File:setup_guide_add_employee_window.~~gif~~\|center]]<br><BR>		#The employee window will open. The Employee tab will be selected, and you can now setup some more parameters:<br><BR>[[File:setup_guide_add_employee_window.png\|center]]<br><BR>
	#Set the employee's [[Employees#Employee_Hourly_Labor_Rates\|Hourly Labor Rate]]. This rate will be used when this employee adds charges to the system.		#Set the employee's [[Employees#Employee_Hourly_Labor_Rates\|Hourly Labor Rate]]. This rate will be used when this employee adds charges to the system.
	#By using the '''Default Color for New Appointments''' option, you can set a default color to be used for all Appointments created by or assigned to this employee. After entering this setting, all Appointments created for this employee automatically appear in this color on the Calendar or the Dispatcher window. You can also choose to override this setting when actually creating the Appointment for the employee.		#By using the '''Default Color for New Appointments''' option, you can set a default color to be used for all Appointments created by or assigned to this employee. After entering this setting, all Appointments created for this employee automatically appear in this color on the Calendar or the Dispatcher window. You can also choose to override this setting when actually creating the Appointment for the employee.

Dina at 13:33, 15 May 2020

2020-05-15T13:33:37Z

← Older revision		Revision as of 13:33, 15 May 2020
Line 9:		Line 9:
	#You can enter some of the details in the this window, such as name, phone numbers, and more (see more details below).		#You can enter some of the details in the this window, such as name, phone numbers, and more (see more details below).
	#Click '''OK'''.		#Click '''OK'''.
	#The employee window will open. The Employee tab will be selected, and you can now setup some more parameters:<br><BR>[[File:~~Commit_setup_guide_add_employee_window~~.gif\|center]]<br><BR>		#The employee window will open. The Employee tab will be selected, and you can now setup some more parameters:<br><BR>[[File:setup_guide_add_employee_window.gif\|center]]<br><BR>
	#Set the employee's [[Employees#Employee_Hourly_Labor_Rates\|Hourly Labor Rate]]. This rate will be used when this employee adds charges to the system.		#Set the employee's [[Employees#Employee_Hourly_Labor_Rates\|Hourly Labor Rate]]. This rate will be used when this employee adds charges to the system.
	#By using the '''Default Color for New Appointments''' option, you can set a default color to be used for all Appointments created by or assigned to this employee. After entering this setting, all Appointments created for this employee automatically appear in this color on the Calendar or the Dispatcher window. You can also choose to override this setting when actually creating the Appointment for the employee.		#By using the '''Default Color for New Appointments''' option, you can set a default color to be used for all Appointments created by or assigned to this employee. After entering this setting, all Appointments created for this employee automatically appear in this color on the Calendar or the Dispatcher window. You can also choose to override this setting when actually creating the Appointment for the employee.

Dina at 10:01, 22 March 2020

2020-03-22T10:01:36Z

← Older revision		Revision as of 10:01, 22 March 2020
Line 56:		Line 56:
	*[[Privileges]]		*[[Privileges]]
	*[[Employee Privileges]]		*[[Employee Privileges]]
	*[[~~CRM~~ Installation]]		*[[Software Installation]]
	*[[Employees & Users FAQ]]		*[[Employees & Users FAQ]]
	*[[To-do Lists]]		*[[To-do Lists]]

Dina at 17:16, 21 March 2020

2020-03-21T17:16:46Z

← Older revision		Revision as of 17:16, 21 March 2020
Line 56:		Line 56:
	*[[Privileges]]		*[[Privileges]]
	*[[Employee Privileges]]		*[[Employee Privileges]]
	*[[~~CommitCRM~~ Installation]]		*[[CRM Installation]]
	*[[Employees & Users FAQ]]		*[[Employees & Users FAQ]]
	*[[To-do Lists]]		*[[To-do Lists]]

Robert: /* See Also */

2014-08-24T11:58:51Z

Sheli at 09:31, 26 November 2012

2012-11-26T09:31:33Z

← Older revision		Revision as of 09:31, 26 November 2012
Line 16:		Line 16:
	#To allow the employee to log in to CommitCRM, click the '''Configure User''' button and set the employee’s password.		#To allow the employee to log in to CommitCRM, click the '''Configure User''' button and set the employee’s password.
	#Select the desired privileges group. You can read more about the employee privileges in the [[Employees#Employee_Privileges_Group\|Employee Privileges Group]] section.		#Select the desired privileges group. You can read more about the employee privileges in the [[Employees#Employee_Privileges_Group\|Employee Privileges Group]] section.
	#Click Configure Web User to add credentials for a Web user to be used in the [[Web Interface\|~~Commit~~ Web Interface]].		#Click Configure Web User to add credentials for a Web user to be used in the [[Web Interface\|CommitCRM Web Interface]].
	#If this is a restricted Employee (e.g. a Subcontractor), you can restrict this employee to only specific Accounts. See more details in [[Subcontractors#Limiting_Accounts_Access\|Limiting Account Access]].		#If this is a restricted Employee (e.g. a Subcontractor), you can restrict this employee to only specific Accounts. See more details in [[Subcontractors#Limiting_Accounts_Access\|Limiting Account Access]].
	#Save the new details (click the '''Save''' button on the tool bar)		#Save the new details (click the '''Save''' button on the tool bar)

Sheli: /* Deleting Employees */

2012-04-09T17:57:59Z

Deleting Employees

← Older revision		Revision as of 17:57, 9 April 2012
Line 48:		Line 48:

	<br>		<br>
	If this is a test employee which was created only for testing (e.g. while in trial), you may consider renaming the Employee and start using it for a real employee. Make sure to delete all old history linked to this test employee (e.g. tickets, charges, etc.) prior to making this step, to avoid having old test history linked to the real employee.		If this is a test employee which was created only for testing (e.g. while in trial), you may consider renaming the Employee and start using it for a real employee. For example, if a new employee joins the team you can rename it to reflect this employee instead of creating a new employee record. This is not recommended on a regular basis but it's possible.

			Make sure to delete all old history linked to this test employee (e.g. tickets, charges, etc.) prior to making this step, to avoid having old test history linked to the real employee.

	==See Also==		==See Also==

Sheli: /* Deleting Employees */

2012-04-09T16:30:05Z

Deleting Employees

← Older revision		Revision as of 16:30, 9 April 2012
Line 45:		Line 45:
	In order to keep data integrity in the database Employees cannot be deleted, because they can have linked data history already created in the system.		In order to keep data integrity in the database Employees cannot be deleted, because they can have linked data history already created in the system.

	If you do not want to use an Employee anymore, a System Administrator can deactivate the employee from the ''Employee Tab > Make Inactive'' option.		If you do not want to use an Employee anymore, a System Administrator can deactivate the employee from the ''Employee Tab > Make Inactive'' option. This way this Employee will no longer use an Active Employee license, however, you will be able to find old records linked to it, like Charges, Tickets, etc.

			<br>
	If this is a test employee which was created only for testing (e.g. while in trial), you may consider renaming the Employee and start using it for a real employee. Make sure to delete all old history linked to this test employee (e.g. tickets, charges, etc.) prior to making this step, to avoid having old test history linked to the real employee.		If this is a test employee which was created only for testing (e.g. while in trial), you may consider renaming the Employee and start using it for a real employee. Make sure to delete all old history linked to this test employee (e.g. tickets, charges, etc.) prior to making this step, to avoid having old test history linked to the real employee.

Sheli: /* Employee Privileges Group */

2012-04-09T16:28:43Z

Employee Privileges Group

← Older revision		Revision as of 16:28, 9 April 2012
Line 41:		Line 41:
	<br><br>		<br><br>
	See also the [[Privileges FAQ]] for more tips about using privileges in CommitCRM.		See also the [[Privileges FAQ]] for more tips about using privileges in CommitCRM.

			==Deleting Employees==
			In order to keep data integrity in the database Employees cannot be deleted, because they can have linked data history already created in the system.

			If you do not want to use an Employee anymore, a System Administrator can deactivate the employee from the ''Employee Tab > Make Inactive'' option.

			If this is a test employee which was created only for testing (e.g. while in trial), you may consider renaming the Employee and start using it for a real employee. Make sure to delete all old history linked to this test employee (e.g. tickets, charges, etc.) prior to making this step, to avoid having old test history linked to the real employee.

	==See Also==		==See Also==

← Older revision		Revision as of 11:58, 24 August 2014
Line 58:		Line 58:
	*[[CommitCRM Installation]]		*[[CommitCRM Installation]]
	*[[Employees & Users FAQ]]		*[[Employees & Users FAQ]]
			*[[To-do Lists]]

	[[Category:Office Management]]		[[Category:Office Management]]
	[[Category:Privileges]]		[[Category:Privileges]]