Welcome, Guest
Username: Password: Remember me

TOPIC: How to restrict a Resource in a request.

How to restrict a Resource in a request. #1483

  • wendy
  • wendy's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
  • Karma: 0
Hello Everyone, and Happy New Year to all!

We are trying to put security on a couple workflows to restrict who can see them. Does anyone know how the "Checked Task" workflow, is set up security wise, for a "New User Account Created"(created by HRBGJOBS)?

When a new user is created, a workflow is auto sent to the Manager of the Resource, with the new user password. We have done some testing and see that ONLY the Manager of the Resource can see this workflow.No one can see these workflows, even with "Administrative Rights".

We want to basically duplicate this in another workflow, but are uncertain of how this security is applied.

Thanks,

Wendy
The administrator has disabled public write access.

How to restrict a Resource in a request. #1484

  • SLeete
  • SLeete's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 54
  • Karma: 0
Hi Wendy,

Thanks for the question. Document number 15.567.559 gives a good breakdown of the differenct security levels used in workflow. I would recommend set the workflow to 99. This allows visibility only to the Creator
and the current workflow actor of the Request .
Scott Leete
Presales, Principal


Exact Software North America LLC

T +1 407 602 6088
F +1 866 544 5456
scott.leete@exact.com
http://www.exact.com
The administrator has disabled public write access.

How to restrict a Resource in a request. #1486

  • wendy
  • wendy's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
  • Karma: 0
Hi Scott,

Thank you so much for the quick response!

Wow that just seems too simple, I think we may have been over thinking it to some degree. We are going to give this a try.

Wendy
The administrator has disabled public write access.
Time to create page: 0.035 seconds
Powered by Kunena Forum  Protected by R Antispam