# Known limitations

None of these are faults. They are limits and deliberate design decisions, listed plainly so you can plan around them rather than discover them halfway through a rollout.

---

## Caps and sizes

| **Thing**                               | **Limit**                                              |
| --------------------------------------- | ------------------------------------------------------ |
| Members listed in a team                | 32                                                     |
| Reviewers taken from a Confluence group | **30**, chosen by display name from the first 150 read |
| Members of the built-in space team      | 16                                                     |
| Watchers per space                      | 50                                                     |
| Label routing rules per space           | 50                                                     |
| Characters in a response comment        | 500                                                    |
| Team name length                        | 3 to 75 characters                                     |

A group with more than 30 usable members is cut to the first 30, and the team editor warns you when it notices. App and service accounts are never included. See [Manage approval teams](https://help.gocapable.com/approval/manage-approval-teams.html).

---

## Content types

| **Type**       | **Support** | **Behaviour**                                                                                                   |
| -------------- | ----------- | --------------------------------------------------------------------------------------------------------------- |
| **Pages**      | FULL        | Everything works.                                                                                               |
| **Blog posts** | PARTIAL     | You can approve and respond, but editing does **not** reset the approval, and automatic approvals do not apply. |
| **Live Docs**  | PARTIAL     | The panel works, but Live Docs change without creating versions, so version and integrity checks are skipped.   |
| **Drafts**     | NONE        | Approvals attach to published versions. An unpublished draft has no approval of its own.                        |

---

## Page lifecycle

| **You do this**          | **The approval**                      |
| ------------------------ | ------------------------------------- |
| Move a page              | Comes with it.                        |
| Copy a page              | Is not copied. The copy starts clean. |
| Archive or delete a page | Goes with the page.                   |

---

## Timing

* Expiry is processed **once an hour** in batches, so nothing happens exactly on the minute. See [Expiry and re-approval](https://help.gocapable.com/approval/expiry-and-re-approval.html).
* Relative expiry, such as six months, only starts once an approval has been decided. A pending approval only ever expires on an **exact date**.
* There is a roughly **two minute** settling window after a page edit, during which the status shows In review.
* Search and reporting read an index that lags the page by a moment. See [Search and reporting](https://help.gocapable.com/approval/search-and-reporting.html).

---

## Things that are deliberately not available

* **Live updates between people.** Two people looking at the same approval do not see each other responses appear. Reload.
* **A Confluence Automation action.** Automatic approvals come from space settings, not from the Confluence automation engine. See [Automatic approvals](https://help.gocapable.com/approval/automatic-approvals.html).
* **A public write API.** Approval state can be read through Confluence content properties. There is no supported endpoint for creating or answering approvals. See [Rovo and AI assistants](https://help.gocapable.com/approval/rovo-and-ai-assistants.html).
* **Any Jira surface.** Approval is Confluence only.
* **Per-person Slack opt-out.** Email can be turned off individually, Slack is site-wide. See [Notifications](https://help.gocapable.com/approval/notifications.html).
* **Approving on somebody else behalf.** Not available to administrators, and not available to AI assistants.

---

## Things worth knowing before an audit

* Administrative changes, such as turning the code requirement on or off and resetting an authenticator, are **not** in the approval history.
* The CSV export does not mark which responses were signed with a code.
* An approver can change their answer after completion, which recalculates the status. Both answers stay in the history.
* Withdrawing an approval notifies nobody.
* There are no backup codes for authenticators.

All of these are unpacked properly in [Compliance](https://help.gocapable.com/approval/compliance.html) and [What is recorded](https://help.gocapable.com/approval/what-is-recorded.html).

---

## Migrating from another app

Approvals can be migrated from **Approvals for Confluence** by AppFox. Other approval products are not currently covered. Talk to us about what you are moving from.

---

## Related

[Common questionsWhen something actually looks wrong.](https://help.gocapable.com/approval/common-questions.html)

[ComplianceWhere these limits matter for a standard.](https://help.gocapable.com/approval/compliance.html)

[What is recordedWhat the audit trail does and does not hold.](https://help.gocapable.com/approval/what-is-recorded.html)

[Manage approval teamsThe team caps in context.](https://help.gocapable.com/approval/manage-approval-teams.html)

[Expiry and re-approvalWhy timing is hourly, not instant.](https://help.gocapable.com/approval/expiry-and-re-approval.html)

[Automatic approvalsWhat automation covers, and what it does not.](https://help.gocapable.com/approval/automatic-approvals.html)

---

_No surprises left. That is the whole list._