Introduction
This is the place where all the system’s organizations are managed.
There’s only one root organization. The “Create” function only creates child organizations.
Pre-requisites
The page is assessible to those with “View users” / “Manage users” permission. With “View users” permission, they can just view the organization list. They can add, edit, delete child organizations if they have “Manage users” permission.
Actions on Organizations
Actions | Description |
---|---|
| Clicking this button opens the Edit popup for a particular record. Users can make amendment to any fields. |
| Clicking this button to trigger the record deletion. Once confirmed, the record is deleted. Root organization is not delete-able. |
Organizations vs. Users
A user can ONLY be attached to one organizations.
If the user is attached to an organization which he currently does not belong to, the user will be removed from the current organization first, and then being attached to the new organization.
Basically, parent-organization users can manage data at the system scope while child-organization users can only manage data at their organization scope.
Example:
The root organization is named “Contemi-Testing”, and there’re child organization:, “Broker A” and “Broker B”.
Contemi-Testing users can manage all accounts, quotes and policies in the system.
Broker A users can only manage those under “Broker A” organization.
Broker B users can only manage those under “Broker B” organization.
As for “Sales commissions”, there’re two levels of setting:
Organization
Product
The setting is reflected during quotation process. If defined, the organization-level commission setting supersedes the product-level one.