Manage workspace settings

Manage workspace settings in Slack — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need the workspace settings aligned with Platform team's compliance checklist. Update the message…
I need the workspace settings aligned with Platform team's compliance checklist. Update the message retention policy to 90 days, enforce two-factor authentication for everyone, and restrict file uploads to the engineering and product channels only. After you apply changes, generate a short summary for the Platform lead and schedule a notice to go to all staff on Monday morning.

Improve — make it easier to accept

+
Before I change workspace settings, make the decision easy for the compliance reviewer. Put a…
Before I change workspace settings, make the decision easy for the compliance reviewer. Put a one-sentence justification up top: why 90-day retention and enforced 2FA. Make the exact settings findable, show who will be affected by channel restrictions, and flag any user groups or bots that will need exemptions or migration steps.

Decide — diagnose the stuck moment

+
I opened the security settings and stalled because enabling enforced two-factor will lock out…

I opened the security settings and stalled.

I opened the security settings and stalled because enabling enforced two-factor will lock out contractors who use a shared corporate SSO and I don't know how many there are. I am afraid of breaking builds or support rotations. What is the most likely impact, what should I check first, and what is the safest rollout plan?

Become — change the pattern

+
We keep toggling security and retention settings ad hoc and then scramble to re-enable access or…

We keep changing settings without migration plans.

We keep toggling security and retention settings ad hoc and then scramble to re-enable access or migrate bots. This wastes Platform time and annoys Product. What operational habit and short checklist will let us change workspace-wide security settings without back-and-forth support tickets? Who should own the migration plan?

Next to this one

Other team chat work people do in Slack.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.