OneSpot at a glance

OneSpot is the DC & NY Market’s one place for its dashboards, its tools, and the work each department does to save time. You sign in with your Ntiva Microsoft account, and what you see follows the groups you’re in.

Departments

Each team has a page of its own, such as Project Delivery or Account Managers. Home shows the ones you can see.

Dashboards

Live reports built in Claude and published here. They open inside OneSpot, and some let you tick boxes and write notes that everyone sees. See Build it in Claude.

Tools

Links to the apps a department uses. They open in a new tab.

Automations and Claude skills

Each department’s register of what it builds to buy its own time back, whether it paid off, and its library of Claude skills to download. See Automations and Claude skills.

SOPs and Guides

Project Delivery’s SOPs, baseline configurations and end user guides, kept in OneSpot: browse them by category, or search them all; preview one, then download it. See SOPs and Guides.

Make a wish

Ask for a new feature in OneSpot, or a change. See Make a wish.

What’s new

When you arrive and there’s news for you, OneSpot says so first. The bell beside your name keeps it for 30 days, with how many are new.

It’s private to Ntiva. Only people signed in with access see anything; each dashboard opens only for the people it’s shared with; and dashboards and their data are kept in OneSpot’s own storage, not on a public website.

Who can do what

In each department you’re a visitor, a member or an admin. Your role comes from the Microsoft groups you’re in, and it can differ from one department to the next.

• Visitors look in: they see what a department shares with visitors.
• Members work in the department: they see what it shares with members, write in its dashboards, add automations and Claude skills, and make wishes.
• Admins run the department: they see everything in it, publish and look after its dashboards, and keep its tools, categories and Automations in order.

• SOPs and Guides, and Automations, are open to everyone who can see the department, unless its admins choose members and admins, or admins only. Anyone it leaves out doesn’t see the card, and can’t open the page or anything on it.
• Writing in dashboards: each dashboard’s publisher chooses Who can save: members and admins unless they change it, admins only, or visitors too. Everyone else who can see it reads what’s saved.
• Whoever published a dashboard looks after it with the department’s admins (refresh, update, settings, unpublish), as long as they could still publish it there.
• A member can own a dashboard too, when the department’s admins hand it to them. They keep it up to date (Refresh data, New version, History, Download a copy) for as long as they’re a member there, and see it even if it’s for admins only. Its settings, sharing and unpublishing stay with the admins, and so do others’ notes, Saved entries and Redact. Members still don’t publish new dashboards.
• Market Leadership’s members and admins also see what every department shares with visitors, publish dashboards in any department, and see Saved entries wherever they can see the dashboard. Its admins review the wishes everyone sends.
• Market admins are admins in every department.

Need more access, or a different role? Email Russell Vidal (russell.vidal@ntiva.com) with the department and the role you need.

Finding your way

• Home shows the departments you can see. If you can see only one, OneSpot opens it straight away. The Ntiva logo at the top left takes you home from anywhere.
• Leaving a dashboard: if you’ve typed something in a dashboard and haven’t saved it, OneSpot asks before you leave it, whether you choose the logo, Back, Help or your browser’s Back. Choose Keep working to stay, or Leave anyway.
• A department shows OneSpot’s own pages first (its Automations, and in Project Delivery its SOPs and Guides), then its dashboards, then its tools. A dashboard opens inside OneSpot; a tool opens in a new tab. A card that says No link yet doesn’t open anything yet.
• Categories: each card says its category (Tools, Reports and so on), and the buttons above the cards show one category at a time. All shows them all again. OneSpot remembers your choice for each department on this browser.
• Grid or ring: the cards start in a grid. On a wide screen, Ring view turns them on a ring instead: use the arrows or the arrow keys, then Open or Launch. OneSpot remembers your choice on this browser. Phones, and devices set to reduce motion, always show the grid.
• What you see follows your groups. Each tile and dashboard is shared with its department’s visitors, members or admins, and Market Leadership’s members and admins see what’s shared with visitors in every department. So a department can look empty to you, and a colleague can see more than you do.
• Shared from another department: a dashboard can also show in other departments, view only. It sits under Shared and says where it’s from. See Show it in another department.
• A link to a dashboard opens it if it’s shared with you. If it isn’t, OneSpot says so.
• Light or dark: a dashboard built with the current skill can be shown light. Choose Light mode above it, or Dark mode to go back. OneSpot remembers your choice on this browser, for every dashboard that has both. Switching reopens the dashboard: if you’ve typed something in it you haven’t saved, OneSpot asks first. Older dashboards are dark only.
• SOPs and Guides: in Project Delivery, find a SOP, a baseline configuration or an end user guide by category, preview it and download it; members and admins upload new ones. See SOPs and Guides.
• Automations: a card in every department, ahead of its dashboards and tools: what it builds to save time, and its Claude skills to download. See Automations and Claude skills.
• Make a wish: members and admins ask for a new feature or a change with Make a wish in the header. See Make a wish.
• What’s new: when you arrive and there’s news, OneSpot says so first: new dashboards you can see (and ones newly shared with your department), your own dashboards due for a refresh, new and updated Claude skills in your departments, skills waiting for you to approve (admins), and news of your wishes. Choose Got it, or open one of them, to go on. Each piece of news shows once; a reminder to refresh shows once each time you sign in.
• New in OneSpot itself: when OneSpot gains something you’ll use (in your department, or for everyone), the greeting says so once, under What’s new in OneSpot, with where to find it.
• The bell, beside your name at the top, keeps the same news for 30 days, read or not, so nothing is lost if you chose Got it in a hurry. Its number is how many are new since you last looked; opening it counts as looking. What needs you (dashboards due for a refresh, skills to approve, a new skill release) comes first, as long as it applies.
• Signing in lasts 12 hours. Twelve hours after you last signed in to Microsoft, OneSpot signs you out, even with the page open, and asks you to sign in again with your password or sign-in method. Ten minutes before, a notice under the header says when, so you can save what you’re working on; anything not saved by then is lost.

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 Russell Vidal (russell.vidal@ntiva.com) to share it with you. Admins can download it from OneSpot with Download skill, beside Inventory, and OneSpot tells them when a new release is out.
• 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. Who can see starts at members and admins: the department’s visitors, and Market Leadership outside its own department, don’t see it unless you choose Visitors, members and admins. For a dashboard people write in, set Who can save too. If you can publish in more than one department, check Department. Choose its Category: a dashboard starts in Reports.
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 if you can see that dashboard, and Update it with this file if you manage it. Otherwise choose a different title.

Keep it current

These buttons sit above the dashboard, for the department’s admins and its owner: the person who published it, or took it over. The bar above each dashboard says who owns it. A member it was handed to gets Refresh data, New version, History and Download a copy, not Settings or Unpublish.

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, or a report saved as a web page (.html). 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. History can’t undo a Refresh data: to correct the numbers, refresh again with the right file.

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

Settings, then Save: it changes for everyone at once. You can also move it to another department you publish in.

Say how often its data is refreshed

Settings, Refresh every: a week, a month (unless you change it) or a quarter. A few days after that, a reminder shows above the dashboard for its owner and admins, and it’s flagged in the inventory.

Hand it to someone else

Settings, Hand it over to: enter the address they sign in with, then choose Hand over (Save doesn’t send it). They accept it the next time they open OneSpot, and it’s theirs from then on; they can also decline. They need to be a member or admin of that department, or in Market Leadership. A member who takes it keeps it up to date (Refresh data, New version, History, Download a copy), and its settings stay with you. Until they accept, nothing changes, and after 30 days the offer lapses.

Take it down

Unpublish: Undo on the message brings it straight back, for about 8 seconds. Later, a department admin can bring it back from Manage deleted in Edit mode. If you published it in a department you don’t run, you can too: from Unpublished, beside Publish dashboard, while you’re in that department.

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

Department admins also have Inventory, beside Help: every tile and dashboard in the departments they run, with who can see it, who owns it and what needs attention, and a download.

Show it in another department

A dashboard published in one department can also show in others, view only: Project Delivery’s portfolio in Account Managers, say. Its department’s admins and the dashboard’s owner (not a member it was handed to) choose where.

1. Open the dashboard and choose Settings (or do this while you publish it).
2. Under Also show in (view only), tick each department, and choose who there can see it: visitors, members and admins; members and admins; or admins only.
3. Choose Save. It shows there at once, and people there hear of it in their greeting.

• It’s view only there. People open it and read what’s saved in it, but they don’t save to it, and they don’t see Settings, New version, Refresh data or Unpublish. Those stay with its own department.
• Where it sits: under Shared, saying “Shared from” its department. Back returns to the department it was opened from.
• Its notes go with it: everyone it’s shared with reads what’s saved in it. Share only dashboards whose notes are fine for them to see.
• Their admins can hide it from their page: in Edit mode, Hide from this page (and Show on this page to bring it back). It’s still shared, and a link still opens it. To stop sharing, its own department unticks the department in Settings.

Want one like it for your department?

Admins can take a copy of any dashboard they can see, in their department, shared with it or elsewhere, and rebuild it in Claude with their own data.

1. Open the dashboard and choose Download a copy, then Download the file.
2. Copy the prompt it gives you. In a Claude chat with the OneSpot Dashboard skill, attach the file and paste the prompt. Claude asks for your data and keeps none of the other department’s.
3. Publish what Claude gives you in your department with Publish dashboard. It’s a dashboard of its own: notes and ticks saved in the original don’t come with it.

The file holds the other department’s data as it shows now, so keep it within Ntiva. Each download is recorded.

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 (not a member it was handed to) 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 department’s admins, the dashboard’s owner (not a member it was handed to) and Market Leadership see it all in Saved entries, beside the dashboard, and can download it as a spreadsheet.
• Typed something by mistake? The department’s admins and the dashboard’s owner (not a member it was handed to) 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. A note whose row is no longer in the data shows under “Unmatched notes”, in dashboards built with the skill from October 2026.
• A new version keeps them when it saves the same way. If it wouldn’t show them, OneSpot says how many before it goes live, with a prompt that asks Claude to keep them, and Publish anyway. Nothing is deleted either way.
• In Claude’s preview, a “Sample mode” notice shows and nothing is kept, and the preview in Publish dashboard saves nothing either. Inside OneSpot, saving is real.

Automations and Claude skills

Each department’s Automations (a card ahead of its dashboards and tools) tracks what it builds to buy its own time back, and whether it paid off. It’s also the department’s library of Claude skills. Everyone who can see the department sees it, unless its admins choose fewer (Edit mode).

Add an automation (members and admins)

1. Choose Add automation, then its Type: a Claude skill, a script, a Power Automate flow, a ConnectWise workflow, a template, or other.
2. For a Claude skill, choose the skill’s .zip, as Claude downloads it. OneSpot checks it, and its name and description fill in from its SKILL.md.
3. Say what it is and what it does, its Phase, and who gets the time back.
4. Describe the task today: the Minutes it takes now and the Times a month. That’s what the work costs, and what it can save. How long it takes once automated isn’t guessed: the check-ins measure it.
5. Add how sure you are, the hours spent building it so far, and anything it’s blocked on. Choose Save.

• Phases: Idea, Design and Build; Internal, Beta and Live testing; Rollout, QC and Live; or Parked and Killed. The bar beside each one shows how far along it is, and a month in one phase without moving is flagged.
• The register is a list: a row each, with who published it, its phase, when it last changed, its skill’s version (with Download) and what it saves a month. Choose a column’s name to sort by it; choose it again for the other way, and a third time for the register’s own order. Choose a row for its details: what it does, the facts, the saving, its skill and earlier versions, and Edit and Check in for whoever may.
• Who changes one: whoever added it (while they’re still a member or admin there), and the department’s admins. Removing one removes its skill’s files too: to keep the record, set its phase to Killed instead.

Check-ins measure the saving

• At 30, 60 and 90 days live, choose Check in and say how long the task takes now, and how many times a month it runs. The page lists the check-ins that are due.
• The saving is the minutes each run saves, times the runs a month now. If people stop using it, the saving falls with it. Until the first check-in, it shows what the task costs today, not a guess.
• The latest check-in counts, and only the days an automation is live add to what it has banked: a spell parked doesn’t.

The figures

Saved per month

The measured savings of the live ones.

Of a person, back

Those hours as a share of one person’s month (160 hours).

Banked to date

The hours saved since each went live, against the hours spent building them all.

In our sights

What the tasks still being built cost today.

Where the time goes back

Who gets the hours: the team, its managers, other departments, clients, or everyone.

Dollars use the department’s rate: $58.34 an hour unless its admins change it. Its admins can also turn Show dollars off, and the page shows hours only.

Claude skills

• Get the latest: Download on its card saves the skill as a .zip. In claude.ai, add it to your skills in place of any earlier version of it. Earlier versions stay listed under the latest.
• Update a skill: whoever added it, or the department’s admins, open it and choose Upload new version beside Download, then the updated .zip, and say what changed. Its details stay as they are, and its SKILL.md may call it something new: it’s still the same skill’s next version. Each upload is a new version, with when and by whom; the same file twice is refused. (Edit takes the updated .zip too.)
• Added by mistake as a new one? When you add a skill whose .zip has the same name as one already in the department, or one much like it, OneSpot lists it and offers Upload as version N of it, so an update never becomes a second skill. If yours really is a different skill, tick Mine is different instead.
• Approval: a skill a member sends, or a new version of one, waits for one of the department’s admins. Until then only they and the admins see it. Admins Approve or Reject it on its card, and whoever sent it can Take it back. Admins’ own uploads go out at once.
• Members hear of it: the greeting tells a department’s members about new and updated skills once they’re approved, and its admins about skills waiting for them.
• What a skill’s .zip needs: a SKILL.md with a name, at the top of the zip or in its one folder; up to 10 MB; and no password. If OneSpot refuses one, it says why.

SOPs and Guides

SOPs and Guides, the first card in Project Delivery, is where its SOPs, baseline configurations and end user guides live. OneSpot keeps the files; a few that couldn’t be copied in still open in SharePoint, marked Still in SharePoint.

• Browse by category: Baseline Configurations (a tile for each technology: Firewall, Intune, Microsoft 365…), Engineering SOPs, Project Management SOPs and End User Guides. Each has its own address, so Back works and you can share a link to one. The trail above the list takes you back up.
• Search looks through all of them, by any words in the title, the technology, the topics or what it covers. Every word you type has to match, and a match in the title comes first. Choosing a topic on an entry searches for it.
• Ask searches inside the documents. Describe what you need in your own words (“reset MFA for an admin”, “firewall rules for a branch office”) and choose Ask, or press Enter. Claude reads the SOPs’ text and picks up to five, best first; each shows the passage that matches, in the SOP’s own words, with the words that matched marked. Choose its title to open it. Decommissioned SOPs are never an answer. A PDF is matched by its title, topics and what it covers, not its text. Claude answers 5 of each person’s questions an hour and 15 a day; past that, Ask still answers, by the words in the SOPs, and says so.
• Ask in Automations: on any department’s Automations, describe what you need done (“draft a weekly status report”) and choose Ask. It looks through the automations and Claude skills in every department you can see, so you find one before building it again. Each answer says where it is, with Open and, for a skill, Download the skill. It shares Ask’s limits and Claude’s budget.
• A skill that’s already there: when you upload a skill, OneSpot says if the very same file is in a department you can see, and Claude names skills that do the same job, with why. To add yours anyway, tick Mine is different. The very same file can’t be added twice in one department: upload it as a newer version of that one instead.
• Claude’s budget: OneSpot spends at most $100 a month on Claude, for Ask and for reading uploads together. Its admins see how much is used once it passes $80. When it’s used up, Claude pauses until the 1st: Ask still finds SOPs by their words, and uploads still work, with the form filled in by hand. Each person can also have Claude read 40 uploads a day; a standardized SOP files itself without Claude.
• Preview one by choosing its title: the document opens in a pop-up as it was written, with no download. Word shows its pages (fonts, tables, pictures, headers), Excel its sheets with their tabs, and a PDF opens in your browser’s own viewer. Beside it: who wrote it, when it was created and last changed (as the file itself says), and who put it in OneSpot and when. Download saves it under the name it was uploaded with. A PowerPoint file shows its text.
• Possible duplicates: entries whose titles are the same but for a version or a copy’s number are marked. The preview lists the others like it; if one is older, remove it.
• Upload (Project Delivery’s members and admins): choose one file or several. Each is checked, then read, and Claude suggests its title, category, technology, who it’s for, its topics and what it covers, and whether it’s a newer version of one already here. Check each field, change what’s off, then save; with several files, each comes in turn. Nothing is filed until you save.
• A newer version: to update one, download it, edit it, then open it and choose Upload new version. (Uploading it as a new file works too: when Claude, or the file’s name, matches one already here, the form offers to replace it; if it’s a different document, choose No, add it as a new entry.) Say what changed: Claude compares the two files and drafts it, and you check it before saving. The entry keeps its place, the new file is the one everyone previews and downloads, and its card says who uploaded it and when.
• What changed: the tab of that name in the preview lists its versions, newest first: who uploaded each, when, and what changed in it. Each older version can still be downloaded; OneSpot keeps the last 10.
• Big clean-ups (Project Delivery’s admins): with several files chosen in Upload, Save all as filed saves every one without the form. Each goes where its own properties say (a standardized SOP names its category and technology in Word’s File > Info), or where Claude suggests; it replaces only the entry with its file name; and a list at the end says what became of each. Select puts a box on each entry: tick them (or Select all here), then Remove selected.
• Change or remove any entry with the buttons on it. One still in SharePoint comes into OneSpot when you change it and upload its file: it keeps its title, category and topics.
• No longer used, but worth keeping? Open it and choose Decommission: say why, and pick what replaced it, if anything. It stays in its place, marked Decommissioned and listed last, and opening it shows when, by whom, why and what replaced it. Nobody can preview or download it, and it can’t take a newer file, until someone chooses Restore.
• Files: PDF, Word, Excel or PowerPoint, up to 25 MB. Files with macros, scripts, embedded programs or a password are refused, with what to do instead. A file is live as soon as it’s saved, and anyone who can see Project Delivery can preview and download it. Removing an entry removes its file, and its older versions, from OneSpot (a link’s file stays in SharePoint).
• What Claude reads: to suggest where an upload goes, OneSpot sends its text (or the PDF itself) to Claude, Anthropic’s AI, through Ntiva’s account; for a newer version, the text of both files, to draft what changed; for Ask, your question, the library’s titles and topics, and the passages that share its words. What you ask isn’t kept. It’s only a suggestion: the form is yours to change, and if Claude isn’t available (or the files are PDFs) you fill it in yourself.
• Writing a new SOP, or putting one in the template? Use the ntiva-sop Claude skill, from Project Delivery’s Automations. Give Claude the Word file, a PDF or your notes: it makes a Word file in the right template (the Intune format for a Baseline Configuration, the PM cover-page format for a PM or Engineering SOP), checks nothing was dropped, and lists what you need to confirm. Upload that file here: OneSpot fills the form in from it. When a Word file isn’t in its category’s template, the upload form says so under Category. You can still save it.

The Project Life Cycle

• What it is: how a project runs at Ntiva, phase by phase, with the SOPs for each step. Choose Project Life Cycle beside Ask in SOPs and Guides: the phases go round a wheel, in order, and the SOPs used throughout a project sit in its middle. On a phone it’s a timeline.
• Reading it: choose a phase for its steps, and each step’s SOPs; choose an SOP to open it, as anywhere in SOPs and Guides. Whoever sees SOPs and Guides sees it.
• Where it started: the SOP Chronology’s phases (Initiation, Planning, Execution, Closing, then Warranty), with its SOPs found by their titles.
• Changing it (Project Delivery’s admins, and the people they name): choose Edit life cycle. Add, rename, reorder or remove phases (up to 8) and their steps (up to 12 a phase); on each step, Choose SOPs (up to 10). Not placed yet lists the Project Management SOPs in no step. Nothing changes for anyone until you choose Save changes; leaving first asks.
• Who can edit it: the department’s admins name people, such as a project manager, by the address they sign in to Microsoft with: Editors on the page, or the second button on SOPs and Guides’ card in Edit mode.
• An SOP decommissioned or removed drops off the wheel for readers; its editors see it marked, to replace.

Make a wish

Want a new feature in OneSpot, or a change? Members and admins choose Make a wish in the header.

• Say what you’d like, and what it would help you do, in up to 2,000 characters. You can send up to 10 a day.
• Market Leadership’s admins review every wish together. They give each a priority, then close it as Completed (it’s done) or Resolved (closed without building it), with a note.
• You hear back in your greeting when yours is closed, with their note.
• Only Market Leadership’s admins see the wishes people send.

A department’s tiles

A department’s admins look after its tiles, the cards that open a tool in a new tab.

• Edit mode, at the top of the department, puts a pencil and a trash can on each tile, and adds Add tile. Each save goes straight to OneSpot, for everyone. The department’s dashboards show there too, with their own buttons.
• A tile’s fields: Category is the small label under its name, and what the buttons above the cards filter by; Order sets its place, lowest first; URL is the https:// address it opens, or # while there’s no link yet.
• Who can see works as it does for a dashboard: visitors, members and admins; members and admins; or admins only.
• SOPs and Guides, and Automations, have a card in Edit mode too, first: its Who can see button (or the card itself) sets who gets the page, as for a tile. They start open to visitors.
• Category: each tile is in one of the department’s categories. Categories, in Edit mode, adds, renames and reorders them. A category with cards in it can’t be removed: move its cards to another first.
• Deleted one by mistake? Manage deleted brings it back, or removes it for good.
• Backup downloads this department’s tiles as a file, to keep.

Questions people ask

Getting around

Dashboards

Automations and Claude skills

Wishes and privacy

When something goes wrong