Admin/PermissionManagement/Account Groups - Revision history

Scarpenter at 04:55, 8 March 2019

2019-03-08T04:55:06Z

Rlusher: /* Auto Assignment of Account Groups and Auto Deallocation from An Account Group */

2014-11-27T22:51:24Z

‎Auto Assignment of Account Groups and Auto Deallocation from An Account Group

Rlusher at 22:50, 27 November 2014

2014-11-27T22:50:42Z

Rlusher at 22:45, 27 November 2014

2014-11-27T22:45:06Z

Rlusher: Created page with " == Creating Account Groups == * Account Groups can be used to control which staff members have access to particular accounts. There are two basic components for setup. * An..."

2014-11-27T22:42:41Z

Created page with " == Creating Account Groups == * Account Groups can be used to control which staff members have access to particular accounts. There are two basic components for setup. * An..."

New page

== Creating Account Groups ==

* Account Groups can be used to control which staff members have access to particular accounts. There are two basic components for setup.
* An account group is created, and accounts can be added or removed from the group. You can change the settings of the account group such that people assigned to the group are denied or allowed to see the accounts contained therein by default.
* Note that an account can belong to more than one account group.
* An organisational unit is assigned to the account group. A staff user in turn is assigned to the organisational unit.
* When a staff member belongs to an Org Unit that is assigned to an Account Security Group called "Sydney Accounts", for example, when that user creates new customer accounts, the default home account security group for the customer account will also be "Sydney Accounts".

== Setup an Account Group ==

* Go to the Admin Menu > Account Groups

[[File:2014-09-29_16_33_41-Cumulus_-_Admin_-_Account_Groups.png]]

* In the setup, the group Access Codes are as follows
** See All Accounts. This allows a staff member to see all accounts in OR out of the group. It is akin to a super user that has full privileges to all accounts.
** Allow Some. The staff member can only see accounts contained in this account group.
** Deny Some. The staff member will be denied access to the accounts in the account group.

* If this group is being used to control security, the Group Type should be "Security Group".

[[File:2014-09-29_16_42_22-Cumulus_-_Admin_-_Account_Groups_setup.png]]

Once you have saved your account group, you can then add or remove accounts to the account group.

[[File: 2014-09-29_16_47_47-Cumulus_-_Admin_-_Account_Groups_List.png]]

* Simply find and check the box next to the account. Click add, then Save Account Group.

[[File:Account group add.png]]

== Assign Org Unit to Account Group ==

* A Staff member is assigned to an Org Unit.
* An Org Unit can be assigned to an Account Group. In this way, one or more staff members can have their access lifted or restricted to seeing certain accounts. The screenshot below depicts this.

[[File:Org unit add Group.png]]

@@ Line 1: / Line 1: @@
-=== Creating Account Groups ===
+This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
-* Account Groups can be used to control which staff members have access to particular accounts.  There are two basic components for setup.
+We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
-== Setup an Account Group ==
+[https://resources.emersion.com/display/EKB/Account+Groups Take me to the Emersion Knowledge Base article]
-* Go to the Admin Menu > Account Groups
+[[file:new_home_sm.jpg|900px]]

← Older revision		Revision as of 22:51, 27 November 2014
Line 48:		Line 48:

	* If the package had no contract, the end user account will not be moved to an account group in the first instance.		* If the package had no contract, the end user account will not be moved to an account group in the first instance.
		+
		+	* This functionality was designed with the agent/franchisee model in mind.

← Older revision		Revision as of 22:50, 27 November 2014
Line 37:		Line 37:

	[[File:Org unit add Group.png]]		[[File:Org unit add Group.png]]
		+
		+
		+	=== Auto Assignment of Account Groups and Auto Deallocation from An Account Group ===
		+
		+	* When an end user account is first created by a cumulus user (staff member), the end user account will not go in this same account group that the staff member is assigned to straight away automatically.
		+
		+	* However, if an order is created and finalized, and the package has contract, it is at this point that the end user account will go into the same account group as the one assigned to the cumulus user/staff member.
		+
		+	* When the contract expires, the end user account will be moved out of the account group automatically.
		+
		+	* If the package had no contract, the end user account will not be moved to an account group in the first instance.

← Older revision		Revision as of 22:45, 27 November 2014
Line 1:		Line 1:

−	== Creating Account Groups ==	+	=== Creating Account Groups ===

	* Account Groups can be used to control which staff members have access to particular accounts. There are two basic components for setup.		* Account Groups can be used to control which staff members have access to particular accounts. There are two basic components for setup.