Skip to main content

Edit Tool After Creation

I created a tool and noticed that the weblink did not properly render the image. I decided to create the app and upload an image later, only to find it's not possible. It would be beneficial to have the ability to edit a tool's name, logo, or image directly in the app after creation, rather than having to contact support for such changes.

Status: Open3 comments

Log in to comment and vote

Comments3

  • Jason Alexander

    โ€ข

    Dec 21, 2025

    I feel the lack of being able to edit or delete is due to lack of foresight in development and planning for implementation as appose to security. What is the difference between someone being able to add a bunch of random fake/junk tools and modifying what is there? It seems like the tool just has ONE pool of "tools" across everyone's tenant as appose to proper segmentation of a tenant in a SaaS application. What if a company has internal proprietary or IP "Tools"? When you create a "Tool" all users of the platform regardless of tenant can see it, that is far more of a security risk if you ask me. I don't see how the product can scale waiting on support to update the tool. And what if someone feels that the picture is not how they want it and asks support to update the picture now the original person is not happy with the picture? What if you're working on a document late at night for a presentation and no one is available to update it?

    • Brian

      Teamโ€ข

      Dec 21, 2025

      Jason Alexander โ€” appreciate you raising these points. I want to clarify one important distinction that guided this design decision and provide more context around the security model.

      The difference between a user adding a bunch of new/fake tools versus editing existing tools is the following:

      ๐€๐๐๐ข๐ง๐  ๐ง๐ž๐ฐ ๐Ÿ๐š๐ค๐ž ๐ญ๐จ๐จ๐ฅ๐ฌ โ€” If a bad actor added fake tools, it wouldnโ€™t impact any existing diagrams, because when a new or random tool is added, none of the user base would have that tool assigned to any of their steps yet. This keeps the blast radius very small. When our team reviews newly added tools, we can spot fake or junk entries and remove them from the tool directory with little to no downstream impact on existing diagrams.

      ๐„๐๐ข๐ญ๐ข๐ง๐  ๐š๐ง๐ฒ / ๐š๐ฅ๐ฅ ๐ญ๐จ๐จ๐ฅ๐ฌ โ€” By contrast, if users could edit existing tools, a bad actor could modify tools that are already widely referenced, immediately impacting diagrams across the system. That creates a much larger, cascading impact surface.

      This was an intentional design decision based on minimizing system-wide impact and protecting shared artifacts. For this specific area of the product, we chose to prioritize reducing blast radius and maintaining integrity of existing diagrams over in-app convenience.

      Regarding Private Tools โ€” we do have an active feature request for this, and itโ€™s currently planned to launch prior to EOH1 2026.

      While the Private Tool feature lives in a similar area of the product as adding new tools, it introduces additional considerations that are distinct from editing the shared tool directory. To keep this discussion focused and avoid conflating the two, Iโ€™d be happy to dive deeper into Private Tools and answer your questions directly in that feature request: https://feedback.puzzleapp.io/feature-requests/p/mark-a-new-tool-as-private

      Regarding logo preferences โ€” each software tool has a primary, canonical logo. We rely on the community to add the toolโ€™s primary logo when submitting it, and if itโ€™s incorrect or outdated, our team can update it within 24 hours of a request. Because this is a shared directory, updates are based on correctness rather than individual preference.

  • Brian

    Teamโ€ข

    Dec 20, 2025

    Hey everyone, appreciate your contribution here unfortunately users are not allowed to edit the tool database after adding a new tool to the community-wide directory.

    Our support team responds promptly to update the Tool directory within minutes to fix the tools if they are accidentally saved with broken images.

    There is a very important reason it is built this way: ๐ฌ๐ž๐œ๐ฎ๐ซ๐ข๐ญ๐ฒ. One of the most valuable components of our platform is our community-built tool directory โ€” where users can sign up and ๐ข๐ง๐ฌ๐ญ๐š๐ง๐ญ๐ฅ๐ฒ ๐š๐ฌ๐ฌ๐จ๐œ๐ข๐š๐ญ๐ž ๐จ๐ฏ๐ž๐ซ ๐Ÿ’,๐ŸŽ๐ŸŽ๐ŸŽ+ ๐ญ๐จ๐จ๐ฅ๐ฌ ๐ญ๐จ ๐ญ๐ก๐ž๐ข๐ซ ๐ฐ๐จ๐ซ๐ค๐Ÿ๐ฅ๐จ๐ฐ๐ฌ to indicate what technology is used across their processes.

    We allow users to add new tools to contribute to the growth of the Tool directory, but not edit them after, because if users could edit information on our tool directory it takes one bad actor to programmatically edit the entire tool directory to negatively impact everyone's diagrams.

    For this specific feature, ๐ฐ๐ž ๐œ๐ก๐จ๐จ๐ฌ๐ž ๐ฌ๐ž๐œ๐ฎ๐ซ๐ข๐ญ๐ฒ ๐จ๐ฏ๐ž๐ซ ๐œ๐จ๐ง๐ฏ๐ž๐ง๐ข๐ž๐ง๐œ๐ž. Just as any other product may make 2FA a requirement to protect important data (a tad inconvenient, but you do it for security), we decided to do so for editing the Tool directory.