Allowing Users to see documents they 'Author' not 'Upload'

Another interesting query for you to get your virtual teeth into.

When I provide a group access to a file folder – the HighQ group folder permissions dictate I can provide three views: All, None or Own.

  • If I select ‘ALL’ I can see all the documents in the folder. Obvs.
  • If I select ‘None’… You can guess.
  • And if I Select ‘Own’… I should be able to see the logged in users documents…Right? wellll..... not quite. 

Here is where I have my issue.

Clicking ‘Own’ in folder permissions, does NOT allow me to view documents where my user is an Author. It only allows me to view documents where the user originally uploaded the document. This is a challenge because ALL the documents in my folder were created by Rules. Therefore the ‘uploader/owner’ for ALL the documents is HighQ ‘Document Automation’ user and not the actual user.

If a user ‘modifies’ a document by changing some content, then the ‘Author’ of the document changes to the actual user name. Great!!! However – even with my user being the ‘Author’ the document - it still does not show up in a folder view when ‘Own’ rights to the folder have been assigned.

Is there any way to..:

  • Change the ‘Owner’ of a document created by a Rule Builder Workflow, so the document is no longer ‘Document Automation’ and is instead the creating user? Could this also be done by using an API call?
  • Change the default view of a folder so that the user can see’s documents they are the ‘author’ as well as the ‘owner/uploader’ of? This needs to be a default view – not something they have to set manually. We don’t want all users seeing all other documents in the same folder.

Any assistance would be gratefully received.

Thanks

Tony.

Parents
  • Apprecate the response, but sadly this does not really help. 

    While I can change the view, the Owner/Creator is always the 'Document Automation' user, not the 'ACTUAL' userID of the user. 

    I've tried filtering on my own field 'Created By' but this will not accept 'ME' (the current logged in user) as a valid option. I could create a view for the 'actual' user, so If I had 100 users, I'd need 100 separate views, one for each user, and I'd need to assign them permissions as well, not exactly workable sadly. 

    Thanks for the assist anyway. 

    Tony. 

  • 0
    Thomson Reuters Thomson Reuters staff member
    in reply to tgent

    Hi,

    Unfortunately, this is a limitation we have in HighQ. You can submit your requirement to the support team as an enhancement request.

    Thanks!

  • Reply
    • 0
      Thomson Reuters Thomson Reuters staff member
      in reply to tgent

      Hi,

      Unfortunately, this is a limitation we have in HighQ. You can submit your requirement to the support team as an enhancement request.

      Thanks!

    Children
    No Data