...
| Excerpt | ||
|---|---|---|
| ||
Learn to work with Network Management |
| Panel | ||||
|---|---|---|---|---|
| ||||
On this page
|
Overview
Network Management is used to represent your company departments and hierarchy structure and use it to administer record level access rights; i.e. the access right associated with a user handling a specific customer rather than the right to access a menu item. Additionally, it can be used to allow or deny sharing of data (records) between the different departments.
Major features
- Simulate the structure of your business including partners establishing access levels within the system based on this structure. Use communities, groups and teams to represent, the organisation departments and teams respectively.
- Network Entity Types are used to categorize and control access to CRM.COM modules and define the global behavior of these entities within the system.
Setting Up Network Management
| Info | ||
|---|---|---|
| ||
| Foundation > Network Management |
...
A community represents your organisation. If you have a business with multiple business partners you can create two communities; one which will represent your business and one under which all the partners belong. For each community, you can define a single person or company (Contact Information) who will be in charge and designated as the point of contact.
Community fields
The table describes the sections of Community Data Entry page, and explains how the fields in the page are used.
...
Name
Classification: An informational classification of the community which can be 'Internal' or 'External'
...
Groups
...
Displays all the groups that belong to the community, which can be created and added to a community through the Actions > Add New Group, available in the Actions menu or through the Groups page.
...
Units
...
Displays all the units that belong the community, which can be added to a group through the groups or units Data Entry page.
...
Users
...
Displays all the users that belong the Community which can be added to units through the units or users Data Entry page..
...
A group represents a department of your organisation such as, sales, marketing or finance. For each group, you can define a single person or company (contact information) who will be in charge of the group and designated as the point of contact.
Group fields
The table describes the sections of Group Data Entry page, and explains how the fields in the page are used.
...
Name
...
The details of the point of contact. A new contact information must be created.
...
When new records are entered in the system, they are usually 'owned by a group', which dictates the users that will have access to this record according to the group they belong to.
By setting covered geographical areas to groups, you enable the system to automatically assign a group to new records, using the geographical areas it is covering. Refer to Automatic assignments based on geographical areas for more information on the logic of how the assignment of the group is done.
Set as Owner Group automatically based on Covered Geographical Areas: If enabled, the specific group will automatically be set as the of owner of newly created records provided that the location of the customer is within the covered geographical area.
You can define Area, District, Town/City and Postal Code as conditions, while if more than one conditions are defined in the same row, they must all be met.
...
Units
...
Displays all the units that belong the group, which can be created and added to a group through Actions > Add New Unit, available in the Actions menu or at the Units Data Entry page.
...
Users
...
Displays all the users that belong the group which can be added to units through the units or users Data Entry page..
...
A unit represents a team within a department such as, team leaders and operators. For each unit, you can define a single person or company (contact information) who will be in charge of the unit and designated as the point of contact.
Unit fields
The table describes the sections of Units Data Entry page, and explains how the fields in the page are used.
...
Name
...
An accounts receivable can be also added to the unit's contact information by using REGISTER PRIMARY ACCOUNT.
| Note |
|---|
Account information in used by Rewards module where units can be used to represent partners and the account information is used for crediting or debiting them through Reward Settlement Runs. |
...
Covered Geographical Areas
...
When a new record is entered in the system, that requires a user to complete it, it is assigned to either a unit or a user, which is responsible for its completion. For example, when a new task (Activity) for installation is created the task is assigned to the 'Installer's Team' and one of the installers will complete the installation.
By setting covered geographical areas to units, you enable the system to automatically assign a unit to new records, using the geographical areas it is covering. Refer to Automatic assignments based on geographical areas for more information on the logic of how the assignment of the unit is done.
Assign Unit automatically based on Covered Geographical Areas: If enabled, the specific unit will automatically be set in the 'Assigned to Unit' of newly created records provided that the location of the customer is within the covered geographical area.
You can define Area, District, Town/City and Postal Code as conditions. If more than one conditions are defined in the same row then they must all be met.
...
Sub Units
...
Displays all the sub-units that belong the unit, which can be created and added to the unit through the Actions > Add New Sub Unit, available in the Actions menu of the unit Data Entry page.
...
Users
...
Displays all the users that belong the group which can be added to units through the users Data Entry page..
...
Data in CRM.COM is subject to different levels of access by users, depending on the group (or business department) they belong to. For example, if customer Z belongs to group A then only users belonging to group A will have access to customer Z entry.
Data however, can be shared between groups (i.e. between yourr departments) and you can define access restrictions on the shared data, such as:
- Access to view data
- Access to modify data
- Access to assign data
- Access to search for data
To share data a group collaboration must be set up, where you can define the group to share its data, to which groups and what access restrictions will be applicable on the shared data.
| Note |
|---|
Group Collaborations do not apply for Controlled Selection Entities. i.e. if Group A is set as an 'Allowed Organisational Unit' for a certain 'activity type' even if there exists a collaboration between group A and group B, a user from group B will still not be allowed to create an activity of that type. |
Group collaboration profile fields
The table describes the sections of Group Collaboration Profiles Data Entry page, and explains how the fields in the page are used.
...
| Warning |
|---|
If the selected collaboration scope is 'All Groups', it only works for groups that belong to the same community or for communities that collaborate with the community of the group. |
...
If the 'Specific Groups' collaboration scope is selected then collaboration settings are defined for each selected group. Start by 'Adding' the group and defining the settings. For the 'All Groups' collaboration scope the actions are only defined once.
Collaboration Settings: The settings which define the access restrictions to shared data. For each access restriction, you can define which data will be shared, its access level (i.e. None, records of all privacy levels, records of specific privacy level)
| Note | ||
|---|---|---|
| ||
|
...
View My Records
...
Defines which, if any data will be available for other groups to view.
- None
- All Privacy Levels
- Specific Privacy Level Group
- Specific Privacy Levels
...
Defines which, if any data will be available for other groups to view and modify.
- None
- All Privacy Levels
- Specific Privacy Level Group
- Specific Privacy Levels
...
Defines which, if any data will be available for other groups to view, modify or assign. Assigning of records only refers to Assignable Entities.
- None
- All Privacy Levels
- Specific Privacy Level Group
- Specific Privacy Levels
...
Defines whether the group will be available in the results of processes that search for groups (in Data Entry pages), and also to use it as a value in group related fields of various modules of the software.
For example, to use the specified group as the 'Owned by Group' of a subscription.
- None
- All Privacy Levels
...
Defines whether the units of the group will be available in the results of processes that search for units (in Data Entry pages) and also to use them as a value in unit related fields of various modules of the software.
For example, to use the unit belonging to the specified group as the 'Assign To Unit' of an activity.
- None
- All Privacy Levels
...
Defines whether the users of the group will be available in the results of processes that search for users (in Data Entry pages) and also to use them as a value in user related fields of various modules of the software.
For example, to use the unit belonging to the specified group as the 'Assign To User' of an activity.
- None
- All Privacy Levels
...
Community collaboration profiles are used when groups sharing data between them belong to different communities.
Set up a community collaboration profile when a group profile is set up with a collaboration scope set to 'All Groups' to ensure that the data is shared to even groups that do not belong to other communities
Community Collaboration Profiles fields
The table describes the sections of Community Collaboration Profiles Data Entry page, and explains how the fields in the page are used.
...
Collaboration Scope: Define whether data from groups of this community will be shared with groups of Specific Communities or All Communities
...
Collaboration with Communities
...
Related Configuration Areas
The following module is related to network management and must be configured for the module to operate at its full capacity.
Manual Link | Area | Description | Configuration |
|---|---|---|---|
| Security Management | Privacy Level & Privacy Level Groups | Configure the privacy level and privacy level groups which can be used in the group collaboration profiles as condtions of the data which can be shared. | Optional |
Using Network Management
...
Assignment of groups and units on new or amended records can be done automatically, using common geographical areas. For example, if the customer requesting an installation is residing in London-Zone 6, then the system would assign the task to the installer's team who is responsible for London-Zone 6.
Unit assignment is performed on 'assignable entities' and denotes the team responsible to perform the task, while group assignment is performed on 'explicit viewing access entities' and denotes the department that owns the record and has full access rights to it.
Unit assignment
Units can be assigned automatically based on covered geographical areas if enabled through Units. Unit assignment is applicable for entities that require the completion of a task to be carried out by a user. These entities are referred to as Assignable Entities
- Activities
- Leads
- Service Requests
- Jobs
A unit will be automatically assigned to entries provided that the location of the customer is within the covered geographical area. In each case the system will compare the customer address according to the table below. against the covered geographical areas of each unit and will assign a Unit when a match is found. If more than one unit cover the area in question, then the automatic assignment is not performed.
| Assignable Entities | Entity address compared against Geographical Area |
|---|---|
Activity Lead Service Request | All available addresses of the related contact information ('Active' and 'Inactive'). |
| Job | Job location |
| Note |
|---|
The option to automatically assign the unit based on geographical area is also present on Automatic Collaboration Rule (ACR) . The system will first go through the ACR and will then check and assign through units configuration. |
Group assignment
Groups can be defined as 'Owned by Group' of entries in the system based on covered geographical areas if enabled through Groups. This only concerns explicit viewing access entities. i.e. entities for which the owner group is defined on the record.
A group will be automatically set as 'Owned by Group' to entries, provided that the location of the customer is within the covered geographical area.
In each case, the system will compare the customer address, according to the table below, against the covered geographical areas of each group and will assign a group when a match is found. If more than one group covers the area in question, then the automatic assignment is not performed.
| Explicit Viewing Entities | Entity address compared against Geographical Area |
|---|---|
Subscription | Subscription location |
Job | Job location |
Accounts Receivable Communications Contact Information Leads Activities Service Requests | All available addresses of the related contact information ('Active' and 'Inactive'). |
Resource Plans Warehouses Reward Offers | Not set automatically |
...
All entities in CRM.COM, for example, Subscriptions, Subscription Types and Activities can beong to multiple entity network types and each type is responsible for distinct functionality and access behavior; e.g. the Activities module is defined as an Implicit Viewing Entity as well as an Assignable Entity.
Refer to the table below for a description of each network entity type and the CRM.COM modules that are of that type.
...
| column | Entity Type |
|---|
...
Explicit Viewing Access
Entities which hold information regarding the group that owns the record. They can be viewed only by users belonging to the same group or by users whose group collaborates with the group.
The following information is set on each record:
...
If no group is defined when creating records of these entities the system automatically sets the 'Owned by Group' to the group of the logged in user or based on geographical areas if any are set up.
...
- Accounts Receivable
- Communications
- Contact Information
- Warehouses
- Leads
- Resource Plans
- Subscriptions
- Activities
- Service Requests
- Jobs
- Reward Offers
...
Implicit Viewing Access
...
Entities which don’t hold information regarding the owner of a record. They can be viewed only by users belonging to the group that owns their master entity or by users whose group collaborates with the group of the master entit
The master entity of an Implicit Viewing Entity is an Explicit Viewing Entity.
...
The second entity available in each row, denotes the master entitiy which has 'Explicit Viewing Access' and from which the viewing access is implied
- Financial Transactions - Accounts Receivable
- Bills - Accounts Receivable
- Rated Billing Items - Accounts Receivable
- Notifications - Contact Information
- Wallets - Accounts Receivable
- Wallet Transactions - Accounts Receivable of Wallet
- Reward Transactions - Accounts Receivable of Rewards Participant
- Installed Items - Warehouses / Jobs / Subscriptions (depending on allocation)
- Delivery Notes - Warehouses
- Warehouse Transactions - Warehouses
- Resource Plan Entry - Resource Plans
- Resource Plan Entry Working Hours - Resource Plans
- Award Reward Transactions - Accounts Receivable of Rewards Participant
- Spend Reward Transactions - Accounts Receivable of Rewards Participant
- Reward Participant - Accounts Receivable
- Subscription Actions - Subscriptions
- Provided Ad Hoc Discounts - Subscriptions or Jobs
- Applied Additive Discounts - Subscriptions or Jobs (Ad hoc or auto-apply)
...
Global Viewing Access
...
- Entities not specified as entities with explicit or implicit viewing access
- Entity types
- Configuration entities
...
Exceptional Viewing Access
...
- Resource Requests
- Viewed by units that requested the resources.
- Viewed by units which are requested as resources.
- Viewed by super users.
- Groups
- Viewed by users who access the system using a unit that belongs to the specific group.
- Viewed by users who access the system using a unit that belongs to a group that collaborates with the specific group (provided "Share My Group" is selected).
- Viewed by super users.
- Units
- Viewed by users who access the system using the specific Unit.
- Viewed by users who access the system using a unit that belongs to the same group as the specific Unit.
- Viewed by Users who access the system using a unit that belongs to a group that collaborates with the group that the specific unit belongs to (provided "Share My Units" is selected).
- Viewed by super users.
- Users
- Viewed by users who access the system using a unit that belongs to the same group as one of the units that the User belongs to.
- Viewed by users who access the system using a unit that belongs to a group that collaborates with the group that includes one of the units that the User belongs to (provided "Share My Units" is selected).
- Viewed by super users.
...
Controlled Selection Access
...
Entities which can be selected by all users, but with restrictions defined at the module level by defining the Allowed Organisational Units (AOUs).
- Entries of these entities can be viewed by all users (regardless of the AOUs) if they have already been selected and applied on another record.
- Any entry of such entity created with defined AOUs cannot be set as a default value within the system, as it won't be available for Users belonging to any Organisational Unit.
Entries of this entities have a definition section where all the AOUs which can select those records are specified. The following options are available:
- Communities: available for all users of groups or units belonging to specified communities.
- Groups: available for all users of units belonging to specified groups.
- Units: available for all users of the specified units.
- Users: available for all users of if no AOU is defined
...
- Price Plans
- Additive Discounts
- Warranties
- Vouchers
- Privacy Level Groups
- Presentment Preferences
- Communication Queue External Systems
- Communication Templates
- Additive Discount Definitions
- All Transactional Entity Types
- Activity Types
- Communication Types
- Lead Types
- SLA Types
- Warranty Types
- Job Types
- Order Types
- Service Request Types
- Subscription Types
- Financial Transaction Types
- Voucher Types
- Wallet Transaction Types
- Reward offer Types
- Reward Schemes
...
Contact Information based Entities
...
- Accounts Receivable
- Activities
- Communications
- Leads
...
Accounts Receivable based Entities
...
- Subscriptions
- Jobs
- Service Requests
- Wallets
...
Assignable Entities
Entities which require a course of action and can be assigned to a unit or a user, which will be responsible for performing the actions.
Assignable entities have their records assigned to either a unit or user. This is done through the 'Assigned To' component which is globally used by all Assignable Entities. The component includes the following:
...
| Note |
|---|
It is possible to only define the unit when creating an Assignable Entity. In this case, before any further processing, the entity must be 'Accepted' by a user that belongs to the defined unit, via the dedicated ACCEPT Action. In the case that only a user is selected, then the system will automatically set the unit to that which the defined user belongs to. |
...
| Anchor | ||||
|---|---|---|---|---|
|
| Excerpt | ||
|---|---|---|
| ||
Learn to work with Network Management |
| Panel | ||||
|---|---|---|---|---|
| ||||
On this page
|
Overview
Network management is the process of defining the structure of an organization's internal departments and external partner network, and subsequently defining access to data, at record level.
Major features
- Simulate the structure of your business departments and partner network
- Use communities, groups, and units to represent organizations, departments and teams (respectively)
- Establish access levels within the system.
- Use Network Entity Types to classify and control access to CRM.COM modules and define their behavior within the system.
| Anchor | ||||
|---|---|---|---|---|
|
An understanding of CRM.COM network entity types is essential for setting up network management.
All CRM.COM entities such as subscriptions, subscription types and activities can belong to multiple entity network types. For example, the activities module is defined as an implicit viewing entity as well as an assignable entity. Entity entries inherit their functionality and access behavior from the network entity type.
Refer to the table below for a description of network entity types
| Table filter | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||
|
Setting Up Network Management
| Info | ||
|---|---|---|
| ||
| Foundation > Network Management |
| Anchor | ||||
|---|---|---|---|---|
|
A 'community' is the representation of an organization. Businesses with many partners can be split into two communities, one representing the business and the other grouping all of its partners. For each community, a single contact ('person' or 'company' contact information) can be designated as the representative.
Community fields
The table describes the sections of Community Data Entry page and explains how the fields in the page are used.
Mandatory Configurable
| Main Information | |
|---|---|
Name (of the community and used for new contact information) | |
| Contact Information | |
| Groups | |
| Displays the groups that belong to the community or which can be created and added by using Add New Group, available in the Actions menu or through the Groups Data Entry page. | |
| Units | |
| Displays the units that belong to the community, which can be added to a group through the Groups or Units Data Entry page. | |
| Users | |
| Displays the users that belong to the community, which can be added to a unit through the Units or Users Data Entry page. |
| Anchor | ||||
|---|---|---|---|---|
|
A group represents a department within an organization such as sales, marketing or finance or a partner. For each group, a single contact ('person' or 'company' contact information) can be designated as the representative.
Group fields
The table describes the sections of Group Data Entry page and explains how the fields in the page are used.
Mandatory Configurable
| Main Information | |||
|---|---|---|---|
Name Classification: 'Internal' or 'Partner' (for information). Partners must have an accounts receivable. Set up an Accounts Receivable on: For partner classification only. Select between:
Is Single Unit: One unit must be created only and assigned to the group. | |||
| Contact Information | |||
Details of the new representative. The contact information is created automatically and takes the name of the group. | |||
| Covered Geographical Areas | |||
New records are assigned to a group (through the 'Owned by Group' field), which designates the users that can access the record. Geographical areas can also be assigned to specific groups, making it possible for the system to automatically assign a group to new records by using the group's geographical area. Refer to Automatic assignments based on geographical areas for more information. Set as Owner Group automatically based on Covered Geographical Areas Area, District, Town/City and Postal Code can be definedas conditions. Conditions defined in the same row must all be met. | |||
Units | |||
Displays the units that belong to the group or which can be created and added by using Add New Unit, available in the Actions menu or through the Units Data Entry page. | |||
Users | |||
Displays the users that belong to the group, which can be added to a unit through the Units or Users Data Entry page. | |||
| Anchor | ||||
|---|---|---|---|---|
|
A unit represents a team within a department such as team leaders and operators or could be partners under the umbrella of a partner group. For each unit, a single contact ('person' or 'company' contact information) can be designated as the representative.
Unit fields
The table describes the sections of Units Data Entry page and explains how the fields in the page are used.
Mandatory Configurable
| Main Information | |||
|---|---|---|---|
Name Classification: 'Internal' or 'Partner' (for information). Partners must have an accounts receivable. Group (that the unit belongs to) Community (that the unit belongs to) Accounts Receivable (created for the unit if required by its group)
| |||
| Contact Information | |||
Details of the new representative. The contact information is created automatically and takes the name of the unit. Same as Group: The contact information of the unit's group is selected. This option is available if the classification of the associated group is set to 'Internal' or if the classification is set to 'Partners', in which case the Set up an Accounts Receivable on field (of the group) should be set to 'Partner group' (I.e., if an account must be created for every unit, then the contact information of the group cannot be used). | |||
Covered Geographical Areas | |||
New records that necessitate user input to complete are assigned to a unit or user. E.g., when a new activity is created for an installation, the activity is assigned to the installer team so that one of the installers will complete the installation. Geographical areas can also be assigned to specific units, making it possible for the system to automatically assign a unit to new records, using the unit's geographical area. Refer to Automatic assignments based on geographical areas for more information. Assign Unit automatically based on Covered Geographical Areas Area, District, Town/City and Postal Code can be defined as conditions. Conditions defined in the same row must all be met. | |||
Sub Units | |||
Displays all of the unit's sub-units, which can be created and added to the unit by using Add New Sub Unit, available in the Actions menu of the unit Data Entry page. | |||
Users | |||
Displays the users that belong the unit. Once units are set up, new users can be created and existing users added from other units, through the Actions menu:
| |||
| Anchor | ||||
|---|---|---|---|---|
|
Community collaboration profiles are used when groups belonging to different communities share data. For more information on collaboration, refer to Group Collaboration Profiles.
Community Collaboration Profiles fields
The table describes the sections of Community Collaboration Profiles Data Entry page and explains how the fields in the page are used.
Mandatory Configurable
| Main Information | |
|---|---|
Community (that will allow its groups to share data through group collaboration profiles) Collaboration Scope: Define whether data from groups of this community will be shared with groups of 'Specific' or 'All' Communities. | |
Collaboration with Communities | The 'Specific Communities' with which the community shares data. |
| Inward Collaboration | |
View existing community collaborations established through an explicit definition (specific community) or through collaboration with 'All Communities' and either:
| |
| Note |
|---|
Set default under Partner Settings: Foundation > Platform > Admin Settings > General Settings. The rewards module uses account information to credit or debit partners (represented by groups and units) through reward settlement runs. |
| Anchor | ||||
|---|---|---|---|---|
|
CRM.COM data is subject to different levels of access. The level of access depends on the group (or business department) of the user.
For example, if customer Z belongs to group A then only users belonging to group A will have access rights to customer Z entries.
Data can be shared between groups (departments) by setting up group collaborations and defining restrictions on:
- View
- Modify
- Assign
- Search
| Note |
|---|
Group collaborations do not apply to Controlled Selection Entities. I.e., if Group A is set as an |
Group collaboration profile fields
The table describes the sections of Group Collaboration Profiles Data Entry page and explains how the fields in the page are used.
Mandatory Configurable
| Main Information | ||||||
|---|---|---|---|---|---|---|
Group (that will share its data) Community: Read-only and determined by the selected group. Collaboration Scope: Define whether data from the group will be shared with 'Specific' ' or 'All' Groups. | ||||||
| Collaboration Settings | ||||||
If the 'Specific Groups' collaboration scope is selected, then collaboration settings are defined for each group. Start by Adding the group and defining the settings. For the 'All Groups' collaboration scope the actions are only defined once. Collaboration Settings: Define access restrictions to shared data. For each restriction, you can define which data will be shared and its access level ('None', 'All Privacy Levels', 'Specific Privacy Level', 'Specific Privacy Level Groups').
| ||||||
View My Records
| Defines the data (if any) that will be available for other groups to view.
| |||||
| Modify My Records (Includes View) | Defines the data (if any) that will be available for other groups to view and modify.
| |||||
| Assign My Records (Includes View & Modify) | Defines the data (if any) that will be available for other groups to view, modify or assign (for Assignable Entities).
| |||||
| Share My Groups | Defines whether the group will be available in (Data Entry page) search results and for use as a value in group-related fields of various modules.
| |||||
| Share My Units | Defines whether the units of the group will be available in (Data Entry page) search results and for use as a value in unit-related fields of various modules.
| |||||
| Share My Users | Defines whether the users of the group will be available in (Data Entry page) search results and for use as a value in user-related fields of various modules.
| |||||
| Inward Collaborations | ||||||
View the existing group collaborations that share their data with this group, either through an explicit definition or through collaboration with all groups. There are two options: View existing group collaborations established through an explicit definition (Specific Group) or through collaboration with 'All Groups' and either:
| ||||||
Related Configuration Areas
The following optional modules are related to network management and can be configured for the network management module to operate at its full capacity.
Manual Link | Area | Description |
|---|---|---|
| Platform | General Settings | Set up the default value ('Group' or 'Unit' level) for creating accounts receivable for partner groups. |
| Security Management | Privacy Level & Privacy Level Groups | Configure the privacy level and privacy level groups which can be used in group collaboration profiles as conditions for sharing data. |
Using Network Management
Cloning groups and collaborations
...
Groups and collaborations (between groups and between communities) can be cloned to save time.
When a group is cloned all of its attributes are automatically replicated in the new group (such as its classification (e.g., partner group), the number of its units, and the number of accounts of each unit).
When a community collaboration is cloned, all of the communities that the community collaborates with are replicated in the new collaboration profile.
To clone any of the above entities, use Clone (entity) from the Actions menu of the respective page and provide the required information.
| Anchor | ||||
|---|---|---|---|---|
|
Groups and units can be assigned automatically on new or existing records using common geographical areas. For example, the system can assign an installer from the same area (e.g., US postcode MA20155) as that of the customer who requested the installation.
Units are assigned to 'assignable entities' and represent the teams responsible for performing the task. Groups are assigned to 'explicit viewing access entities' and represent the departments that own and have full access rights to the record.
Unit assignment
Units can be assigned automatically based on covered geographical areas provided the feature is enabled through Units. Unit assignment is applicable for entities that require that a task is completed by a user. The following are Assignable Entities:
- Activities
- Leads
- Service Requests
- Jobs
A unit is automatically assigned to an entry provided that the customer is located within the covered geographical area.
The system compares the address of the customer to the geographical areas covered by each unit and assigns a unit when a match is found (see table below). Automatic assignment cannot take place if more than one unit covers the area.
| Assignable Entities | Entity Address Compared To Geographical Area |
|---|---|
Activity Lead Service Request | All active addresses of the related contact information. |
| Job | Job location |
| Note |
|---|
The system initially refers to Automatic Collaboration Rules (ACRs), which also offer the option to automatically assign units based on geographical area. If a match is not found the system subsequently checks the unit configuration. |
Group assignment
'Owned by Group' of entries can be based on covered geographical areas if the feature is enabled through Groups.
'Owned by Group' is only associated with explicit viewing access entities (entities for which the owner group is defined on the record). A group will automatically be set as the 'Owner' of entries provided that the customer is located within the covered geographical area.
The system will compare the address of the customer to the geographical areas covered by each group and will assign a group when a match is found (see table below).
In each case, the system will compare the customer address, according to the table below, against the covered geographical areas of each group and will assign a group when a match is found. If more than one group covers the area the assignment is not automatic.
| Explicit Viewing Entities | Entity Address Compared To Geographical Area |
|---|---|
Subscription | Subscription location |
Job | Job location |
Accounts Receivable Communications Contact Information Leads Activities Service Requests | All active addresses of the related contact information. |
Resource Plans Warehouses Reward Offers | Not set automatically. |
Network Management Business Examples
...
Set up Network Management for your business network
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Scenario 1 Company ZX wants to set up its Network Management for two Organisational Units organizational units (External Internal and InternalPartner) with the following structure: Solution Communities Create a Community for External Organisational Units.Classify the Community as External.
Groups
Units
Users (User Management)
|
Automatic Group Assignment
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Scenario 2 Company ZX wants to set the 'Owned By Group' of all the applicable entities based on the area that in which the customer is resding located, as the information will always be handled by departments in the respective location departments. There are three 'Owned By Groups': London, Birmingham, and Manchester.
Solution
|
| Note | ||
|---|---|---|
| ||
|
Glossary
| CRM.COM Term | Definition |
|---|---|
| Organisational Unit | Used to organise A unit, group or community, used to organize the company’s network. Communities, Groups and Units are all considered Organisational Units. |
| Privacy Level | Assigned on single records and provides a hierarchical level of privacy used to control sharing of the record as well as visibility and modification, A numeric value (ascending with higher privacy) used to control access to view and modify data shared between organizational units. |
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Links
|