Curate your department's memory

Give one team its own shared context. What managers edit directly, what members propose, and how company policy overrides a department page.

Department memory is for the things true of one team and not of the whole workspace: what it owns, how it runs its week, which tools it standardises on.

Open Memory and pick the tab named after your department. Where that tab sends you depends on what you hold.

Who can do what

You are	What you get
A member of the department	Read everything approved, and propose changes
A manager of that department	Direct editing, plus the review queue for that department
An admin or the owner	Direct editing and review for any active department

A manager seat is a grant on top of your normal role. A plain member who manages their own department gets the curator view, not the propose only one.

Curate a department page

Open the department tab.
Click Add to memory, then Write a memory.
Pick the type: fact, decision or SOP.
Save. Your text is stored as approved knowledge for that department.

To change something, open the section and click Edit page. To retire a page, archive it. Every accepted change writes a new version and the old one stays in history.

A five person revenue team keeps losing track of inbound leads. Their manager adds an SOP: "Every inbound lead is logged in HubSpot within one working day, owner assigned before end of day." A rep who then asks their Talent to draft a follow up gets the ownership step included, and a Routine that summarises the week can be written against the same rule rather than someone's memory of it.

Propose as a member

Members use the same Add to memory button, and the confirm step says Propose. You can propose an add, a change, an archive or a restore. You never see the pending queue or who proposed what. You are told when your proposal is decided.

Review proposals

Managers of the department, admins and the owner see a Review section on the department page.

Open a proposal. It names the action, the page it targets, the current text, and whether the target is still current.
Fix the wording and the type if needed.
Approve revision or Reject.

A Stale target badge means the page changed after the proposal was written. Read the current version before approving. A Safety blocked badge means the text tripped the credential filter and cannot be approved as written.

The sections you are writing into

Overview and mandate, Priorities, People and ownership, How we work, Tools and standards, and Challenges and dependencies once it has content.

Company memory wins on conflict. A department page can add detail to a company rule, sharpen it or say how your team applies it. It cannot override it. If a company page is wrong, fix it there instead of writing a contradicting department page.

Members read the memory of their current active department only, and that scope updates the moment someone moves them. There is no way to read another department's memory as a plain member, and an archived department stops serving pages entirely.

What to check

No department tab. You are not assigned to an active department. An admin fixes that from Team.
You see Propose but you manage this team. Your manager seat is on a different department, or it was not assigned. Ask an admin to check your seat under Team.
A teammate cannot see a page you just wrote. Confirm they are in the same department, and that you saved to the department tab rather than to You.
A page vanished after a reorganisation. The department was archived, or you were moved. Ask an admin which department now owns that knowledge, and move it to the company space if it applies to everyone.