Rules for apps
What a team's app needs before it is shared with several teams or the whole organisation: a repository, green CI, tests, monitoring, who publishes, and your own rules for every app. Report only for the first two weeks, then enforced.
A small app for yourself should take a minute. An app the whole organisation relies on deserves real engineering. Your workspace’s rules for apps decide what an app needs before it reaches a wider audience, and I hold every app to them.
Rules per audience
The wider an app is shared, the more it needs. These are the rules every workspace starts with:
| Rule | Just me | My team | Several teams | Whole org |
|---|---|---|---|---|
| Real repository | No, I keep the versions | No | Required | Required |
| CI | None | None | Lint and tests green | Lint and tests green, plus your workspace’s reference checks |
| Automated tests | None | None | At least one | One for every data change |
| Monitoring | None | Health check | Health check and alerts to the owning team | Health check, uptime, alerts and a named owner |
| Who publishes | Anyone who may change it | Anyone who may change it | A lead of the owning team | A workspace admin |
| Staging first | Optional | Optional | Required | Required |
| Design and rules | Applied, findings shown | Applied, findings shown | Enforced | Enforced |
| If something is missing | Report only | Report only | Hold it back | Hold it back |
- Sharing with people by name counts as several teams.
- Reference checks are CI jobs by name (for example
sast,licences), or the jobs a reference repository you name passes. They must be green on the app repository’s main branch before an app goes organisation-wide. Set the reference repository under the rules in Workspace settings > Apps; it may live on another code host than your apps, and with more than one code host connected you choose which. If I can’t read it, the rule says why. - Staging first means a new version runs on the app’s staging copy before you make it live. Where it is optional, an app’s owner can turn it on.
- Teams can only add to these rules. A team’s own rules can ask for more, never less.
When you share an app wider and something is missing, I tell you in your chat, in plain words, what it still needs, for example “Green CI on lint, tests” or “A lead of the team publishes it”. Ask me and I take care of what I can: I move the app into a repository, add tests from your sentences and set up its monitoring. If your team has app repositories turned off, I say so instead of turning them on; a lead turns them on under Team settings > Repositories.
The first two weeks
The rules start in report only in every workspace, for two weeks from the first time an app is shared. During that time I share the app anyway and tell you what it will need once the rules hold. After two weeks, the audiences set to Hold it back are enforced: an app that misses something stays where it was until it is ready. Workspace settings show which phase you are in.
Rules for every app
Add your own rules in plain words, for example “every page shows our logo in the header”, “tables use our status colours” or “no internal abbreviations in labels”. Each rule is about style, structure or wording, and is either a Must or shown as a hint.
- I build every app by your rules from the first version.
- After each version, a reviewer that did not build it checks the version against every rule. What it finds shows on the app as a finding.
- A Must rule holds an app back where Design and rules is enforced. Elsewhere it shows as a finding, so the team can fix it before sharing wider.
Change the rules
The quickest way is to tell me in the chat: “apps for the whole organisation need two tests”, “make sharing with several teams report only” or “every app uses our logo”. I show you what changes and a workspace admin applies it with one tap. Every change is a new version, recorded in the audit log, and can be undone.
You can also review and edit the rules under Workspace settings > Apps. Everyone in the workspace can read them; owners and admins edit them.
Sharing with people by name
Besides teams, you can share an app with people by name under Share > Chosen teams or people. Only people in your workspace can be named, and each sharing can end on its own after 30 or 90 days. They open the published version with their own rights and hear about it in their chat.
Related
Last updated: January 1, 0001
Open kanman