> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mibyanai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Approvals and roles

> Separate tender preparation, review, and authorization for Go decisions, pricing, proposals, and submission

Tender separates preparing work from reviewing and authorizing it. Requests appear in the **Approval inbox** with their type, related opportunity, requester, and current status.

## Approval types

| Approval                        | When it is used                                                     | Typical reviewer               |
| ------------------------------- | ------------------------------------------------------------------- | ------------------------------ |
| Go / No-Go                      | Before significant bid effort or when a blocker or exception exists | Bid lead or executive approver |
| Pricing or financial commitment | Before confirming price, guarantee, or financial exposure           | Finance approver or owner      |
| Proposal approval               | After technical, commercial, and compliance review                  | Reviewers and bid lead         |
| Submission approval             | Before any external upload, email, or handover                      | Owner or executive approver    |

## Available roles

| Role                | Main capabilities                                            |
| ------------------- | ------------------------------------------------------------ |
| Owner               | Manage, write, review, and approve Go, price, and submission |
| Admin               | Manage, write, review, and approve Go                        |
| Bid manager         | Write, review, and approve Go                                |
| Technical reviewer  | Review technical content                                     |
| Commercial reviewer | Review commercial content                                    |
| Legal reviewer      | Review legal content                                         |
| Finance approver    | Review and approve pricing                                   |
| Executive approver  | Review and approve Go and submission                         |
| Contributor         | Write without approval authority                             |
| Viewer              | Read and monitor only                                        |

<Note>
  Roles define what the system permits. Your internal policy may require additional approvals or financial thresholds. Document those rules in the company profile and do not rely on a role name alone.
</Note>

## Process an approval request

<Steps>
  <Step title="Open Approvals">
    Use the pending count in the Tender navigation to find open requests.
  </Step>

  <Step title="Open the opportunity and version">
    Confirm that the request points to the intended proposal, price, or package—not an older revision.
  </Step>

  <Step title="Review evidence and risk">
    Check uncovered requirements, open comments, exceptions, and deadlines.
  </Step>

  <Step title="Approve or reject with a reason">
    When rejecting, state what must change and who owns the correction.
  </Step>

  <Step title="Verify the next workflow state">
    Return to the opportunity and confirm that the expected next action is available and no unintended external action occurred.
  </Step>
</Steps>

## Recommended segregation of duties

```mermaid theme={null}
flowchart LR
  BM["Bid manager\nprepares and requests"] --> TR["Technical or legal reviewer\nreviews"]
  TR --> FA["Finance\napproves price"]
  FA --> EA["Executive approver\napproves submission"]
```

Small teams may assign more than one role to the same person, but retain a second review before pricing or submission whenever possible.

<Warning>
  Approval in Tender does not by itself grant legal authority outside the system. The approver must be authorized under your company's formal delegation policy.
</Warning>

<Card title="Next: submission package" icon="box-archive" horizontal href="/tender/submission">
  Freeze the package, run the sandbox check, and understand external-submission boundaries.
</Card>