Share apps and the app catalogue
Mine, Team and Shared: who sees an app, who changes it, and how other teams find it in the workspace's app catalogue and the Apps tab, with each viewer seeing data with their own rights.
Who sees an app
Every app has one of three levels. You see it in the app’s title bar (for example Team ▾) and change it there, in the app’s settings or by asking me.
| Level | Mine | Team | Shared |
|---|---|---|---|
| For | Mockups, previews, personal helpers | Team dashboards and tools | Tools for other teams or the whole organisation |
| Who sees it | Only you, plus people you invite by link for a limited time | Everyone in the team’s workspace | The teams or people it is published to, listed in the app catalogue |
| Which version | The live draft | The live version | A published version; the team works on the next one without disturbing anyone |
| Chat beside it | Your own | The team’s | Each viewer’s own chat with kanman |
| Who changes it | You ask, I change | Anyone on the team, in the team chat | Only the owning team; others send requests |
A new app starts as Mine. Moving it up is one step, and I check it again each time. I also tell you what changes for the new viewers, for example “2 data sources they may not read show as empty for them”. Where your team’s risk tiers ask for it, sharing needs a lead’s OK first.
Each viewer’s own rights
Data from your connections always shows with the rights of the person looking, never the owner’s. Someone who may not read a source sees it empty, with a note why. The app’s own data store is the app’s data: everyone who sees the app sees it.
Two exceptions you decide on explicitly when sharing: showing your team’s own numbers to others, and an app that calls a service with its own login (then everyone who sees the app sees that data). I name both in the check before the app moves up.
The owning team’s chat is never shared. Someone from another team asks me about the app in their own chat, and requests for changes (Ask the owners for a change) reach the owners bundled into their next brief.
The app catalogue
Every app set to Shared appears in the workspace’s app catalogue: Apps in the workspace navigation, at app.kanman.ai/<workspace>/apps. It answers a simple question: is there already a tool for this, and which team made it?
- Search by what you need, not by name: “check whether a connector is live”, “who is on call”, “open incidents by service”. I search by meaning across what apps do and the data they read. When nothing fits, I offer to build it for your team.
- Featured shows apps picked for you, rising this week and new. Categories: dashboards, tools, forms, reports, previews and mockups.
- One list, one card everywhere: the catalogue and every team’s Apps tab show apps the same way. A filter switches between My teams (or This team in a team’s tab) and All teams I can see.
- Each card tells you what you need to choose: a small preview with the app’s name and the data it reads, an icon that says what it works with (a tracker, metrics, pipelines and releases, incidents, docs or a connection), whether it is running, the team or person who made it, how many people used it in the last 30 days (“Used by 4 people”) and when someone last opened it (“Opened 2 days ago”). The preview never shows the app’s data: who may see that is decided for each viewer.
- One page per app: a card opens the app’s page in its team’s Apps tab, whichever team you are in. There you see the live app with your own rights, and someone from another team can Ask the owners for a change, which reaches them in their next brief. Older catalogue links open the same page.
You can also simply ask in the chat: “is there an app that shows our on-call rota?” I answer with the right app, whichever team made it.
App links
Every app has a link of its own that opens only the app, with a thin kanman bar for people who just use it:
https://app.kanman.ai/a/<workspace>/<team>/<app>/
The link keeps the app’s own routes and filters: copy it with the link button in the app’s title bar while you look at a filtered view, and whoever opens it lands on the same view. The bar has Ask the owner, Open in kanman and can be hidden.
Someone without access sees why (the app is not shared with them, its team is closed to them, or it belongs to another workspace) and can ask the owner for access in one step.
Where IT has set it up, people on your company network open apps directly from your runners at your own address: Let people reach apps directly.
Related
Last updated: January 1, 0001
Open kanman