A grant cannot be queued to start when the current one ends #117

New Issue

2026-09-21T07:18:35Z

cgalo5758 commented

2026-09-21 07:18:35 +00:00

What a person cannot do today

Queue a grant behind the one an organization already holds. An operator can end a grant on a date, after which the organization falls back to its type's default, but cannot say what it should hold instead. Moving an organization from the plan it is trying down to the plan it is buying, when the trial ends, is two acts, and the second one lives in somebody's memory.

What they should be able to do

Issue a grant with a start in the future, see it on the organization's page as queued behind the live one, and have it take effect on its own when the day comes.

Why it matters

Every arrangement with an end has a next step, and without a queue the next step is a reminder rather than a record. An organization whose grant lapses silently drops to its type's default, which is rarely what was agreed.

Where

The grants ledger already carries a start time, written when a grant is conferred, so the schema may need nothing. internal/server/operator_enrollment.go, the Issue grant form; the conferral, which must not deliver a grant that has not started; and a scheduled activation alongside the sweep that expires grants.

Done when

Issue grant takes a start, a grant that has not started is visible and revocable but delivers nothing, a scheduled run activates it and records the transition, and both the organization page and the grants list show a queued grant as queued.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Queue a grant behind the one an organization already holds. An operator can end a grant on a date, after which the organization falls back to its type's default, but cannot say what it should hold instead. Moving an organization from the plan it is trying down to the plan it is buying, when the trial ends, is two acts, and the second one lives in somebody's memory. ## What they should be able to do Issue a grant with a start in the future, see it on the organization's page as queued behind the live one, and have it take effect on its own when the day comes. ## Why it matters Every arrangement with an end has a next step, and without a queue the next step is a reminder rather than a record. An organization whose grant lapses silently drops to its type's default, which is rarely what was agreed. ## Where The grants ledger already carries a start time, written when a grant is conferred, so the schema may need nothing. [`internal/server/operator_enrollment.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/operator_enrollment.go), the Issue grant form; the conferral, which must not deliver a grant that has not started; and a scheduled activation alongside the sweep that expires grants. ## Done when Issue grant takes a start, a grant that has not started is visible and revocable but delivers nothing, a scheduled run activates it and records the transition, and both the organization page and the grants list show a queued grant as queued. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

enhancement

area/entitlements area/operator-ui labels 2026-09-21 07:18:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#117