Difference between revisions of "Organisation"

From Hornbill
Jump to navigation Jump to search
(41 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;">
+
{{DISPLAYTITLE:Organization}}
__NOTOC__
+
{{bluebanner|[[Main Page|Home]] > [[Administration]] > [[System Administration|System]] > [[Organisational Data|User and Guest Access]] > Organization|[[:Category:Administration|Index]]}}
{| style="width:100%"
+
{{IntroAndLinks|
|[[Main Page|Home]] > [[Administration]] > [[System Administration|System]] > [[Organisational Data]] > Organisation
+
The Hornbill platform allows a hierarchical Organizational Structure to be defined within your instance which, when members are added to each of the business units, can greatly assist in providing a solid foundation on which current and future Hornbill Application functionality operates.
|style="text-align:right;"|[[:Category:Administration|Index]]
 
|}
 
</div>
 
{|style="width: 100%"
 
|- valign="top"
 
|style="width:73%"|
 
==Introduction==
 
The Hornbill platform allows a hierarchical Organisational Structure to be defined within your instance which, when members are added to each of the business units, can greatly assist in providing a solid foundation on which current and future Hornbill Application functionality operates.
 
 
<br>
 
<br>
 
<br>
 
<br>
Whether your structure consists of simply a single "Company", "Department", and Support Team (which is all you need to get started) or a more complex and multi-layered configuration including multiple Divisions, and Cost Centers, the correct definition is a key aspect in utilising the Hornbill Platform to it's maximum.
+
Whether your structure consists of simply a single "Company", "Department", and Support Team (which is all you need to get started) or a more complex and multi-layered configuration including multiple Divisions, and Cost Centers, the correct definition is a key aspect in utilizing the Hornbill Platform to it's maximum.|
|style="width:5%"|
 
|
 
|style="width:22%; border-style: solid; border-width: 1px; border-color:#e6e6e6; background-color:#f2f2f2;"|
 
 
 
== Related Articles ==
 
 
:* [[Users]]
 
:* [[Users]]
|}
+
:* [[Sites]]
 +
:* [[Custom Buttons]]
 +
}}
  
==Types of Business Units (Groups)==
+
== Organization List==
Each business unit you define within Hornbill should be considered a Group. When creating a Group you will be required to specify a Type against that Group.
+
[[file:Organisationbreadcrumb.png|350px|right]]
 +
The Organization List contains the groups that make up your organization. The list forms a hierarchical structure where you can create an browser through the different levels of your organization. The ''Breadcrumb'' displayed at the top of the list highlights where you are within each level of your organization and lets you navigate back up to the higher levels.
 +
 +
===Types of Groups===
 +
{{#ev:youtube|SmS_rCkX-w4|400|right}}
 +
Groups are available to define different business units. When creating a Group you will be required to specify a Type against that Group.
 
There are six Group Types available, the default being "General".
 
There are six Group Types available, the default being "General".
 
<br>
 
<br>
 
:* '''Company'''
 
:* '''Company'''
::Logically, this will be the Type set against the Group that sits at the top of your heirarchy, and which all other Groups sit beneath. It's entirely possible that you have more than one Group of Type "Company", where they sit in the heirarchy will be dependant on a "Parent" Group being specified upon creation.
+
::Logically, this will be the Type set against the Group that sits at the top of your hierarchy, and which all other Groups sit beneath. It's entirely possible that you have more than one Group of Type "Company", where they sit in the hierarchy will be dependent on a "Parent" Group being specified upon creation.
  
 
:* '''Division'''
 
:* '''Division'''
::This is a section of a large company that can be divided into an organisational function – often by product or geography. Each Division can contain the necessary resources to support that product line or geography (i.e. its own Departments)
+
::This is a section of a large company that can be divided into an organizational function – often by product or geography. Each Division can contain the necessary resources to support that product line or geography (i.e. its own Departments)
  
 
:* '''Department'''
 
:* '''Department'''
::This is a specialised functional area within a Company (or Division) – this is often based on functions, products, customers, geographies or processes.  
+
::This is a specialized functional area within a Company (or Division) – this is often based on functions, products, customers, geographies or processes.  
  
 
:* '''Costcenter'''  
 
:* '''Costcenter'''  
 
::This is a defined area or person to which direct and indirect costs are allocated.  
 
::This is a defined area or person to which direct and indirect costs are allocated.  
 
:* '''Team'''
 
::A team is a group of users with a set of complimentary skills, organised to work together to complete a task job or project. In Hornbill, a team is a group to which requests can be assigned. If you wish to define other teams in your structure, but do not want them to be visible in a Hornbill Service Manager Request-assignment situation, then you should specify the Group Type as "General".
 
  
 
:* '''General'''
 
:* '''General'''
::This is a generic container that can be used for any area that has not been defined above. For example, a team that should not be assigned requests may fall under this group type.  
+
::This is a generic container that can be used for any area that has not been defined above. For example, a team that should not be assigned requests may fall under this group type.
 
+
<br>
 +
{{infobox|'''Reporting Hint'''
 +
::Groups are stored in the table ''h_sys_groups'' and the types described above are represented by an integer value between 0 and 5 in a column called ''h_type''. These are as follows: <nowiki> 0=general, 1=team, 2=department, 3=costcenter, 4=division, 5=company</nowiki>. The group type may be useful when creating measures, widgets, and reports.}}
  
==Creating a New Group==
+
===Creating a New Group===
 
[[File:New Organisation Form.png|350px|right|link=https://wiki.hornbill.com/images/9/96/New_Organisation_Form.png|New Group Form]]
 
[[File:New Organisation Form.png|350px|right|link=https://wiki.hornbill.com/images/9/96/New_Organisation_Form.png|New Group Form]]
Your Organisational Structure is created and managed via Hornbill Administration.  From the Home page navigate to ''System->Orgnisational Data->Organisation''.  Using the ''Create New'' button in the tool bar you can begin to add your organisation structure.
+
Your Organizational Structure is created and managed via Hornbill Administration.  From the Home page navigate to ''System->User and Guest Access->Organization''.  Using the ''Create New'' button in the tool bar you can begin to add your organization structure.
  
:* '''Organisation Id'''  
+
:* '''Organization Id'''  
 
:: This is the unique identification of the group. This value should not contain any spaces or special characters. Organisation ID's cannot begin with a numeric digit, must be at least two characters long and are limited to a maximum of 160 characters and can only contain: Letters, Numbers and Underscores. Please be aware, that once the ID has been saved, it cannot be amended. If this new Group has a parent, then the ID will be constructed using the ID that you specify as well as being prefixed (upon clicking create) with the ID(s) of any parent groups.
 
:: This is the unique identification of the group. This value should not contain any spaces or special characters. Organisation ID's cannot begin with a numeric digit, must be at least two characters long and are limited to a maximum of 160 characters and can only contain: Letters, Numbers and Underscores. Please be aware, that once the ID has been saved, it cannot be amended. If this new Group has a parent, then the ID will be constructed using the ID that you specify as well as being prefixed (upon clicking create) with the ID(s) of any parent groups.
 
   
 
   
Line 69: Line 62:
 
:* '''Notes'''  
 
:* '''Notes'''  
 
:: A free text field to record any additional information regarding the group.
 
:: A free text field to record any additional information regarding the group.
 +
<br>
  
==Editing an Existing Group==
+
===Editing an Existing Group===
 
To edit an existing group:
 
To edit an existing group:
 
<ol>
 
<ol>
<li> Via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organisations'' menu item, and then the ''Organisation'' option.</li>
+
<li> Via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organizations'' menu item, and then the ''Organization'' option.</li>
 
<li> Click the group that requires editing</li>
 
<li> Click the group that requires editing</li>
 
<li> The following options are available to edit:</li>
 
<li> The following options are available to edit:</li>
Line 86: Line 80:
 
<br>
 
<br>
  
==Deleting a Group==
+
===Deleting a Group===
 
[[File:Deleting a Group.png|350px|right|link=https://wiki.hornbill.com/images/9/94/Deleting_a_Group.png|Deleting a Group]]
 
[[File:Deleting a Group.png|350px|right|link=https://wiki.hornbill.com/images/9/94/Deleting_a_Group.png|Deleting a Group]]
 
To delete an existing group, via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organisations'' menu item, then the ''Organisation'' option and do the following:
 
To delete an existing group, via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organisations'' menu item, then the ''Organisation'' option and do the following:
Line 92: Line 86:
 
<ol>
 
<ol>
 
<li> Ensure that there are no users assigned to that group (this can be checked by clicking the "Assigned Users" tab available when viewing the Group details). If there are, remove them by following the process described in the section ''Removing Users from a Group''. '''If the Group is of type "Team", it is also prudent to check that there are no Service Manager requests currently assigned to that team and take action to re-assign those requests before the Group is deleted.''' </li>
 
<li> Ensure that there are no users assigned to that group (this can be checked by clicking the "Assigned Users" tab available when viewing the Group details). If there are, remove them by following the process described in the section ''Removing Users from a Group''. '''If the Group is of type "Team", it is also prudent to check that there are no Service Manager requests currently assigned to that team and take action to re-assign those requests before the Group is deleted.''' </li>
<li> From the Organisation Structure list, select the group to be removed by ticking the checkbox on the left hand side of its name</li>
+
<li> From the Organization Structure list, select the group to be removed by ticking the checkbox on the left hand side of its name</li>
 
<li> Click the arrow next to the “Create New” button – and click the “Delete Selected” option.</li>  
 
<li> Click the arrow next to the “Create New” button – and click the “Delete Selected” option.</li>  
  
 
<li> Click OK when presented with the “Are you sure" prompt</li>
 
<li> Click OK when presented with the “Are you sure" prompt</li>
<li> The group has now been removed from your Organisational Structure</li>
+
<li> The group has now been removed from your Organizational Structure</li>
 
</ol>
 
</ol>
 
<br>
 
<br>
  
==Group Membership - Associating Users to a Group==
+
===Group Membership - Associating Users to a Group===
[[File:Search and Associate Users.png|350px|right|Associating Users to a Group]]
+
[[File:Search and Associate Users.png|350px|right|link=https://wiki.hornbill.com/images/8/81/Search_and_Associate_Users.png|Associating Users to a Group]]
Once you have created your Organisational Structure, Users can be given Group Membership by assigning them to a desired group. via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organisations'' menu item, then the ''Organisation'' option and do the following:
+
Once you have created your Organisational Structure, Users can be given Group Membership by assigning them to a desired group. via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organizations'' menu item, then the ''Organization'' option and do the following:
 
<br>
 
<br>
 
<ol>
 
<ol>
Line 121: Line 115:
 
<br>
 
<br>
  
==Removing Users from a Group==
+
===Removing Users from a Group===
 
[[File:Removing Users from a Group.png|350px|right|link=https://wiki.hornbill.com/images/f/f7/Removing_Users_from_a_Group.png|Associating Users to a Group]]
 
[[File:Removing Users from a Group.png|350px|right|link=https://wiki.hornbill.com/images/f/f7/Removing_Users_from_a_Group.png|Associating Users to a Group]]
If a user(s) no longer needs to reside in a group, via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organisations'' menu item, then the ''Organisation'' option and do the following:
+
If a user(s) no longer needs to reside in a group, via Hornbill Administration, in the context of Instance Configuration, select the ''Users, Roles & Organizations'' menu item, then the ''Organization'' option and do the following:
 
<br>
 
<br>
 
<ol>
 
<ol>
Line 133: Line 127:
 
<li>The user(s) is now removed from the group.</li>
 
<li>The user(s) is now removed from the group.</li>
 
</ol>
 
</ol>
 +
 +
== Team List ==
 +
A team is a group of users with a set of complimentary skills, organized to work together to complete a task job or project. In Hornbill, a team is a group to which requests can be assigned. Team members can only consist of users that have a subscription to Hornbill.
 +
  
 
[[Category:Administration]]
 
[[Category:Administration]]

Revision as of 00:35, 10 April 2021

Home > Administration > System > User and Guest Access > Organization Index

Introduction

The Hornbill platform allows a hierarchical Organizational Structure to be defined within your instance which, when members are added to each of the business units, can greatly assist in providing a solid foundation on which current and future Hornbill Application functionality operates.

Whether your structure consists of simply a single "Company", "Department", and Support Team (which is all you need to get started) or a more complex and multi-layered configuration including multiple Divisions, and Cost Centers, the correct definition is a key aspect in utilizing the Hornbill Platform to it's maximum.

Related Articles

Organization List

Organisationbreadcrumb.png

The Organization List contains the groups that make up your organization. The list forms a hierarchical structure where you can create an browser through the different levels of your organization. The Breadcrumb displayed at the top of the list highlights where you are within each level of your organization and lets you navigate back up to the higher levels.

Types of Groups

Groups are available to define different business units. When creating a Group you will be required to specify a Type against that Group. There are six Group Types available, the default being "General".

  • Company
Logically, this will be the Type set against the Group that sits at the top of your hierarchy, and which all other Groups sit beneath. It's entirely possible that you have more than one Group of Type "Company", where they sit in the hierarchy will be dependent on a "Parent" Group being specified upon creation.
  • Division
This is a section of a large company that can be divided into an organizational function – often by product or geography. Each Division can contain the necessary resources to support that product line or geography (i.e. its own Departments)
  • Department
This is a specialized functional area within a Company (or Division) – this is often based on functions, products, customers, geographies or processes.
  • Costcenter
This is a defined area or person to which direct and indirect costs are allocated.
  • General
This is a generic container that can be used for any area that has not been defined above. For example, a team that should not be assigned requests may fall under this group type.


Information
Reporting Hint
Groups are stored in the table h_sys_groups and the types described above are represented by an integer value between 0 and 5 in a column called h_type. These are as follows: 0=general, 1=team, 2=department, 3=costcenter, 4=division, 5=company. The group type may be useful when creating measures, widgets, and reports.

Creating a New Group

New Group Form

Your Organizational Structure is created and managed via Hornbill Administration. From the Home page navigate to System->User and Guest Access->Organization. Using the Create New button in the tool bar you can begin to add your organization structure.

  • Organization Id
This is the unique identification of the group. This value should not contain any spaces or special characters. Organisation ID's cannot begin with a numeric digit, must be at least two characters long and are limited to a maximum of 160 characters and can only contain: Letters, Numbers and Underscores. Please be aware, that once the ID has been saved, it cannot be amended. If this new Group has a parent, then the ID will be constructed using the ID that you specify as well as being prefixed (upon clicking create) with the ID(s) of any parent groups.
  • Name
This is the user friendly name for the group. This can be amended at any time after the Group has been created.
  • Parent
This is how the hierarchy is defined. Here, the direct parent of the group should be specified. For example, if creating a division, the organisation may be selected as a parent. Be aware, that once the Parent has been saved, it cannot be amended.
  • Type
This is a drop-down list, specifying the type of group that is being created (Company, Division, Department, Costcenter, Team or General)
  • Allow Task Assignment
This flag indicates whether activities can be assigned to the Group as a whole. It is possible to configure the Business Process Workflow to assign tasks to a group.
  • Attributes 1 to 9
These fields are currently not used.
  • Notes
A free text field to record any additional information regarding the group.


Editing an Existing Group

To edit an existing group:

  1. Via Hornbill Administration, in the context of Instance Configuration, select the Users, Roles & Organizations menu item, and then the Organization option.
  2. Click the group that requires editing
  3. The following options are available to edit:
  4. a. Name
    b. Type
    c. Allow Task Assignment
    d. Attributes and Notes
    Currently, it is not possible to change the ID or the Parent of the group.
  5. Click the “Save Changes” button to confirm any amendments


Deleting a Group

Deleting a Group

To delete an existing group, via Hornbill Administration, in the context of Instance Configuration, select the Users, Roles & Organisations menu item, then the Organisation option and do the following:

  1. Ensure that there are no users assigned to that group (this can be checked by clicking the "Assigned Users" tab available when viewing the Group details). If there are, remove them by following the process described in the section Removing Users from a Group. If the Group is of type "Team", it is also prudent to check that there are no Service Manager requests currently assigned to that team and take action to re-assign those requests before the Group is deleted.
  2. From the Organization Structure list, select the group to be removed by ticking the checkbox on the left hand side of its name
  3. Click the arrow next to the “Create New” button – and click the “Delete Selected” option.
  4. Click OK when presented with the “Are you sure" prompt
  5. The group has now been removed from your Organizational Structure


Group Membership - Associating Users to a Group

Associating Users to a Group

Once you have created your Organisational Structure, Users can be given Group Membership by assigning them to a desired group. via Hornbill Administration, in the context of Instance Configuration, select the Users, Roles & Organizations menu item, then the Organization option and do the following:

  1. Click the group in which user(s) need to be assigned
  2. Click the “Assigned Users” Tab
  3. Click the “Add Users” button. A form is displayed with the following options:
    • Search Users
    Begin typing the name of the user to assign to the group, click the name to select them
    • Membership
    Select whether the user is a Member, Team Leader, or Manager of the group.
    • Allow Viewing Tasks
    Allows the User to view tasks that are assigned to the Group
    • Allow Actioning Tasks
    Allows the User to action tasks that are assigned to the Group
  4. Once complete, click the Add Userbutton”. Repeat the process of adding users until all have been added, and then clickClose


Removing Users from a Group

Associating Users to a Group

If a user(s) no longer needs to reside in a group, via Hornbill Administration, in the context of Instance Configuration, select the Users, Roles & Organizations menu item, then the Organization option and do the following:

  1. Click the group from which user(s) need to be removed
  2. Click the “Assigned Users” Tab
  3. Select the users to be removed by ticking the checkbox on the left hand side of their name
  4. Click the arrow next to the “Add Users” button – and select the “Remove from Group” option.
  5. Click OK when presented with the “Are you sure" prompt
  6. The user(s) is now removed from the group.

Team List

A team is a group of users with a set of complimentary skills, organized to work together to complete a task job or project. In Hornbill, a team is a group to which requests can be assigned. Team members can only consist of users that have a subscription to Hornbill.