# [Story or feature name]: acceptance criteria

**Owner:** [name] · **Status:** Draft · **Last updated:** [date]
**Story:** [link]

> Free acceptance criteria template from SprintProof: https://sprintproof.com/templates/acceptance-criteria-template
> Replace everything in [brackets]. Delete the guidance lines (starting with ">") when you are done.

## 1. Which format to use

> Given / When / Then for flows with a starting state and a result. A rule checklist for facts that are always true: limits, permissions, formats. Mix them.

## 2. Happy path

> The main flow, one scenario per path, one When per scenario.

**Scenario:** [name]
- **Given** [starting state]
- **When** [one action]
- **Then** [what the user sees and what is saved]

## 3. Edge cases and errors

> Expired, used, duplicate or wrong input; wrong account or workspace. Name the exact message or error code.

**Scenario:** [name]
- **Given** [state]
- **When** [action]
- **Then** [exact result, message or error code]

## 4. States: empty, loading, error

> What each screen shows before, during and after the data arrives, and when it fails.

- **Empty:** [what it says, what the user can do]
- **Loading:** [what shows]
- **Error:** [what shows, and whether the user can retry]

## 5. Permissions

> Who may do the action, what everyone else sees, and whether the API enforces the same rule.

- [ ] [Role] may [action]
- [ ] [Role] cannot [action]: they see [hidden / disabled / error]
- [ ] The API enforces the same rule as the interface

## 6. Limits

> The number, per what, what happens at the limit and when it resets. State the first request over the limit.

- [ ] At most [number] [things] per [who] per [period]. The next one returns [result].
- [ ] [Expiry]: [what happens after it]

## 7. Non-functional

> Only what you can measure: screen width, screen reader, time, logging, compatibility.

- [ ] Works at [width] px and with a screen reader
- [ ] [Step] completes in under [time]
- [ ] [Event] is logged with [fields]
