The one spot for every dashboard.

Before you start

• Who can publish: a department’s admins, in their own department, and Market Leadership’s members and admins, in any department. Everyone else can view the dashboards they’re allowed to see.
• The OneSpot Dashboard skill has to be on in your claude.ai account. It teaches Claude OneSpot’s look and rules, so the file works the first time. If Claude doesn’t use it when you ask for a OneSpot dashboard, ask for the skill to be added to your account.
• Your data: a spreadsheet, a table pasted into the chat, or a description. With no data, Claude uses made-up sample values and says so.

Build it in Claude

Start a new chat in claude.ai and describe what you want. Saying “OneSpot dashboard” is enough for Claude to use the skill. These prompts are a good start; replace the parts in brackets.

Use the OneSpot Dashboard skill. Build a dashboard for [department] showing [what it’s for]. The numbers that matter most are [the key figures]. Here is the data: [attach the spreadsheet or paste it].

Use the OneSpot Dashboard skill. Build a dashboard for [department] showing [what]. It should refresh from a spreadsheet with a sheet named [sheet name] and the columns [column A, column B, column C].

Use the OneSpot Dashboard skill. Build a dashboard for [department] where people can tick [what to tick, such as the services to offer] and add notes for each [client, project], saved in OneSpot so everyone sees them later. Let people filter by [account manager, status] and sort the table.

Convert this dashboard for OneSpot with the OneSpot Dashboard skill. Keep what it shows: the same figures, charts and tables.

Attach the .html file with the last prompt.

Check it in Claude’s preview: the numbers, the charts, the filters. Ask for changes in plain words. When it looks right, download the .html file.

Publish it

1. Go to your department.
2. Choose Publish dashboard, then choose the file.
3. OneSpot checks the file and shows a report.
   • Ready to publish: a live preview appears next to it.
   • Can’t be published yet: choose Copy prompt, paste it into the same Claude chat, and choose the new file Claude gives you.
4. Set the title, description, icon and Who can see. For a dashboard people write in, set Who can save too.
5. Choose Publish. The dashboard opens right away and shows as a card in the department.

A department can’t have the same file twice, or two dashboards with the same title. When OneSpot finds one, it offers Open it or Update it with this file instead.

Keep it current

These buttons sit above the dashboard, for the department’s admins and the person who published it. The bar above each dashboard says who published it.

What you can do follows the groups you’re in today. If you move to a group that can’t publish in that department, its admins look after the dashboards you published there. Move back, and they’re yours to manage again.

Show new numbers in the same layout

Refresh data: choose the spreadsheet. OneSpot shows what it found and asks before everyone sees it.

Change the layout, charts or wording

New version: choose the updated file from Claude. The link and the card stay the same.

Go back to an earlier version

History: restore any of the last 15 versions, with the data it had.

Rename it, or change its icon, who can see or who can save

Settings: saved straight away.

Take it down

Unpublish: Undo on the message brings it straight back. Later, a department admin can bring it back from Manage deleted in Edit mode, and you can from Unpublished at the top of the page, if you published it somewhere you don’t run.

A new version shows the data inside its own file. If you refreshed the data since the last upload, refresh it again afterwards.

Dashboards people write in

A dashboard can let people tick boxes and write notes, such as the services to offer each client and what was discussed. OneSpot saves them centrally, so everyone who can see the dashboard sees them later, on any device.

• Who can save is the publisher’s choice, and can be changed in Settings. It starts at members and admins. Everyone else who can see the dashboard sees what’s saved, read-only.
• Notes belong to whoever wrote them. Only they can change a note. They can delete it, and so can the dashboard’s owner and the department’s admins.
• Ticks are shared. Anyone who can save can change them.
• It saves as people go. A tick saves when it’s ticked and a note when it’s added: there’s no Save button to forget. If someone closes the page while a save is still on its way, OneSpot asks first.
• Every change is recorded: what changed, who changed it and when, kept for a year. The dashboard’s owner, its department’s admins and Market Leadership see it all in Saved entries, beside the dashboard, and can download it as a spreadsheet.
• Typed something by mistake? The dashboard’s owner and its department’s admins can Redact an entry in Saved entries: its words are cleared from every change to it, and who and when stay. If it’s still saved, delete it in the dashboard too.
• They stay with the right row after Refresh data, as long as each row keeps its ID, like a client ID.
• In Claude’s preview, a “Sample mode” notice shows and nothing is kept. Inside OneSpot, saving is real.

When something goes wrong