Short Description Approver eligibility is governed at the team level. This article explains the Can Approve for Team rule and how to manage approver assignments.
What this article answers
- Which team members are eligible to approve.
- The minimum number of approvers required per team.
- How to change who can approve.
The short answer
Any member of a team whose membership has Can Approve for Team = Yes is eligible to approve that team's tactics. Members with Can Approve for Team = No cannot approve, even if they're otherwise admins.
The rules in detail
- Approval eligibility is set per team membership, not per user globally.
- A user on two teams may be an eligible approver on one and not the other.
- Each team must have at least one member marked Can Approve for Team = Yes. Hive9 enforces this — you can't reduce the team's approvers to zero.
- When approval workflows are enabled on your instance, only users with Can Approve = Yes appear in the workflow's eligible-approver list.
How to change a user's approval permission
- Go to Settings → Teams and open the team.
- Find the user's row in the team membership list.
- Toggle Can Approve for Team to Yes or No.
- Save.
[SCREENSHOT NEEDED — Team membership grid with Can Approve toggle]
The change takes effect immediately for new approval workflows. In-flight approvals continue with the approver list captured at the time the tactic was submitted.
How this interacts with workflow approver types
Approval workflows can specify approvers in several ways:
- User — a named individual.
- Role — anyone with a specified role.
- Record Owner — the user who owns the object.
- Custom Attribute — a user referenced via a tactic attribute.
In every case, the resolved approver must also have Can Approve = Yes on the relevant team. The workflow's approver specification narrows the eligible pool; the team-level toggle is the underlying eligibility gate.
Common questions
Can a Client Admin approve any team's tactics? A Client Admin's role grants broad access, but they still need Can Approve = Yes on the specific team to be picked up by that team's approval workflows.
What if my only approver leaves the company? Add another team member with Can Approve = Yes before deleting the departing user, so the team always has an active approver.
Can I require multiple approvers in sequence? Yes — that's what Advanced Approval Workflows are for. They support serial and parallel approval chains across multiple users or roles.
Comments
Please sign in to leave a comment.