The appropriate Catalog control is to set the dashboard object to Read-Only . Oracle Analytics allows administrators—and owners for objects they control—to open a catalog item's Properties and modify its access-related attributes. Oracle specifically gives setting an analytics object to read-only as an example of preventing other users from modifying the content.
This setting addresses the requirement directly because the dashboard remains available for consumption while modifications are restricted according to the object's permissions and ownership configuration. It is therefore preferable to mechanisms that would alter discoverability or content organization without enforcing edit protection.
Adding an object to Favorites merely creates a personal shortcut and has no security effect. Transferring ownership doesn't inherently prevent the new owner or other permitted users from modifying the dashboard. Renaming affects catalog references and naming, not write permissions. Archiving creates an archive representation for migration or backup purposes and doesn't constitute the normal method for protecting an active dashboard against edits.
Thus, the correct procedure is to locate the dashboard in the Catalog, open Properties , and configure the item as Read-Only .
Reference Topic: Managing Administration, Security, and Performance — Catalog Object Properties and Read-Only Content
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit