Skip to content
KoshKramaniti

Tool setup guideFree templateAdded 29 Aug 2026

Check a new app before you connect it

See what a new app can access, what could go wrong and who looks after it before you connect it.

Use it when A new app or plugin looks useful, but what it can access, how it could fail and who looks after it are not yet clear.

Download template

It is a simple text file. Open it in any text editor, or paste it into ChatGPT, Claude or Gemini and ask for help filling it in.

How to use it

  1. Use this as an evaluation document. It is a guide, not an installable plugin.
  2. Read the provider’s current permission and data documentation. Mark anything you cannot confirm as unknown.
  3. Ask the owner to approve a bounded test only after the required evidence is available. Record how to revoke access.
What you will need before you start
  • The specific plugin and current documentation
  • Requested permissions and intended data
  • An owner who can approve and revoke access

The template

Fill in the blanks for your business. This is what you get when you download or copy it.

Before connecting a plugin

  1. State the exact workflow outcome it should improve.
  2. List every permission it requests and every system it can reach.
  3. Identify the least-privileged setup that still proves usefulness.
  4. Record what happens when the plugin fails, returns poor data, or takes an unintended action.
  5. Name the person who can approve, disable, or remove the connection.

Decision record

  • Plugin and version
  • Intended use
  • Permissions granted
  • Data boundary
  • Failure path
  • Owner
  • Approval date and review date

Do not connect a plugin merely because it is available. A useful connection has a clear job, a bounded permission set, and a reversible path.

See an example

A made-up example, so you can see what a filled-in version looks like.

This is an illustrative scenario, not a client case study or a measured result. Do not reuse its details as facts about your work.

A team considers a document-search connection for approved reference notes.

Sample inputs

Demonstration inputs only: the desired job is searching one reference folder. The hypothetical connector requests access to all documents. Its retention policy has not been supplied.

Example output

Intended use

Search approved reference notes in one folder.

Permission inventory

[Fact within this demonstration] The hypothetical request covers all documents. [Inference] The requested scope is broader than the stated job.

Data boundary

Only the approved reference folder is in scope. Private client documents are excluded.

Unknowns

Can access be restricted by folder? What data is retained? How is access revoked?

Decision

Hold the connection. Ask the provider for scoping and retention details.

Owner and failure path

[Name the administrator] reviews the evidence and records a revoke procedure before any test. Approval: pending.

How to tell it is done well

Every permission has a reason; unknown retention or access behaviour stays visible; a named owner can disable the connection.

Where a person should decide

Permissions and provider behaviour change. Recheck current documentation before connecting; no plugin compatibility is implied. Keep consequential actions with the named human owner.

Permissions and provider behaviour change. Recheck current documentation before connecting; no plugin compatibility is implied.

Edit your own copy on this site
About this version

Version 1.1 adds setup guidance, an illustrative example and a review checklist. Provider-neutral Markdown instructions; no installation or platform compatibility is implied. Runtime behaviour has not been verified across AI providers. Reuse terms have not yet been published.

How we write Kosh templates