Skip to Content
author's profile photo Former Member
Former Member

acess right with (user owns)

Hi,

This is for BI 4.1. I have user access to only the right which the user owns, like Edit objects which user owns etc.

Now this may cause a concern once the user leaves or moves on to something else.

The other user will not be able to change the object because he/she does not owns it. Is there any recommended method other than using Admin ID for changing the user?

Please advise.

Regards,

SS

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2014 at 04:05 PM

    Hi Surendra,

    You should create User Group and assign the appropriate access rights to that Group.Add the users which all are suppose to be in that group.

    Now, if a user leaves or moves on to something else, as the other user falls in that user group will have the same access rights and will be able to do his/her activities.Also you can add up new user directly to the group.

    A simple way describing it :Training: Managing Users, Groups and Folders - BusinessObjects XI

    Regards,

    Javed

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi ,

      As per SAP BO User Mgmt Guide:

      Owner rights

      Owner rights are rights that apply only to the owner of the object on which

      rights are being checked. In the SAP BusinessObjects User Management

      System, the owner of an object is the principal who created the object; if that

      principal is ever deleted from the system, ownership reverts to the

      Administrator.

      Owner rights work similarly to their corresponding regular rights and are

      useful for managing owner-based security. However, owner rights are

      effective only when the principal has been granted owner rights but regular

      rights are denied or not specified.

      http://help.sap.com/businessobject/product_guides/boUMS01/en/FPM75_UMS_admin_en.pdf

      Check the topic :To create an FPM administrator

      in the pdf to get how to handle this type of scenario.

      Regards,

      Javed

  • author's profile photo Former Member
    Former Member
    Posted on Feb 08, 2014 at 08:41 AM

    Hi,

    I would do the below :

    1. Keep the content into a separate folder.

    2. Assign the EDIT RIGHTS ( Not the OWNER rights)

    3. Restrict the VIEW rights on that folder for the group which user belongs to.

    So if users moves out of the organization and any other user joins and the edit rights are still the same.

    Hope it helps.

    Regards,

    Upendra.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      Exactly that is correct. Carry on keeping the objects in one folder and assign the rights.

      The best practise is to ensure the rights on the public folders is given to a specific user group instead of user group.

      For example --> User A belongs to Group 1.

      User B belongs to Group 2.

      Assuming Folder Structure like this :

      Root Folder --> Folder A
      --> Folder B

      Apply global edit rights for Group 1 and Group 2 on Root folder and assign View Objects applied at OBJECTS LEVEL only at the root folder.

      Now on Folder A --> Apply View Objects at Object and Sub-object level for Group 1. Here view rights are restricted to only GROUP 1 users.

      Folder B --> Apply View Objects at Object and Sub-object level for Group 1. Here view rights are restricted to only Group 2 users.

      If the users in Group 1 are moved away from company, just move the Folder A as sub folder to Folder B. The rights can be assigned this way.

      Now to change the ownership of the report you would need to copy and paste into your personal folder, which automatically makes you as owner of that report.

      One suggestion is to keep the security model as simple as possible.

      Regards,

      Upendra.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.