How do I keep a register of our tools?

For admins: list the tools your company uses, say who owns each one and what data may go in it, answer how much AI is in it, and mark the ones that are never worth reviewing again.

The Tools page is your company’s register of the software it uses. You add tools by hand, import a spreadsheet or import your software list from Velory, and say who owns each one, what it is for and what data may go into it.

Managers can read this page. Only a company admin can change anything on it.

Flow does not hold what a tool costs, how many seats you have or when a contract renews.

In this guide:

• The three tabs
• Retired, still in use
• What to check
• How far the registry is filled in
• All tools
• Add one tool
• Import a spreadsheet
• Import from Velory
• Requests
• One tool’s page
• Fill in the registry
• Fill one field across every tool
• Record teams
• Say how much AI is in a tool
• Link the policy rules that apply
• Mark a tool as reviewed
• Where “AI features” and “EU residency” come from
• Filter and export
• Retiring a tool
• What this page does not do

The three tabs

The same three tabs are on every Tools screen:

• To do is what stands between you and a complete AI register.
• All tools is the whole list, with what is missing on each row.
• Requests holds the tools people have asked for, and the answer each one got.

One line above them says how many tools you have, how many count as AI tools, and how many are reviewed.

Retired, still in use

Only a company admin sees this list.

It lists tools you retired that people still named in Know Your AI, with how many people and teams have them. Select one to open the tool.

A team is only counted once at least five of its people finished Know Your AI, and a team under five people is never counted. Nothing is read while a round’s results are held, and only answers given before the results were sent are read.

Flow recognises a tool in Know Your AI only when it is on your list and Velory has described it. A tool that was never on your list is not shown here.

What to check

To check lists what Flow found on your own tools. Every line comes from a fixed rule, and no AI writes it. Select a line to open the tool, or the list of tools it is about.

• Clashes with policy: an AI tool marked 3 Confidential or 4 Restricted while your data rules keep customer contracts or personal data out of AI tools.
• Data leaves the EU: a tool marked 3 Confidential or 4 Restricted that keeps its data outside the EU. Either Velory checked this, or the tool’s own website says so and the row says it was not checked by Velory.
• Not checked: Velory has not checked whether there is AI in the tool, and the tool has no answer of its own from when it was added.
• No use policy: an AI tool with no use policy, or one still in Draft.
• Training behind (admins only): AI tools where under half of the people who have them finished Know Your AI.
• No policy rule linked: AI tools with no approved policy rule linked. It opens All tools with the policy rule filter on AI tools with no rule and reviewed tools hidden, so the table lists the same tools.

A retired or reviewed tool is left out. The number beside To do counts these lines and the retired tools still in use.

How far the registry is filled in

The Registry list at the foot of To do has a bar for business owner, AI in this tool, use policy, data class, tech owner and data region, with how many of your tools have each one answered. Select a row to open the page that answers that one field down the whole list. AI in this tool and Data region have no such page: Velory checks those against the vendor, so there is nothing for you to fill in.

These bars count your reviewed tools too. The registry is your record under the EU AI Act, and that record is about every tool you have. Retired tools are left out. A manager does not see the two owner bars.

When both lists are empty, the tab says so above the registry and points you at All tools.

All tools

The table has a row per tool: who owns it, how much AI is in it, its data class, where its data sits, and whether it has a use policy.

A field nobody has filled in reads Missing. A fact Velory has not checked reads Not checked. The two are different: you can fill in the first, and only Velory can check the second. Region is always the second kind.

Policy rules counts the approved policy rules linked to each tool.

Filter by business owner (admins only), by policy rule, by AI, by data class, or by Missing, which narrows to the rows with a registry field still to fill in. Select any row to open that tool’s own page.

Add one tool

1. Open Tools in the left sidebar, then All tools.
2. Select Add tool.
3. In Tool, start typing the name. The box suggests every tool Velory has described that you do not already have.
4. In Approval, paste the link to where the tool was approved: a Linear ticket, a Slack thread, a document. The link has to start with http:// or https://. Leave it blank if there is nothing to link to.
5. Select Add tool.

You do not have to pick a suggestion. Type any name and the tool goes on your list. Velory still matches what you typed against the tools it has described, including other names a tool goes by, so “M365” is added as Microsoft 365.

You can type the tool’s website instead, such as paper.design or https://linear.app. If the website belongs to a tool Velory has described, that tool is added, the same as if you had typed its name. When the name you give is a different product on that website, such as Microsoft Whiteboard on microsoft.com, Flow does not add the described tool in its place: it treats the name as a new tool. If not, the dialog comes back showing the name and icon the site uses for itself, with its address beside them. You can change the name there. Select Change to type something else, or Add tool to add it. Flow reads the name and icon from the tool’s own website only, and nothing about you goes with the request. If the site cannot be read, the website’s address is used as the name and the tool has no icon.

If Velory has not described the tool, the dialog asks for a Category. Pick what the tool is for. Flow compares tools of the same kind when it looks for overlap, and a tool with no category is left out of that reading. A tool Velory has described keeps the category Velory gave it, so you are not asked.

When the dialog shows a website Velory has not described, it also asks whether the tool uses AI, where its data is stored, and for its DPA, sub-processor and trust center links. Select Fill in from the website to have Flow read the tool’s own site and fill these in. Each answer the site gave says Found on and names the page. Change any answer that is wrong: an answer you change is kept as yours, without a page. Your company can run 20 new website checks a day, and a website another company had checked in the last 30 days does not count toward them. Past that, fill the answers in yourself or leave them blank. When you add the tool, Velory sees it, but not who added it, so it can add the tool to the catalog.

A website anyone can publish on, such as a GitHub Pages site, is not read. You can still answer the AI and data questions yourself, the links are not kept, and Velory is not told about the tool.

A tool nobody has described shows no verified facts about AI features or where its data sits until Velory describes it.

The dialog also asks which teams use the tool, its business owner and its data class. Why you have it and its use policy are filled in afterwards, on the tool’s own page.

Import a spreadsheet

1. On All tools, select Import CSV.
2. Drop your file on the panel, or select choose a file. It is read in your browser and never uploaded. A file can hold up to 500 rows.
3. Read what the import will do, then select Add (or Fill in, when the file adds no new tools).

Select Download a template to get a file with the right headings. The file needs a heading line and one tool per row. These columns are read:

Cost, seats and renewal columns are skipped, and so is any other column. Both commas and semicolons separate the columns, so a file saved from a Swedish or German Excel is read correctly.

An owner’s email address must belong to someone on your People list. An address that does not is left out, and the preview marks the row Not on People. The tool still goes on the list.

The preview sorts every row into one of four tabs:

• In the catalog: a tool Velory has described. It goes on under the name the rest of Flow uses. It is matched by name, by another name it goes by, or by its website.
• New: a tool Velory has not described. It goes on under the name in your file.
• Already listed: a tool you already have. Its empty fields are filled in, and nothing on it is overwritten. The tab says which fields each row fills. To change a value that is already there, edit it on the tool’s own page.
• Skipped: a row that is not imported, with the reason. For example, it has no tool name, or it names a tool that is further up in the same file.

Where part of a row cannot be read, such as a team name that does not exist, the preview says so under the tool’s name. The rest of the row is still imported.

After the import, the website of each new tool Velory has not described is checked, once for tools that share a website: whether it has AI in it, where its data is kept, and links to its DPA, sub-processor list and trust center. Each answer is kept with the page on the tool’s own site it came from, and the tool’s AI shows as Not verified, with that page, until Velory checks it. The panel counts the checks as they finish. Your company can run 20 new website checks a day, and a website another company had checked in the last 30 days does not count toward them. A tool past the limit is not checked. If you leave the panel while the checks run, the checks that have not started do not run. Velory sees each new tool, but not who added it, so it can add the tool to the catalog.

Import from Velory

If Velory is your HR system, All tools also has Import from Velory. It reads the software list you keep in Velory with the token you connected under People, then shows the same preview as a spreadsheet. The button is not there for a company on another HR system.

1. On All tools, select Import from Velory. Flow reads your software list straight away.
2. Read what the import will do, then select Add (or Link, when every tool is already on your list).

Flow reads the name of each tool on the list, and the AI agents too. An AI agent with no vendor in Velory is left out and shows under Skipped: a company’s own agent can be named after a person. Flow does not read cost, seats, plans or agreements.

The preview has the same four tabs. Nothing you set on a tool you already have is overwritten. Flow only links it to its entry in Velory, so if the tool is renamed in Velory later, the next import knows it is the same tool and does not add it twice. A tool that came in from Velory keeps the name it had when it came in. To rename it, edit it on the tool’s own page.

A company setting up Flow can also bring in its people and its software list in one go, from the first step on Home. See setting up your company.

You can import again at any time. Only tools that are new on the list in Velory are added. If the list in Velory changes between the preview and your press, nothing is imported and the panel asks you to read it again.

Before it reads any software, and again after, Flow checks that the token still reads the Velory company you connected. If it reads another company, or Velory refuses it, the panel says so and nothing is imported. The token also needs to see software in Velory. A token made by a company admin who sees the whole company can. When the token is the problem, the panel links to Open HR system settings, where you replace it.

Requests

Requests is where a tool somebody asked for turns up, with the answer it got.

Select Copy request link at the top of the page and share that link with the company. The link is printed under the tabs as well, so you can select it by hand if your browser will not let the button reach the clipboard.

Anyone on your people list can open it, sign in the way they already do, and ask for a tool. They can type the tool’s name or its website, and select Check to see the name and icon Flow reads from that website. They see what you already have in the same category before they send. Their manager, taken from your people list, gets one email and answers from it without signing in.

For a tool Velory has not described yet, the form also asks whether it uses AI, where its data is stored, and for its DPA, sub-processor and trust center links. Select Fill in from and the tool’s website to have Flow read the answers off that website. Each answer it finds shows the page it came from. An answer it cannot find there says Not found on and the domain. Flow never takes an answer from another website, and it does not check a site anyone can publish on, such as a GitHub or Notion page. The person can change any answer before they send. A website Flow read in the last 30 days fills in straight away. Flow reads up to 20 new websites a day for each company. Past that, the answers say Not checked yet, and the request still goes through.

A tool Velory has not described goes to Velory to review against the vendor’s own site. Velory sees your company’s name and the answers that were sent, never who sent them. If Velory adds the tool to its catalog, or matches it to a tool already there, your request and the tool on your list use the answers Velory checked from then on. The answers that were sent stay on the request.

Somebody whose manager is not on the list, or whose manager has left, sends their request to you and the other admins instead. Every admin gets their own link, the first answer is the one that counts, and the request records which of you gave it.

The person asking can also send it to someone else: the company’s admins, or anyone on your people list except themselves. When they do, their manager gets a copy with no link, and the row here says who it went to, for example “Sent to Cleo Lind, not their manager”.

An admin who proposes a tool never receives their own request; it goes to the other admins. And if there is nobody left who could answer, the person is told so on the form and cannot send until they pick someone or you set their manager on the People page.

Each row says the tool and one line of status:

• Waiting, with the team it came from and the day it was sent.
• Approved, with the day, the team, and whether it has been added to your tools.
• Declined, with the day and the team.
• Approved on one day and closed on another, for a request a manager approved and an admin then stopped.
• Adding not finished, for the rare case where adding one to your tools stopped half way. Select Finish adding on that row to complete it.

A second line under the status says who the request was sent to: their manager, the admins, or the person they picked.

A request from somebody whose Flow data has been erased reads Former employee where the team would be. The decision stays, because it is your company’s record of what it approved.

Decline request on a waiting row, and Close request on one a manager has already approved. The word changes because the act does: declining is the answer, and closing keeps the manager’s answer and stops the request. It is yours to use when the person who should answer is out of reach: their manager has left or changed, or the link they were sent has run out. It closes the request and tells the person who asked. You cannot approve from this page, only decline, because approving is the manager’s job.

It also works on a request a manager has already approved, as long as nobody has added it to your tools. That is the case where a tool gets added to your list by hand while the manager is deciding: the approval stands on the record, but the request is no longer one you can act on, and this is how you close it. The person who asked is told their request was approved and then closed.

The approval is not erased when you do this. The row keeps the manager’s answer and its date, and records your close beside it, so the request reads as approved on one date and closed on another. A closed request is finished: nobody can add it or answer it after that.

Adding an approved request to your tools

An approved request carries one button: Add to tools. Use it once your company actually has the tool.

It adds the tool to All tools and links the new tool back to the request it came from. From there it behaves like any other tool: you fill in its owner, its data class and its use policy on its own page.

It is refused if that request is already on your list, if the manager has not approved it yet, or if the tool is already on your list. Each refusal says which.

You cannot approve a request from this page. Approving is the manager’s job, and yours is to act on what they approved.

One tool’s page

Select a row in All tools to open the tool. Its name is at the top, with whether it is an AI tool or an add-on, and whether it is retired or reviewed. The line under the name is the tool’s own website and, for company admins, how many people in how many teams use it. Teams under five people are not counted.

The page reads top to bottom:

• Left to do: for a tool with rows on the To do tab, what those rows are, each linking to the part of the page that fixes it. A reviewed or retired tool has none.
• Registry: the business owner and the tech owner, each with the job title from your people list, why you have it, the use policy and the data class.
• From the Velory catalog: the facts Velory checked on the vendor’s own site. See Where “AI features” and “EU residency” come from.
• Policy rules that apply: see Link the policy rules that apply.
• Training: for company admins, each team that has the tool and how many of its people finished Know Your AI.

Each registry row has Add (when it is empty) or Edit on its right. Both open the form with the cursor in that field. Edit all fields in the ··· menu at the top opens the same form. Cancel leaves without saving.

A use policy reads Being written or In force. Next to one that is being written, Put in force marks a policy that is being written as agreed. Company admins see Written by beside the policy: the admin who last changed its words, and the date. Managers do not, for the same reason they do not see owners. Saving the same words again, or putting a policy in force, does not change it. A policy written before this was added shows no name or date. If that admin’s data is erased, the date stays and the name goes.

A use policy that is In force is also read as a policy document. It appears on Policy, under 1. Documents, as soon as you save, named after the tool (for example “Cursor use policy”). Reading it takes about a minute, and then the rules Flow finds in it join your Commitments list like any other document’s. They do nothing until you approve them there. When you approve one, Flow links it to this tool for you, and if the policy later stops saying it, that link goes. A tool’s use policy is about that tool, so Flow does not take your company’s ground rules from it. Change the words and Flow reads the policy again. Put it back to Being written, clear it, or retire the tool, and the document leaves Policy. Rules you already approved stay approved.

Fill in the registry

Open the tool and select Edit or Add on a row, or Edit all fields in the ··· menu. You can set:

• Business owner: the work address of whoever is accountable for the tool. Start typing and Flow offers your people list. When your people list has a name for the address, Flow shows it under the box and you type nothing else. An address that is not on the list is fine too, and so is someone on it without a name: Flow then asks for Their name, because it has no other way to know it.
• Tech owner: the same, for whoever runs it.
• Why we have it: one line on what the company buys it for.
• Use policy and Policy state: what may go in the tool, and whether that policy is Being written or In force.
• Data class: 1 Public, 2 Internal, 3 Confidential or 4 Restricted.
• Category: only for a tool Velory has not described. A described tool takes its category from the catalog.
• Approval link: where the decision to use it is written down. It has to be an http or https address under 500 characters, with no username or password in it. This is a page people open, so a link carrying a password is refused rather than quietly shortened.

EU residency is not a box. Velory checks it against the vendor’s own pages, so it is in the From the Velory catalog section and reads either the answer we checked or Not found. For a tool Velory has not checked, the Data region column in All tools shows what the tool’s own website says, followed by (vendor’s site). It does not count as the field filled in until Velory checks it.

If a save is refused, the form comes back with everything you typed still in it, and a line at the top names the box Flow could not read and puts your cursor in it. Nothing is written until every value on the form is one Flow can read.

If your Why we have it or Use policy is over its limit, the box comes back with what you wrote still in it, over the limit, so you can shorten it there. Text more than twice the limit is the one thing a refusal cannot bring back: that box shows what is still saved instead, and a line at the top says to paste your new text again. Flow never returns part of a long text, because a part that looks whole is one you would save by mistake.

Fill one field across every tool

Five registry fields start empty on every tool you add. Opening each tool to answer one of them is a long afternoon, so each field has a page of its own that lists every tool with that one field to fill in.

1. Open Tools. The Registry list at the foot of To do has a row per field that still has tools to answer, with a bar and how many of them are done. A field every tool has answered shows a full bar.
2. Select the field you want to work through.
3. Answer a row and select Save on that row, or tick several rows, pick one answer in Set several at once at the top, and select Set ticked tools.

The fields with a page are business owner, tech owner, why we have it, use policy, and data class. Where the data sits and AI features have no page, because Velory checks those against the vendor’s own pages.

The title says how many of your tools have the field answered. It counts the same tools the table lists, so the number and the list never disagree. Retired tools are left out of both, and of what a page will save: a row retired while you had the page open is refused rather than quietly answered. Reviewed tools are in, because the registry is your record rather than a review.

An admin also sees each row’s business owner, so you can see who to ask. On the business owner page that column is not repeated.

An owner is a person. If someone is listed as the owner of a tool, they see that on their own results page: the tool, and whether they are the business owner or the tech owner. They cannot change it there, so they will ask you.

Only admins see an owner. A manager who opens Tools reads what the company uses and what is missing, with no owner anywhere: not the column on All tools, not the filter, not the two rows on a tool’s own page, not the column on a fill page, and not the owner columns in the export. The business owner and tech owner pages are admin-only, so a manager does not get a row for them under To do either.

If a value is refused, the page comes back with a line naming the tool and the box, your cursor in that box, and nothing written. Set ticked tools checks the value before it touches a row, so either every ticked tool takes the answer or none of them does. Press it with nothing ticked and Flow says so rather than reporting a save.

A box left on “Leave as is” changes nothing. That is what every box starts on, so setting one thing across a page of tools leaves the rest of the field alone on all of them. Nothing on the bar can empty an answer either. Clearing one is a job for that tool’s own row, where you can see what you are clearing. Press Set with every box still on “Leave as is” and Flow asks you to choose an answer first.

Setting Policy state on its own adopts the policies those tools already have, without touching a word of them. A ticked tool with no policy at all has nothing for a state to describe, so it is left alone and counted on the way back.

What you save here is written where the tool’s own page writes it, so the two screens always show you the same answer.

Import a spreadsheet of answers

Import from a spreadsheet at the foot of the table takes a file of answers for the field you are on.

1. Select Import from a spreadsheet, then choose your file. It is read in your browser and never uploaded.
2. Read what the import will do. Every line it will not write is named.
3. Select the button naming how many tools will be answered.

One import answers up to 900 tools. A file that would answer more is refused with that number, rather than written in parts that could each fail on their own.

The file needs a heading line, a column of tool names, and at least one column for the answer. Cells hold what the page shows: an owner by their work address, an answer as it reads in the dropdown.

An address and a name are two columns, never one. A name can hold anything, including the middot Flow prints between the name and the team on screen, so one column could not be taken apart again without guessing.

The address is what counts. A line with a name and no address beside it is refused, because a name on its own is nobody Flow can find.

Flow also takes the values it stores, so a file you downloaded with Export CSV on All tools reads straight back: it already carries the owner, data class and policy state columns. It carries no column for the use policy itself or for why we have it, so those two pages need a file of your own.

Columns you leave out are left alone. You can send a file of nothing but Policy state, and it adopts those policies without touching a word of what they say. The same goes for half an owner: a file with only Business owner email moves the address on every line it names and leaves each name as it was. It is the same rule the Set ticked tools bar follows, because it is the same job: one answer applied to tools you are not looking at one by one.

Lines are matched to the tools on the page by name, the same way the Add tool box matches what you type, so a line saying “Microsoft 365” finds the row you hold as M365. A line is named and left alone when no tool on the page answers to it, when more than one does, when a value is not one of the answers, or when Flow cannot read it, such as an owner cell that is not an email address. Flow does not guess which row or which answer you meant.

A tool named on more than one line is left alone entirely, and the message gives you the line numbers. It holds whatever the two lines say, and it holds when they say the same thing: a file that names one tool twice has not said which line wins, and Flow would rather you tell it than pick.

A blank cell changes nothing either. The tool keeps the answer it has. Nothing in a file can empty an answer: the control on the page is what clears one.

This import does overwrite. A tool that already has an answer for this field takes the one in your file, and the preview shows both, what each tool says now and what it would say, with a count of how many answers are being replaced. Lines that already say what the tool says are listed as changing nothing and are not written. The tool import works the other way and leaves a tool you already have alone. The difference is what the file is for: there it proposes a new row, here it answers a question you went looking for.

Record teams

The same Edit form holds one more thing:

• Teams: tick every team that uses the tool.

Select Save. Anything you leave blank stays blank.

A policy left as Being written reads that way in the table and still counts as missing, so To do keeps asking for it. Set Policy state to In force when it is agreed, or select Put in force on the tool’s page. Only a policy in force is one an employee can be held to.

How Flow knows a tool is AI

The AI column on All tools and the AI features row on a tool’s page say one of three things:

• AI tool: the product itself is AI, like Claude or Cursor.
• Add-on: a regular tool with an AI feature inside, like Notion AI or GitHub Copilot.
• None: no AI in the product.

Hover over a tag to read its definition. The AI heading opens the definitions of both when you hover over it or select it.

Velory sets this in its tool catalog from the vendor’s own pages, so the tool’s Edit form has no box for it. Until Velory has checked a tool, the tag shows any answer the tool already had and says Not verified, with a link to the vendor page it came from when there is one. Once Velory has checked it, Velory’s answer replaces it on every screen. A tool with no answer at all reads Not checked.

The check asks people which AI tools they use, and it offers your own list rather than a generic one. A tool on your list is offered when it reads AI tool or Add-on, or when Velory has verified that it has AI features. A tool Velory has checked and found no AI in is not offered, whatever it said before. Nothing else puts a tool in front of your people, and no model gets a say in it.

The check offers at most twenty tools. If nothing on your list qualifies, people see Flow’s standard list of tools instead.

Link the policy rules that apply

Only a company admin can link or unlink a rule. A manager sees the list.

A tool’s page lists the rules from your approved AI policy that cover it. Each rule shows the document it came from and its topic, and one of two lines:

• Asked in Round 2 means the newest round that asked people about that rule. A round asks about the rules that were ticked on Policy when it was first sent.
• Not asked yet means no round has asked about it. A rule you reworded after a round went out counts as not asked, because nobody was asked the new wording.

To link a rule, open the tool. Under Policy rules that apply, rules tagged Suggested are ones whose words match the tool: a rule that names the tool, a rule about AI tools when this is one, a rule about where data is kept when the tool keeps it outside the EU (checked by Velory, or found on the tool’s own website and marked as not checked by Velory), or a rule that mentions the kind of work the tool does. Each suggestion says why it was matched. Select Link to accept one; a suggestion is not linked until you do. To link any other rule, search for it in the box at the bottom of the card, pick it, and select Link.

Select Unlink to take a rule off the tool. If you remove a rule from your approved list on Policy, it comes off every tool when you save. A rule that comes from this tool’s own use policy has no Unlink. It shows From this tool’s use policy instead, which opens the policy for editing: change the words there to change which rules apply.

Only approved rules can be linked. If your company has not approved any yet, the section sends you to Policy.

Mark a tool as reviewed

Some tools are never worth reviewing again. A password manager everybody needs is one.

Open the tool, open the ··· menu at the top and select Mark reviewed. The tool’s page then reads Reviewed beside its name. It stays in All tools, marked Reviewed, and the Reviewed filter lists or hides the reviewed ones. It drops out of To check, and the registry bars still count it, because the registry is about every tool you have. Unmark reviewed reverses it.

Where “AI features” and “EU residency” come from

The From the Velory catalog section on a tool’s page comes from Velory’s own record of the tool. Nothing in your spreadsheet can set it. It has five rows: AI features, EU residency, DPA, Sub-processors and Trust center.

Velory records a fact only with a link to the vendor’s own site. Each row shows the fact, that link and the date somebody checked it. The DPA, Sub-processors and Trust center rows are links to the vendor’s own pages; Velory does not record a date for those, so they read No date recorded. They show only once Velory has checked AI features or EU residency for the tool. A row with no link on the vendor’s site reads Not found.

A tool Velory has not described shows From the vendor’s site instead, when Flow read the tool’s own website as it was added or asked for. Each row there shows what that website said, with the page and the date it was read, and says Not checked by Velory. A row the website did not answer reads Not found. Once Velory checks a fact, Velory’s answer replaces it. A tool whose website nobody read shows no facts at all.

Filter and export

The filter bar narrows All tools by owner (for admins), by policy rule (any rule linked, no rule linked, AI tools with no rule, or one rule), by how much AI is in a tool, by data class, by whether a tool is reviewed, and by Missing, which lists the rows with a registry field still to fill in. There is a text box for the name. The table shows fifteen rows to a page, in name order.

Export CSV downloads the whole filtered list, not just the page you are reading, with the filters you set.

The export’s data region column holds only what Velory verified. A region found on the tool’s own website is left empty there.

Retiring a tool

Open the tool, open the ··· menu at the top and select Retire. It drops out of the list and stops being offered in the check. The row stays, so an answer that named it still makes sense. Put back reverses it.

What this page does not do

• It does not hold cost, seats or renewals. Keep those in your finance and licence tools.
• It does not measure usage, and it does not touch the tool. Flow never signs in to a vendor and never changes anyone’s access.
• A person can see, on their own Write-ups page, the tools you list them as owning, because a company admin can see the same thing about them.
• Erasing a person takes their address and name off every tool they own. The tool stays, because it is your record. It then reads as a tool with no owner on the business owner bar under To do.