Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Dashboard page options drop-down

Received Response
135
Views
17
Comments
Charles M
Charles M Rank 6 - Analytics Lead
edited Aug 13, 2024 5:47PM in Oracle Analytics Cloud and Server

Hi -

We have just disabled/removed some Dashboard Report Links (such as Analyze, Edit, etc.). However, I can still see the page options drop-down, which allows for editing the dashboard properties. Is there a way to remove or disable this, so that users wouldn't have the ability to access it?

pastedImage_0.png

OBIA 11.1.1.10.1 / OBIEE 11.1.1.9.3

Regards,

Charles

«1

Answers

  • SonPat99
    SonPat99 Rank 6 - Analytics Lead

    Dear Charles,

    You will have to give Read-Only (OPEN) access to the catalog to make this go away.

  • Martin van Donselaar
    Martin van Donselaar Rank 6 - Analytics Lead

    What (exactly) did you do already and what are you trying to achieve? To be honest what you are trying to do seems like a bad idea.

    Why would you grant a user permission to edit dashboards and then take away the tool to do so to make sure he doesn't? That makes no sense to me.

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Hi Martin,

    Thanks for the reply. Let me clarify ...

    We don't want either one (that's what I am saying). We removed the Analysis Analyze link already. And, we want to do the same for the 'Edit Dashboard' option. These are dashboards developed by IT, and placed under the shared folder for others to use, but not edit/modify.

    I logged in as a non-admin, non-dashboard owner account and was able to see the 'Edit Dashboard' option. I know we have a custom role ... I'm wondering if that has something to do with this?

    Regards,

    Charles

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Making the object isn't enough for you? If you remove the whole menu then the print/export options as well as the ability to create and use customizations will be gone and that's a heavy incision into the capabilities of the tool that you offer to your end users.

    Keeo it read-only but leave the other options - that's my counsel. Think of the users and don't take away functionality for the sake of a fake gain in security

  • SonPat99
    SonPat99 Rank 6 - Analytics Lead

    @Charles M

    Exactly my point to keep it OPEN (read Only)

    Thank you @Christian Berg Sir for confirming the same...

  • Martin van Donselaar
    Martin van Donselaar Rank 6 - Analytics Lead

    Like both Christian and the nameless person confirmed: You need to handle this through setting the roles access permissions

    So, find the dashboard objects in your catalog and remove the write and delete permissions

    pastedImage_1.png

    Acquaintance yourself with the OBIEE Security Architecture, you can start by reading:

    https://docs.oracle.com/middleware/12211/biee/BIESC/GUID-10AB239C-7B14-4652-856B-8716A753592E.htm#BIESC793

    https://www.rittmanmead.com/blog/2012/03/obiee-11g-security-week-understanding-obiee-11g-security-application-roles-and-…

    https://www.rittmanmead.com/blog/2012/03/obiee-11g-security-week-managing-application-roles-and-policies-and-managing-se…

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Thanks Martin, Christian, and unamed-user . Let me take a look at the materials, and review the capabilities. I'll reply back with some comments/questions.

    In the meantime, are we saying that: it is possible to leave the analysis link enabled/visible, and control for editing/deleting through the catalog permissions? So, in such a case, a user could use the analysis link to view the criteria, etc. ... but, could not alter or delete anything?

    Also, would the owner/creator always have "full" access to the object,or is it totally based on the role?

    Thanks for helping with this.

    Regards,

    Charles

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Role based. Better never even try to do things on a user basis. You won't ever see the end of managing things one by one

  • SonPat99
    SonPat99 Rank 6 - Analytics Lead

    Adding to Mr. Berg's solution, it all comes to just adding to users to Roles:

    Let's say there are 2 users:

    USER A- Creator of these reports

    USER B- Who will be seeing these reports, but cannot edit these reports

    Create two custom Roles (ROLE A and ROLE B) and add BI CONTENT AUTHOR (Role A) and BI CONSUMER (Role B) respectively for the roles created.

    Assign these roles to USER A and USER B respectively.

    Now, USER A will have read-write access to this dashboard/analysis and USER B will have only READ access to this dashboard/report.

    USER A -- Analysis link will not be visible for this user

    Please go through the documents already shared and try to understand the concepts of Roles and Users.

    Note: You can skip the step of creating different Roles if you have a simple requirement for this report only. In that case, just add the users to BI Content Author and BI Consumer.

    Hope this helps...

    Regards,

    Sonkar (not un-named now.. )

  • Martin van Donselaar
    Martin van Donselaar Rank 6 - Analytics Lead

    Sonkar,

    If you are planning to post more on this forum and help others I suggest you set a more meaningful display name, that will make it easier to keep track of "who said what"