Tines Academy › Lesson

Control access and go live

Decide who should see the dashboard, check its numbers against the source, and work through what it needs before a team can rely on it.

Objective: Choose appropriate access for a dashboard, trace a result back to its source, and assess whether it’s ready for team use.

Decide who can open it

Maya’s dashboard can include customer comments and ticket links, so access should stay with her support team. Space access, the default, suits this setup when everyone who can access the space should also be able to see the dashboard’s data.

You don’t have to push the dashboard live to finish this learning path. If you’re building it just to learn, keep it as a draft in the space you’ve been using, work through the readiness questions, and note anything you can’t check yet. You don’t need to move it or involve colleagues just to finish the lesson. If you want your team to use it, complete the team access and data checks before pushing live.

Common settings for who can open a page

Tenant admins have broader access, so don’t use an admin account to test whether someone without space access is blocked.

Decide what each audience can see

A page’s access setting controls who can open it; it doesn’t automatically give different people different views. For example, colleagues outside support might need a separate summary page without customer comments or ticket links. Those details should be left out of the data the page receives, not just hidden on screen.

You don’t need to build a separate page in this lesson, but keep the difference in mind: a person who can inspect the page’s data can see anything it loads, regardless of what’s visible.

If someone can’t sign in, find out why. Don’t widen the page’s access just to get around the problem.

Decide who looks after the dashboard

Choose an owner and a backup who can investigate failed updates and change the workflow. Make sure both have the access they need, know who looks after the ticket system connector, and agree how often they’ll check that the data is current.

For team use, check that the dashboard is in the right shared space. You may already have built there to use the ticket system connector. Check that the space’s members are allowed to see the dashboard and its saved data, and that the connector is available there. Move the workflow only if it needs a different home.

You’ll record the owner, backup, and connector contact in Readme later in this lesson. The person who builds the dashboard may not maintain it, so colleagues need to know who to contact.

Trace one number

Before people use a number in a meeting, make sure you can explain where it came from.

Choose the number

In Browser, note the negative-rating count for the last full week and any selected product area or channel filters.

Find the responses behind it

Send this in workflow chat, filling in your filters:

Show the prepared responses behind the negative-rating count for the last full week, using these filters: [filters]. Show the dates and counting rule used.

Compare with the originals

Open two or three matching tickets or survey responses. Check the rating, rating date, product area, and channel against the dashboard.

With test data, compare with the saved original responses instead.

If something doesn’t match

Show Tines 3B the number and example that disagree. Ask it to investigate, then repeat the check after a correction.

Keep the dashboard as a draft until you understand the difference.

Get the dashboard ready

For team use, confirm that the dashboard is in the shared space you chose and that its connector is available there. Move it only if needed. For practice, keep it in its current space.

Choose the tab that matches your setup, then send the prompt in workflow chat.

Review this dashboard's readiness for team use. Keep it as a draft. Keep the page and any routes supplying its data restricted to Space access. Ask whether this is a practice build or intended for team use. For practice, record unassigned roles as "Not yet agreed" without requiring me to arrange them now.

Update the Readme with how the dashboard works, where its data comes from, and what remains untested. Ask who owns the dashboard, who’s the backup, and who looks after the ticket system connector, and record those contacts.

Check that the test switch will be hidden on live and that simulated failures can't be triggered there, even without the switch. Report what you checked and what remains unverified. Don't push live.

Review this test-data dashboard and explain what remains before a team could use it with real data. Keep it as a draft, with the page and any routes supplying its data restricted to Space access. Ask whether this is a practice build or intended for team use. For practice, record unassigned roles as "Not yet agreed" without requiring me to arrange them now.

Update the Readme with how it works, that it uses test data, and what remains untested. Ask who would own it and who could act as backup. Record those roles, or note that they’re still to be decided.

Check that the test switch will be hidden on live and that simulated failures can't be triggered there, even without the switch. Report what you checked and what remains unverified. Don't push live.

Check the dashboard

Read the build summary in workflow chat. For practice, note any checks you can’t complete in Readme and continue. You don’t need to recruit colleagues to complete this lesson.

Check the notes

Check that the data source, owner, backup, and remaining checks are recorded correctly. Roles you haven’t arranged should stay marked as “Not yet agreed.”

Check who can open the page

Before team use, ask two colleagues to try the same draft link using their own accounts:

A colleague with space access should be able to open it.

A colleague without space access should be blocked.

Use non-admin accounts for both checks.

If you’re practicing or the accounts aren’t available, record this check as unverified and continue.

Check the test-only controls

Read the results showing how the test switch and simulated failures are prevented on live.

Hiding the switch alone isn’t enough. If Tines 3B couldn’t verify that the simulations are blocked, keep that check open.

If something doesn’t match

Share the expected result and what happened in workflow chat. Ask for a focused fix, then repeat the affected check.

Don’t widen access just to complete a test. Ask Tines 3B to record unfinished checks in Readme.

Five go-live readiness questions

Push live

Publishing is optional. If you’re practicing, still using made-up data, or have important checks left to finish, keep the draft and continue to the knowledge check.

Review readiness

Review the five readiness questions and unfinished checks in Readme. Follow your organization’s review and approval process.

Ask Tines 3B to confirm how the live dashboard will load its first set of data without bringing over practice data or test settings.

Publish the draft

Select Push live in the branch selector.

For this first release, start with empty live storage if that option is offered and matches your agreed plan. The first update should load data from the ticket system.

If publishing is blocked, read the reason and ask someone with the required access for help.

Check the first update

Open the live page from Links.

Before data has loaded, it should show a no-data message. After the first successful update, check:

The last 12 full weeks and current week so far have loaded.

The refresh time is correct.

A known count matches the source.

You can ask Tines 3B to help run the first update manually rather than wait for the weekday schedule.

Check access on live

Repeat the allowed-user and blocked-user checks using the live link.

Check that the test switch is absent and ask Tines 3B to verify that simulated failures can’t be triggered on live. Finish these checks before inviting the team to use the dashboard.

If something doesn’t match

If someone can see information 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 dashboard. 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 who should see the dashboard, who should maintain it, and what needs checking before a team relies on its numbers. If you published it, finish the live checks before the team starts using it. If you’re keeping it as an exercise, leave it as a draft and keep your readiness notes. Next, you’ll follow Maya through her first month live.

Build it safely: You learned to consider both page access and access to saved data, so customer comments stay with the people who should see them.