Skip to content
Decide who may open what, across companies and branches · presentation 1 of 5 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Decide who may open what, across companies and branches · presentation 1 of 5

Installing an applet is a door, not a fence

You can explain what an applet install actually grants, what it cannot restrict…

What decides what appears

Step 1 — Follow the chain that ends at a launchpad tile

You will know where to look when somebody signs in to nothing.

Screen capture pending the demo tenant

The platform launchpad with no tiles on it

Step 2 — Know what that row really buys you

You will be able to say what uninstalling achieves.

Where this step sits
    flowchart TD
  s1["1. Follow the chain that ends at…"]
  s2["2. Know what that row really buys…"]
  s3["3. Know what it does not buy…"]
  s4["4. Watch an invitation admit somebody to…"]
  s5["5. Understand why 'install everything' is a…"]
  s6["6. Put the boundary where the boundary…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Where the fence stops

Step 3 — Know what it does not buy you

You will stop using the applet list as a security boundary.

What this step names
  1. Every server-side permission code is named for the thing it protects —…
  2. A document
  3. An export —
  4. None of them names an applet

Step 4 — Watch an invitation admit somebody to a second tenant

You will check a catalogue before you use it in an invitation.

  • Open the catalogue, read the tenant on each row…
Screen capture pending the demo tenant

The employee Login tab, with the invitation options and the catalogue picker

Step 5 — Understand why "install everything" is a fair option

You will make the right call on the invitation toggle.

What you do
  1. Read as *install everything*, it sounds reckless
  2. Read accurately, it is bounded: it refuses to run at all unless you have…

What to do instead

Step 6 — Put the boundary where the boundary is

You will have a defensible shape.

Where this step sits
    flowchart TD
  s1["1. Follow the chain that ends at…"]
  s2["2. Know what that row really buys…"]
  s3["3. Know what it does not buy…"]
  s4["4. Watch an invitation admit somebody to…"]
  s5["5. Understand why 'install everything' is a…"]
  s6["6. Put the boundary where the boundary…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;

NarrationSlide 1 of 10

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.