Approval Policies
Set up who approves intake gates, governance gates, timesheets and funding requests, so submitters never have to pick an approver themselves.
An approval policy decides who must approve a request. When someone submits, Completix reads the policy, finds the matching approvers and sends the request to them automatically. You set policies once, and every request of that kind follows them.
On this page
Where to find approval policies Policy types Intake policies, gate by gate Default Approvers and rules Submission policy Site and LOB policies What approvers getEach policy has two parts. Default Approvers handle any request that does not match a rule. Rules send specific requests, such as a high score or a large budget, to different approvers. A policy only routes requests while it is Active.
Submitters do not choose approvers. They submit, and the policy does the routing.
Where to find approval policies
Approval policies are in the settings, under Approval Policies.
- With Global View selected, the settings show Global Settings and the site-wide policies.
- With a Line of Business (LOB) selected, the settings show that LOB's own policies.
- If you manage more than one LOB, use the drop-down beside the settings name to switch between LOBs without changing the LOB switcher.
You need the right site or LOB permission to see and change approval policies.
Policy types
Each kind of request has its own policy. Click a policy to expand it.
- Project intake. Routes each gate of an intake request to its approvers, with one versioned policy per intake template. See the next section.
- Governance Approval. Routes governance gate approvals on projects.
- Timesheet Approval. Routes submitted timesheets.
- Funding Approval. Routes funding requests from projects and intake requests to the LOB funding they draw from. Money is only committed or reserved once the request is approved.
Intake policies, gate by gate
You do not create intake policies yourself. When you create an intake template, Completix creates a matching policy with the same name, and every gate you add to the template appears in that policy. Expand Project intake to see one entry per template, showing how many gates and versions it has. Open template takes you to the template itself.
Expand a template to set up its approvals:
- Version. The box at the top shows the version you are looking at and its date. Current marks the version new requests use. Use the arrows beside it to switch versions.
- Request created and the gates. The steps follow the template. Select a gate to see and change its approvers. Each gate shows how many rules it has, so every gate can go to different people.
- Default Approvers, rules and the Submission policy for the selected gate appear on the right.
When you publish a new version of an intake template, the policy gets a new version too. Requests already submitted keep following the version they started with. Only new requests use the current version.
Default Approvers and rules
Default Approvers receive every request that does not match a rule. The number beside it shows how many approvers are set.
To send some requests to other approvers, add a rule:
- Click Add rule.
- Under Conditions, pick a field, then an operator and a value. For example, Scorecard, Total Score, Greater than 70.
- Click Add condition to add more conditions to the same rule.
- Under Approval required from, add Members, Groups, or both.
Click a rule to collapse or expand it, and use Delete rule to remove it. The fields you can use in conditions depend on the policy. Intake policies can use the template's shared fields, and Intake, Governance and Timesheet policies can use the LOB.
Groups are set up in Site Admin. Using a group instead of named members means you only update the group when people change roles, not every policy.
Approvers do not have to belong to the LOB the policy is for.
Submission policy
Below the rules, each step of an intake policy has a Submission policy. Use Add action to set a field automatically when the gate is approved or rejected, for example moving a status field from one value to the next.
- Actions can set fixed fields or shared fields.
- A field set by a submission policy is read only in the intake form, so the value always comes from the approval.
- Shared fields can change from gate to gate, which makes them useful for grouping and filtering in the intake list.
Site and LOB policies
The site-wide policies in Global Settings do two jobs:
- When lines of business are turned off, they apply to every request.
- When you create a new LOB, they are the starting point for that LOB's policies.
Each LOB can then change its own policies. If an LOB does not have a policy set up, the site policy applies. If neither is set up, the policy is not configured.
What approvers get
- Automatic access. Anyone named in a policy gets the permission they need to preview and approve the request. You do not need to give them a separate role.
- The reason they were picked. The approvers list on a request shows which rule added each approver.
- A place to comment. Approvers can approve, reject or ask for more information, and add a comment so the submitter knows what is needed.