---
"@type": WebPage
"@id": "https://helloloam.dev/solutions/work-on-it-together"
"@source": "https://helloloam.dev/data/webpage/work-on-it-together.json"
"@stamp": "2026-10-22T21:53:55+00:00"
about:  # 3
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/fine-grained-permissions.json"
    name: Fine-grained permissions
    identifier: fine-grained-permissions
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/mechanics.json"
      name: Mechanics
      identifier: mechanics
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/draft-and-live-lifecycle.json"
    name: Draft and live lifecycle
    identifier: draft-and-live-lifecycle
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/mechanics.json"
      name: Mechanics
      identifier: mechanics
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/backups-as-a-snapshot.json"
    name: Backups as a snapshot
    identifier: backups-as-a-snapshot
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/mechanics.json"
      name: Mechanics
      identifier: mechanics
description: Everyone gets a key of their own, with the rights it needs. A colleague writes, you publish — and every change says who made it.
headline: Work on it together
identifier: work-on-it-together
image:
  "@type": ImageObject
  contentUrl: /assets/images/work-on-it-together.jpg
  caption: Six colleagues around one table, each on their own laptop, working on the same figures.
inLanguage: en
name: Work on it together
url: "https://helloloam.dev/solutions/work-on-it-together"
---

# Work on it together

## The worry

Letting someone else into your website feels risky. One shared login, and anyone can change anything — or remove it. So the work stays with one person, and everyone else sends emails.

## What happens instead

On a loam site, access is a key, not an account. Everyone who works on the site gets [a key of their own](/principles/fine-grained-permissions), with exactly the rights it needs. Sarah may write the news but not publish it: her changes [wait as drafts](/principles/draft-and-live-lifecycle) until you say so. Nothing reaches a visitor before it is approved.

## Who did what

Every change lands in [the site's journal](/principles/mcp-with-a-trust-model): what was done, by which key, and what was asked. “What changed this week?” is a question your agent answers. When someone leaves, you take back their key — nothing else needs cleaning up.

## In practice

- A copywriter writes, the owner publishes.
- A design agency changes the design, never the content.
- An auditor reads everything and changes nothing.

## What it costs

You decide every key — and the right to change the design goes only to people you fully trust, because the design is code. Drafts are shared, not private: someone who may publish can publish your draft. And a key is only as safe as the account behind the agent that holds it.