لم تُترجم هذه الصفحة بعد.

A confidential HR policy

This example is for an HR lead, and the admin who helps them, in an organization on instruction.md. You will keep an HR policy in a workspace that only HR can see, sealed so that only the people you give its key to can read it. instruction.md stores it and delivers it, but can't read it.

The situation

HR writes the rules an assistant uses to answer employees' questions about leave. Some of these rules are confidential: how cases are handled, what is paid and when. Nobody outside HR may read them. That includes the rest of the company, and it includes instruction.md, the company that stores them.

Two settings of a workspace do this together:

  • Restricted: only the people added to the workspace see it, and the organization's owners and admins.
  • Sealed: its instructions are encrypted on its people's devices before they reach instruction.md. Only someone with the workspace's key can open them. Owners and admins see that the instructions exist, but they can't read them without the key either.

What you'll make

  • A workspace called HR, restricted to the HR team and sealed.
  • An encryption key for each HR member, given the workspace's key.
  • A short leave policy, written and published inside the workspace.
  • A note for IT about how agents can read it.
A restricted, sealed HR workspace in Settings, Workspaces.

What you need

  • A plan with sealed workspaces:

    Plans On Team and Enterprise

  • The right role. Only the organization's owners and admins can make, restrict and seal a workspace. See People and roles.

  • A new, empty workspace. Only an empty workspace can be sealed. An existing instruction can't be moved into a sealed workspace yet, so you write the policy again there.

  • A passkey, a security key or a passphrase for each HR member, to unlock their encryption key.

Steps

  1. Make the workspace

    Open Settings ▸ Workspaces. Under Add a workspace, type HR in Workspace name and choose Create. A new workspace is open to every member until you restrict it.

  2. Restrict it

    In the HR section, turn on Restricted. The line under it says Only the people added to it see it, and the organization's owners and admins.

  3. Add the HR team

    Next to People, choose Show. Under Add someone, pick a person in Who, a role in Role, and choose Add. Repeat for each HR member. A Maintainer can change and publish, a Reader can only read. See People and roles.

  4. Set up your own encryption key

    Open Your account ▸ Security. Under Encryption key, choose Set up. Pick how you unlock it: Use a passkey, Use a security key or Use a passphrase. Then the editor shows your recovery key, once. Keep it somewhere safe, tick I saved my recovery key, and choose Finish. The editor says Your encryption key is ready.

    Your key is made in your browser. instruction.md only keeps copies of it that are locked by your passkey, security key, passphrase or recovery key.

  5. Seal the workspace

    Back in Settings ▸ Workspaces, in the HR section, choose Seal workspace next to Seal this workspace. Unlock your key if you are asked. The editor asks Seal HR?. Choose Seal workspace. A sealed workspace can't be unsealed.

    The section now shows Workspace key, marked Sealed, with how many people have the key.

  6. Give the key to each HR member

    Each HR member sets up their own key, as in the step above. They then show as waiting, for example 2 people waiting for the key, each with a fingerprint: a short code that belongs to their key.

    Ask each person to read you the fingerprint they see under Encryption key on their own Your account ▸ Security page, for example on a call. If it matches, choose Give the key, check the fingerprint again, and confirm. They can now open the workspace's sealed instructions.

    Anyone who already has the key can give it. People who haven't set up a key yet are listed too, for example 1 person hasn't set up a key.

  7. Write and publish the policy

    Switch to the HR workspace and choose New instruction. Write the policy, for example:

    Leave policy
    ---
    spec: "1"
    title: Leave policy
    ---
    
    # Leave policy
    
    You answer Acme employees' questions about time off: holidays, sick leave and parental leave.
    
    MUST: answer from this policy only, and say so when a question is outside it.
    
    MUST: pass every question about one person's own case to :role[HR]{ref=#hr}.
    BECAUSE: a case can hold health or family details that only HR may see.
    
    NEVER: tell one employee about another employee's leave.
    
    ## Holidays
    
    Full-time employees get 25 working days of paid holiday a year, plus public holidays.
    Up to 5 unused days carry over to the next year, until 31 March.
    
    ## Sick leave
    
    An employee tells their manager on the first day.
    From the fourth day in a row, they send a doctor's note to HR.
    
    ::role{id=hr title="HR team"}

    The instruction shows Sealed beside its name. Choose Publish… and publish version 1. See Publish a version.

    Restricting the workspace doesn't hide an instruction you share with Your organization: every member can then find it, whichever workspace holds it. Being sealed, its text still opens only with the key.

Check it worked

  • In Settings ▸ Workspaces, the HR section shows Workspace key, Sealed, and the number of people who have it.
  • An HR member opens the policy and reads it, after unlocking their key.
  • Someone without the key who opens its address sees This instruction is sealed, and can't read the text.

Your key stays unlocked in your browser tab, and locks after 30 minutes away, or when you close the tab. To lock it now, open the command palette and choose Lock encryption key.

Agents reading the policy (hand this to IT)

An AI app connected straight to instruction.md only gets the sealed, unreadable text. To read the policy, an app needs the workspace's key, one way or another. Each way is set up by someone technical:

  • An agent with its own key. This is the way for the assistant that answers employees. The agent, such as a bot or a server process, gets a key of its own, kept in a file only it can read. Add the agent to the HR workspace first, as a Reader. Then someone who has the key gives it the key, the same way as for a person, after comparing its fingerprint.
  • The company's own connection point. IT runs a small program at your company's own address, such as mcp.acme.com, and gives it the workspace's key. People connect their AI apps to that address instead, and sign in with instruction.md as before. instruction.md still decides, for each person, what they may read. The program opens only what that person may read, so HR members need no key of their own in their AI apps. Employees outside HR still can't read the policy this way.
  • A person's own key. An HR member can also connect their AI app with their own encryption key.

Send IT the page for developers: Sealed instructions for developers. It explains each way, step by step.

When someone leaves HR

  1. Remove them from the workspace

    In Settings ▸ Workspaces, open the HR section's people with Show, and choose Remove next to the person.

  2. Rotate the key

    Choose Rotate key and confirm. New versions are sealed with a new key that the person who left never had. Only owners and admins can rotate, and only if they hold the key.

Rotating protects what comes after. Whatever the person read before, they may have kept.

What you give up

A sealed workspace keeps instruction.md out of the text. So everything that only instruction.md's servers can do with the text doesn't work there:

  • The assistant can't read sealed instructions or sealed agent conversations, because it runs on our servers.
  • Search inside the text, server checks, public pages and read links don't work.
  • One person edits a draft at a time. If two people save the same sealed draft, the editor says Someone else saved this sealed instruction while you were editing. Your next change replaces theirs.
  • No publishing later. A sealed instruction can't be scheduled to publish later yet. Publish it now instead.
  • No moving in. Existing instructions can't be moved into a sealed workspace yet.
  • A lost key is gone. If you lose every way to unlock your key and your recovery key, nobody at instruction.md can get back what only you could open.

What instruction.md still sees: each instruction's name and title, who reads and changes it and when, how many versions it has, roughly how long each one is, and which agents follow it. See What instruction.md still sees.

The AI model that follows the policy reads it. That is the point. Choose your model provider with that in mind.

If it doesn't work

What you see Why What to do
Sealed workspaces are on Team and Enterprise. next to Seal this workspace Your plan doesn't include them. See which plans include them, and who can change yours, in Plans and billing.
It has 3 instructions. Only an empty workspace can be sealed. The workspace already holds instructions. Make a new workspace and seal it before you write in it.
You don't have this workspace's key yet. You set up your key, but nobody has given you the workspace's key. Ask someone in HR who has it to choose Give the key for you.
This instruction is sealed with Set up your encryption key, then someone who has this workspace's key gives it to you. You have no encryption key yet. Set one up in Your account ▸ Security, then ask for the workspace's key.
That didn't unlock your key. Check what you entered and try again. The passphrase or recovery key was wrong. Try again, or choose Lost your passkeys? Use your recovery key.
Still stuck Something isn't working, or ask us.

Questions

Can instruction.md read a sealed HR policy?

No. It is encrypted on your people's devices before it reaches instruction.md, and only someone with the workspace's key can open it. instruction.md still sees its name, who changes it and when, and which agents follow it. See What you give up.

Can the organization's owners and admins read it?

They see the restricted workspace and its instructions' names. They can read the text only if someone gives them the workspace's key.

How does an AI app read a sealed instruction?

As an agent with a key of its own, added to the workspace. HR members' own AI apps can also go through your company's own connection point, which holds the workspace's key. IT sets this up. See Agents reading the policy.

What if I lose my encryption key?

Unlock it another way, or with your recovery key. If you lose every way and the recovery key, what only you could open is gone. Add a second way to unlock with Add another way to unlock.

Can I seal a workspace I already use?

Not yet. Only an empty workspace can be sealed, and instructions can't be moved into one yet. Make a new workspace and write the policy there.

Last checked against the product:

Was this page helpful? Report a problem