Sign inDeploy now
Deploy now

SpringRoll reference

AI-built app handoff checklist for IT teams

By Updated

Start with one useful app. Use SpringRoll to record its owner, choose the release workflow and give the right people a launch link.

Deploy your first appTalk to the team
Product workflowInstall, authorize, deploy, verify
  1. 01 · SetupInstall the skill

    Use the setup command in Docs with your coding agent.

  2. 02 · WorkspaceAuthorize the first live call

    Sign in and choose the workspace. There is no token to paste.

  3. 03 · PublishAsk the agent to deploy

    SpringRoll records the app and release, then starts the deployment.

  4. 04 · Verify and shareCheck the build result

    After READY, open the app and share the intended environment link.

A deployment result is the handoff record. Opening the app checks that the result actually works.

1. Name the owner and the outcome

Record an accountable App Owner, department and support contact. Write down the task the app solves and the person who will verify it. Keep a current source bundle or repository so the next change is repeatable.

2. Choose the release workflow

Use Direct to Production for the direct release path, or configure Staged for Development, UAT and Production review. Record which environment is being tested, the release ID and the build result. Run the app's main task after READY.

3. Verify the launch handoff

Choose the audience in Access, then copy the SpringRoll app link. Use separate test accounts to verify the intended experience.

  • Intended colleague: sees the app in the portal and launches the selected environment.
  • Unapproved colleague: cannot launch that environment; the app offers the appropriate access-request path.
  • Direct provider URL: verify application or provider authentication independently. Portal launch rules control the SpringRoll path, so record the result for the origin URL too.
  • Save the release, environment, test identities, expected result and observed result in the handoff. Never include credentials.

4. Connect only the data the task needs

A data-product gateway grant controls selected fields and query rules. A native connector grant authorizes selected APIs and follows the source account's permissions. Choose the route for the app, review its environment-specific grant and verify the result with sample data first.

5. Give colleagues a useful starting point

Publish the app's description and owner, share its SpringRoll link and show the team one complete task. Our team helps with deployment, data connections and the launch handoff.

6. Plan for the builder's departure

An app can outlive the employee who first built it. Identify the replacement owner before an absence or role change, review the source and deployment records together, and make sure support contact details point to someone who remains accountable. Transfer ownership through the governed workflow rather than sharing the builder's login.

Review launch audiences, application identities and environment-specific data grants when responsibilities change. A colleague's personal access to a source system is not an application grant. Verify the running app after the transfer, record the next maintenance task and give the incoming owner a way to suspend the app if its purpose or data access is no longer appropriate.

Deploy your first app