Thursday, 14 July 2011
Using Group Level Permissions instead of User Level
For ease of catalog administration, only assign permissions at a group level (as opposed to an individual user level) for objects in the web catalog (i.e. reports, pages, dashboards, prompts, etc.). Adding individual users to these elements makes maintenance difficult and costly. Also, you will save yourself many hours of “hunting and pecking” to determine who has access to what.
Subscribe to:
Post Comments (Atom)
Search My Blog and world of Internet
Popular Posts
-
ORACLE BI APPLICATIONS – IMPLEMENTATION & CUSTOMIZATION FOR ORACLE EBS from iWare Logic Technologies on Vimeo .
-
Some columns, such as Social Security Number (SSN), may contain sensitive information that should only be displayed to certain Users or Grou...
-
What is a FACT LESS FACT TABLE? Where we use Factless Fact? We know that fact table is a collection of many facts and measures having...
-
Difference between Dashboard and Scorecard Statistics Dashboards can be broader in scope, but still cover the same statistics that have bee...
-
OBIA - Overiew from Srinath D on Vimeo .
-
For ease of catalog administration, only assign permissions at a group level (as opposed to an individual user level) for objects in the web...
-
See the Webnier on Oracle Financial Analytics Mobile Application Demo http://medianetwork.oracle.com/media/show/16745 Cheers
-
"Work is hard if you're paid to do it and its pleasure if you pay to be allowed to do it." — Finley Peter Dunne (1867-1936...
-
FREE Webinar on Oracle SOA 11g on 23Jul and 26 Jul EDT REGISTER: Space is limited. Reserve your Webinar seat now at: http://soatraining.hp...
-
Urgently Looking for a direct end client position - Oracle BI Apps with Siebel CRM knowledge - San Jose, CA -Contract -Rates -Open - Exp- 8...
No comments:
Post a Comment