nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Anyone can Approve/reject a workflow?

tik

I am trying to followup on an earlier post by one of a member here.

Ts 7.2.1 on solaris

Using modeler. When trying to assign a review task to a reviewer, I expect that only he can Approve or Reject. But what I find out that almost any teamsite user can.
I understand from earlier posts as this being a bug. Is there a fix?
If there is no fix, is there a criteria on who can approve/reject or is it a role of at least "admin"?

Thanks
Rahul

Find more posts tagged with

Comments

Adam Stoller

I am trying to followup on an earlier post by one of a member here.

Ts 7.2.1 on solaris

Using modeler. When trying to assign a review task to a reviewer, I expect that only he can Approve or Reject. But what I find out that almost any teamsite user can.
I understand from earlier posts as this being a bug. Is there a fix?
If there is no fix, is there a criteria on who can approve/reject or is it a role of at least "admin"?

Thanks
Rahul

I believe the answer is:

If you're finding that someone else - who is neither the task owner, job owner, or a Master user - has the ability to approve / reject the task, please provide details.

tik

Yes

I see that even Admin users can Approve/Reject a wf

Should I be expecting this?
If not, I can post & provide details.

thanks
Rahul

Adam Stoller

Yes

I see that even Admin users can Approve/Reject a wf

Should I be expecting this?
If not, I can post & provide details.

thanks
Rahul

Quite possibly that's considered part of their default set of rights (some of which you could potentially alter by either customizing the OOTB roles [bad] or creating copies of the OOTB roles, customizing them, and using them instead of the OOTB roles [good])

tik

thanks Fish