Difference between revisions of "Application Scope Access"

From SmartWiki
Jump to: navigation, search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''UTA Application Scope Access''' -
+
The '''UTA Application Scope Access''' feature on the [[UTA Settings - Settings|Settings]] page of all {{UTAs}} allows you to assign a designated [[Role|role]] played by a [[User|user]] for a specific branch or company. In other words, you can define implicit permission for a given user to UTA objects without them being explicitly indicated on a record.
  
The '''UTA Application Scope Access''' feature on the '''Settings''' page of all [[UTA]]s allows you to assign a designated [[Role|role]] to a [[User|user]] if branch or company of a '''Level 1''' instance is in the list. In other words you can define implicit permission on/in a UTA without them being explicitly indicated on a record. It also lets you associate the permissions of an individual to those of a particular company.
+
''Impact'':  A [[User|user]] can now see the {{l1}} items of a company based on the [[Security Matrix|matrix permissions]] of the selected [[Role|role]], even if that individual is not assigned to the {{l1}} items.
  
Impact:  A [[User|user]] can now see the '''Level 1''' items of a company based on the matrix permissions of the selected [[Role|role]].
+
In the example below, "Rolf Lathrop" has been assigned as a "Manager" of "Abbeville Womens Equality." Rolf can see all of the {{l1}} items belonging to "Abbeville Womens Equality." His access will be restricted by the [[Security Matrix]] permissions of the "Manager" [[Role|role]].
  
In the example below, '''Alan Davis''' can see all of the '''Level 1''' items belonging to '''AAAA Couriers'''. When he looks at the '''Level 1''' items he will be restricted by the '''Security Matrix''' permissions of the '''Manager''' [[Role|role]].
+
These permissions mean that the [[User|user]] does not have to be directly attached to the {{l1}} item. They do not have to be the [[owner]], assigned or in an associated company in order to see the items.  
  
These permissions mean that the [[User|user]] does not have to be directly attached to the '''Level 1''' item. They do not have to be the owner or assigned or in an associated company in order to see the items.
+
[[Image:ApplicationScopeAccess.png|link=|750px]]
  
[[Image:Car2.png]]
+
==Enabling Application Scope Access==
 +
# On the [[UTA_Settings_-_Security|Security tab]] of the [[UTA Settings Page]], select "Enable Application Scope Access."
 +
# Scroll to the bottom of the page and hit "Save".
 +
# Now navigate to the [[UTA_Settings_-_Settings|Settings tab]] of the [[UTA Settings Page]].
 +
# In the first section of the page, click the hyperlink for "Application Scope Access".
  
[[Category:System Management]][[Category:Universal Tracking Application]][[Category:Applications]]
+
==Restricted Roles==
 +
When using Application Scope Access - the Lookup for selecting an external company can be restricted by selecting roles in ''Roles to Restrict Level One Lookup Using Scope Access Settings''. This setting applies to the {{l1}} standard field Company lookup, the UTA Contacts lookup, and the UTA Companies lookup.
 +
 
 +
''Impact'': When enabled, a user in one of the selected roles that clicks the Lookup button will only see the companies that they are associated with in the Application Scope Access list.
 +
 
 +
==See Also==
 +
* [[Security Matrix]]
 +
* [[UTA Settings - Security]]
 +
 
 +
[[Category:Universal Tracking Application]][[Category:Security]][[Category:UTA Settings]]

Latest revision as of 10:34, 21 November 2013

The UTA Application Scope Access feature on the Settings page of all Universal Tracking Applications™ allows you to assign a designated role played by a user for a specific branch or company. In other words, you can define implicit permission for a given user to UTA objects without them being explicitly indicated on a record.

Impact: A user can now see the Level 1 items of a company based on the matrix permissions of the selected role, even if that individual is not assigned to the Level 1 items.

In the example below, "Rolf Lathrop" has been assigned as a "Manager" of "Abbeville Womens Equality." Rolf can see all of the Level 1 items belonging to "Abbeville Womens Equality." His access will be restricted by the Security Matrix permissions of the "Manager" role.

These permissions mean that the user does not have to be directly attached to the Level 1 item. They do not have to be the owner, assigned or in an associated company in order to see the items.

ApplicationScopeAccess.png

Enabling Application Scope Access

  1. On the Security tab of the UTA Settings Page, select "Enable Application Scope Access."
  2. Scroll to the bottom of the page and hit "Save".
  3. Now navigate to the Settings tab of the UTA Settings Page.
  4. In the first section of the page, click the hyperlink for "Application Scope Access".

Restricted Roles

When using Application Scope Access - the Lookup for selecting an external company can be restricted by selecting roles in Roles to Restrict Level One Lookup Using Scope Access Settings. This setting applies to the Level 1 standard field Company lookup, the UTA Contacts lookup, and the UTA Companies lookup.

Impact: When enabled, a user in one of the selected roles that clicks the Lookup button will only see the companies that they are associated with in the Application Scope Access list.

See Also