Advancing and retiring an app

An app moves forward one phase at a time, and a wider group can reach it at each step.

Phase	Who can reach it
Interview	The Builder
Internship	A hand-picked cohort, plus the Builder and manage_apps holders
Apprenticeship	A wider cohort, plus the same people
Full-time	Everyone in the company, or the Teams you choose
Sunset	Nobody; the app is retired

Who may advance or retire an app#

You can advance or retire an app if you are its Builder or hold the manage_apps ability. The buttons appear in the Lifecycle card of the details page. Nobody sees them once the app is retired.

Advance to the next phase#

1. In the Lifecycle card, select the button for the app's current phase:
   • Open to internship from Interview
   • Promote to apprenticeship from Internship
   • Graduate to Full-time from Apprenticeship
2. A dialog opens titled "Move [name] to [phase]?", for example "Move MyApp to Internship?" Write a Sign-off statement, such as "Used daily by the pilot cohort with no blocking issues." It is required.
3. When you are moving to Internship or Apprenticeship, choose the Cohort. Filter the list with Filter by name, title... and tick the people who should be able to use the app. At least one person is required; the dialog shows how many are selected. When advancing from Internship, the current cohort starts selected, and you can widen it.
4. When you are moving to Full-time, the dialog has an optional Team access section. Choose Teams from the list to limit the app to them, or leave it blank for everyone in the company.
5. Select Move to followed by the new phase, for example Move to Internship.

The sign-off statement is stored with the move in the app's lifecycle record. A phase cannot be skipped.

Promotion requirements#

Your administrator decides what must happen before each move: nothing, an approval, or a measure the platform checks. When something is required, the dialog opens with a Promotion requirements section above the sign-off.

• Adoption is the measure for apps: the share of the group being left that opened the app in recent days (30 by default). It is shown as Met, Not met or Not enough data, with what it needs, for example "needs 50%". The Move to button is unavailable until it is met. Moving from Interview to Internship has no measure.
• When approval is required, the button reads Request approval. Your sign-off and cohort go to the admins and executives who approve, and the app stays in its phase until one of them approves. Nobody advances it directly. The Lifecycle card shows no advance button while a request is waiting.

While a request is waiting, the details page shows a banner, Promotion to the new phase · awaiting approval, with a Withdraw request button for the person who asked. If an approver declines it, a banner shows their note and the app stays where it is. Approvers use Approve to the new phase or Decline on the banner; the reason is required. An admin can approve their own request; an executive who is not an admin cannot. Pending requests also appear in a Promotion requests · awaiting approval section on the directory.

Retire (sunset) an app#

1. Select Retire in the Lifecycle card.
2. In the Retire [name]? dialog, enter a Reason.
3. Type the app's name exactly in the field labeled "Type" followed by the name "to confirm".
4. Select Retire.

A retired app stops running and can no longer be reached by anyone. It stays in the directory as a record, shown when Show retired Apps is turned on, and its lifecycle history is kept. Its code repository stays on the details page. This cannot be undone.