Changes

Jump to: navigation, search

Organization hierarchy

1,829 bytes added, 17:31, 6 June 2019
no edit summary
==Configuration—Advanced==
===Filter Owner Based on Branch===
The contacts available to be selected in the [[Level 1 Entity]] Owner [[standard field]] for an organization can be restricted to those belonging to the related [[branch]] (an organization record subordinate to another organization in the company hierarchy) and its sub-organizations. The branch must be selected first in the standard field at level 1. 
 
This function is enabled on the main UTA Settings Page in the Level 1 Setting section. 
 
1. Click the 9-square menu icon on the top right of your page.
 
:: {{Icon-Menu}} 
 
2. Under the '''Configuration '''heading, select '''Tracking''' '''Applications '''and then select the '''Edit '''button (pencil icon) next to the specific application you want to configure. ''' '''
 
'''* '''Alternatively, you can select the specific [[Universal Tracking Application]] you want to restrict the owner choices for under the heading '''Applications.'''
 
:: [[File:060619_1.png|400px|border]]
 
3. Under the second tab''', '''select '''Standard Fields. '''
 
* Note: The second tab is your [[Level 1 Entity]]; the nomenclature will differ depending on the application. You can confirm what the Level 1 Entity is for a specific application by looking under the first tab, '''General, '''and finding the label for '''Tracking Object Label. '''
 
:: [[File:Standard fields.png|250px|border]] 
 
4. Within the list of standard fields, select the field with the name '''Owner. '''The field details will be displayed.
 
5. Under '''Feature Options''', toggle on '''Filter Lookup Results by Branch. '''
 
:: [[File:Filter lookup results by branch.png|400px|border]] 
 
* With the other '''Feature Options, '''you may choose other configurable restrictions for this standard field, such as Lookup restrictions for specific [[Roles]] and so on. 
 
===Organization Based Security===
Organization security is based on the user's organization in the overall hierarchy.  
* You permission an organization to access a resource, and everyone in that organization will be able to access that resource.
* When you add new people to that organization, they will also automatically gain access to the resource. '''Advantages''': * When you create a user in an organization, you will not have to take the extra step to set any specific permission for the user to access a resource. The user will instead have "inherited" access by being associated with that organization.
'''AdvantagesNote''': * When you create a user in an organization, you will not have to take the extra step to set any specific permission for the user to access a resource. The user will instead have "inherited" access by being associated with that organization.
'''Note''':
* Organization security does not allow you to give individual users from different organization access to the resource.
* You must associate each organization with the resource; giving multiple organizations access must mean repeating the process. * If you "move" the user to another organization, they will automatically lose access to resources associated with their previous organization.
[[Category:System Management]][[Category:Glossary]]
2,299
edits

Navigation menu