These additional values are available to use with your Organization values. These fields are not required but instead allow you further customization of your Issuetrak site.
When checked, users within this organization will only be able to view issues submitted by other users within this organization, depending on their user permissions, i.e. Can view issues submitted by other users. They will not be able to see issues submitted by users outside of this Organization. Likewise, they will not be able to see users from other Organizations in the various user-related fields in an issue or issue search, including Next Action, Task Assigned To, and more. In a customer support situation, all customer organizations usually have Internal Only checked, but the support organization does not. Thus, the support representatives can view all issues/users, but users in a customer organization can only see issues/users within their organization.
Additional Organizations Allowed
In cases where users within an Organization should not see all issues and users in your system but should be able to see the issues and users of select other Organizations, you would engage “Additional Organizations Allowed.” This functionality allows you to set up a multi-tier hierarchy often referred to as “Nested Organizations.”
Example: Suppose your company sells to dealers and those dealers sell to specific clients. The dealers support their clients, and your company supports the dealers. You would enter each of your dealers as separate Organizations and mark each dealer’s Organization as Internal Only. Dealer 1 and Dealer 2 would no longer be able to see each other’s issues or users.
All clients related to your dealers would also be entered as separate Organizations and marked Internal Only. Clients A, B, C and D would no longer be able to see each other’s issues or users, nor would they be able to see Dealer 1 or Dealer 2’s issues or users.
Under Dealer 1, you would “Add Additional Organizations” respective of Dealer 1’s client base, perhaps Clients B and C. Dealer 1 would now be able to see and maintain issues across their Organization as well as across Clients B and C. Clients B and C would still not be able to see Dealer 1’s issues, nor each other’s issues. Effectively, Dealer 1 becomes a ‘parent’ Organization to the ‘child’ Organizations, Customers B and C.
Selecting “Read Only” next to a child Organization will grant the parent Read Only access to the child’s issues. If “Read Only” is not selected, the parent will be able to access and maintain the child’s issues. Selecting “View Users” will make the child’s member users available to the parent within any of the user-related fields in an issue or issue search, e.g. Next Action, Task Assigned To, etc. If “View Users” is not selected, the parent will not see any of the child’s member users available in these fields in an issue or issue search.
In most Nested Organization scenarios, only “View Users” is selected next to the child Organizations, allowing the parent to view all member users and to maintain all the child’s issues.
This title will appear above the menu bar throughout the system after a member user of this particular organization has logged in.
Left Organization Logo
This logo will appear on the left above the menu bar throughout the system after a member user has logged in. Clicking on this logo will take the user to the Logo URL specified.
Right Organization Logo
This logo will appear on the right above the menu bar throughout the system after a member user has logged in. Clicking on this logo will take the user to the Logo URL specified.
Email sent from the system to users in this organization will use the Email Name and Email Address values entered here as default From/Reply To values. If left blank, System Defaults for outgoing email will be used.
Export to Excel
The list of organizations can be exported to an MS Excel file automatically by choosing the menu options Administration > Organization Export to Excel. A dialog box will appear with the options to Open, Save, or Cancel the operation.
Email Distribution Lists
Organization-based Email Distribution Lists can be defined, allowing you to select a list of users to be notified when specific issue events occur based on the Organization submitting an issue. These events include: submit, assign, next action, note entered, close and escalation.
An auxiliary field for providing the website or domain of an organization. Prior to 11.6, this field was used to help determine the organization that an email sender should be assigned to.
IEM Email Domain
This field is used by IEM to determine the organization that an email sender should be assigned to.