Tines Academy › Lesson
Get it ready to go live
Work through ownership, team access, and final checks to decide whether the tracker is ready for everyday use.
Objective: Use the five readiness questions to decide whether a workflow is ready to go live.
Get ready for everyday use
Sue’s tracker is taking shape, but there’s more to do before her team relies on it. She needs to choose who’ll look after it, add the real reviewers and notification channel, and ask colleagues to try it.
So far, you’ve built and tested on a draft, keeping your test requests separate from live data. After going live, you can make changes on a new draft and use approved examples to test them.
You don’t need to push the tracker live to complete this path. If you’re building it to learn, read through the preparation steps and readiness questions, and note what you’d need before a team could use it.
Decide who looks after the tracker
Choose an owner and a backup who can investigate problems and update the workflow. The owner doesn’t have to be the person who built it. Make sure both people have the access they need, and agree how often they’ll check for requests and notifications that need attention.
For team use, check that the tracker is in the right shared space. You may already have moved it there to use the chat connector. Check who can access its saved requests and that the connector is available in that space. Move the workflow if it needs a different home.
You’ll record the owner and backup in Readme later in this lesson. These may not be the people who built the tracker, so make it clear who colleagues should contact.
Get the tracker ready
For team use, confirm that the tracker is in the chosen shared space and that its connector is available there. Move it only if needed. For practice, keep it in its current space.
Send this prompt in workflow chat, saying whether you’re building for practice or team use.
Review this tracker's readiness for team use. Keep the pages and any routes supplying their data restricted to Space access. Leave the workflow as a draft.
Ask whether this is a practice build or intended for team use if I haven't said.
For team use, ask for the real operations reviewers, each requester's manager, and the operations notification channel. Confirm the destination before sending anything. Ask who owns the tracker and who's the backup.
For practice, leave unassigned roles and missing setup marked as "Not yet agreed". Don't require me to arrange colleagues or connect a chat service to continue. If I'm using previews, keep them labeled "Preview only" and don't send anything.
Update Readme with how the tracker works, the agreed contacts and settings, and any failed or unfinished checks. Don't mark a check as passed without a supporting result.
Check how requests and reviewer settings are stored. Explain how to leave made-up requests out of live while keeping the real reviewer and manager settings. Don't delete data or push live.
Check how test identities and simulated failures are blocked on live, not just hidden from the page. Report what you verified and what still needs checking.
Check the tracker
Read the summary in workflow chat, then open Readme. Check that the contacts, settings, and unfinished checks match what you agreed.
For practice, record any checks you can’t complete and continue. You don’t need to recruit colleagues to complete this lesson. Before team use, complete the account and delivery checks below.
Try the requester and reviewer accounts
Ask one colleague to submit a made-up request and another, set up as an operations reviewer, to review it.
They should use their own non-admin accounts, not the test switch.
Check that:
The requester can see their own request but not someone else’s.
The reviewer can review another person’s request.
The reviewer can’t approve a request they submitted themselves.
Ask Tines 3B to help check direct requests too. Hiding buttons or removing requests from a list isn’t enough.
Try the manager account
Submit a made-up request for $5,000 using a new vendor website.
Have the assigned manager open it using their own account. Check that it waits for their decision before operations can approve it.
Also check that another manager can’t open or decide on a request that isn’t assigned to them.
Check the notification
Confirm that you’re allowed to send a test message to the operations channel.
Send one clearly labeled test message and check that it arrives in the agreed channel with the expected details.
If you’re using previews, leave delivery marked as unverified.
Run the saved tests
Open Monitor and run the saved tests from Tests.
Check that they pass on this version. If one fails, open its step and ask Tines 3B to explain the difference.
If something doesn’t match
Tell Tines 3B which account or request you used, what you expected, and what happened. Ask for a focused fix, then repeat the affected check.
Ask it to record unfinished checks in Readme. Don’t make a page public or widen access just to complete a test.
Remember to check who can access the workflow in the shared space. Everyone with that access can also look through its saved requests, even if the tracker’s pages show them a restricted view.
If some people shouldn’t see all the requests, keep using made-up data and leave the tracker as a draft. Ask whoever manages access in your organization how to let them use the tracker’s pages without giving them access to the workflow itself.
Five go-live readiness questions
Push live
Publishing is optional. If you’re practicing or have important checks left to finish, keep the draft and continue to the next lesson.
Review readiness
Review the five readiness questions and unfinished checks in Readme. Follow your organization’s review and approval process.
Publish the draft
Select Push live in the branch selector.
If asked about storage, follow the plan you agreed with Tines 3B. Leave out made-up requests while keeping the real reviewer and manager settings.
If publishing is blocked, read the reason and ask someone with the required access for help.
Check the live tracker
Open the live page from Links.
Use clearly labeled, made-up test requests to check that:
Requests below $5,000 reach operations.
Requests of $5,000 or more reach the assigned manager first.
Notifications reach the agreed channel.
The real reviewer and manager settings are still in place.
Use a different vendor website for each spend test.
Check access on live
Repeat the requester, reviewer, and manager checks using their own accounts on the live page. There should be no test switch.
Finish these checks before inviting the team to submit real requests.
If something doesn’t match
If someone can see requests or make decisions they shouldn’t, restrict access until it’s fixed.
Ask Tines 3B to investigate and fix the problem on a draft. After publishing the fix, repeat the affected live checks.
One last question about your own workflow. At the end of the path, we’ll bring your answers together in a brief you can review and give Tines 3B to start building.
What to do if something still feels fuzzy
You worked through what the tracker needs before a team can rely on it. If you published it, finish the live checks before your team starts submitting real requests. If you’re keeping it as a learning exercise, leave it as a draft and keep your notes on what still needs testing or setting up. Next, you’ll follow Sue through her first month live.
Build it safely: You learned why a live workflow needs an owner and a backup, and what they need to look after.