Set your organization's rules
This page is for the owners and admins of an organization. You will set the rules that apply to everyone in it: who can read a new instruction, what new members and agents may do, which tools instructions may use, and whether the assistant is on.
Before you start
- Who can do this: the organization's owners and admins. Other people don't see these rules.
- Where: most rules are in Settings ▸ Security. A few are elsewhere, and each section below says where.
- What you need: nothing else. Each rule saves as soon as you change it, and a short message says what changed.
The rules belong to the organization, so they apply in every one of its workspaces. Your personal organization has the same rules, for your own instructions.
Who can read new instructions
In Settings ▸ Security ▸ Defaults, the row Who can read new instructions sets who can read a new instruction's versions until someone shares it. Choose one:
- Private: only the people who have a role on it, in its workspace or on the instruction itself. This is where every organization starts.
- Organization: everyone in the organization.
- Public: everyone, signed in or not.
A message says "Default visibility changed". Instructions that exist already keep who can read them. To change one, see Share an instruction.
What new members can do
The row What new members can do sets the role a new member gets on the default workspace's instructions, when their invitation doesn't say. Choose one:
- Read: a Reader. This is where every organization starts.
- Suggest: a Contributor, who proposes changes.
- Publish: a Maintainer, who edits and publishes.
A message says "Members' role changed". The invitations you send from Settings ▸ People always name a role, so this is for the ones that don't, such as those your company's directory sends. It doesn't change anyone who joined already. The roles are explained in Invite people and choose their roles.
Agents may publish, or only suggest
The row Agents may publish decides what an agent with its own sign-in may do when it changes an instruction.
- Off, where every organization starts: an agent suggests changes, and a person publishes them. If an agent tries to publish, it is refused and told to suggest the change and ask a maintainer.
- On: an agent with the Maintainer role may publish versions itself. It can also merge proposed changes.
A message says "Agents may publish" or "Agents propose". Agents' own sign-ins are the ones made under Developer ▸ API keys. An AI app you connected as yourself, such as Claude or ChatGPT, acts as you, with your role. This switch doesn't apply to it.
Two more rules about agents aren't in the editor yet, and both are off to start with. One lets agents approve proposed changes, and lets their changes reach chosen version names without a person. The other lets agents share an instruction with more people, or make it public. A developer sets them. See the developer note at the end of this page.
Only signed versions
Every version published on instruction.md is signed for you with your organization's key, so you can always tell who published it. See Keep agents on a stable version for how agents use this.
The switch Only signed versions on refs is in Developer ▸ Signing ▸ Signed versions. Developer shows in the side bar only when developer mode is on. With developer mode off, Settings ▸ Security has a row that says where these rules went, and Open Developer opens it.
Only approved integrations
Plans On Team and Enterprise
Integrations are the tools, skills and other agents your organization adds for its instructions. With this rule on, instructions may use only those. Anything else an instruction names is marked as not approved, and isn't used.
Open Integrations in the side bar
Its first page, Overview, lists What's connected.
Turn on Only approved integrations, under Rules
A message says "Only approved integrations from now on". On a plan without this rule, the row shows a Team badge instead of a switch.
Turn it off again and any MCP server, skill or agent may be used. To add integrations, and to allow or block single tools, see Add the tools your agents may use.
The assistant on or off
The assistant is the editor's AI helper. It is on for every organization to start with. The switch is the organization's, so it applies to everyone working on its instructions.
Open Settings ▸ Security
Find the Assistant section.
Turn The assistant in the editor off, or on
A message says "The assistant is off for this organization" or "The assistant is on for this organization".
When it is off, nobody can use the assistant on the organization's instructions. People see "The assistant is turned off for this organization." When it is on, a person's messages and the open instruction's text are sent to OpenAI to answer them. instruction.md keeps none of it. To learn what the assistant does, see The assistant.
Apps your people use
Plans On Team and Enterprise
This is about the apps your people connect with Sign in with instruction.md: you will be able to allow the ones you trust and block the rest. Each person already sees, and can disconnect, the apps that act as them in Connected apps.
Developer mode for new members
Developer mode shows technical details in the editor, such as raw syntax and addresses. Each person turns it on or off for themselves. You can choose what people new to your organization start with.
Open Settings ▸ General
Find the For developers section.
Turn Developer mode for new members on, or off
A message says "New members start with developer mode on" or "…off".
It is a starting point only. A person who has set developer mode themselves keeps their choice. This row is not shown in a personal organization, which has no other members.
Check it worked
- Each change shows a short message saying what changed.
- Open Settings ▸ Security again: each row shows the choice you made.
- For the assistant: open an instruction of the organization. With the switch off, the assistant says it is turned off for this organization.
Undo or stop
Every rule on this page can be changed back the same way, at any time. A change applies from then on. It doesn't change instructions, people or versions that exist already.
If it doesn't work
| You see | Why | What to do |
|---|---|---|
| Nothing in Settings ▸ Security but a row about Developer | You aren't an owner or an admin. | Ask one of them. |
| Changing the policy didn't work | The change didn't save, for example because the connection dropped. | Try again. |
| A Team badge instead of the Only approved integrations switch | Your plan doesn't include it. | Upgrade in Settings ▸ Billing. See Plans, limits and billing. |
| No Developer in the side bar | Developer mode is off. | Choose Open Developer in Settings ▸ Security, or turn on Developer mode in Settings ▸ General. |
| this organization doesn't let agents release versions | An agent tried to publish while Agents may publish is off. | Accept its suggestion yourself, or turn the switch on. |
| Still stuck | Write to us at support. |
Questions
Who can turn the assistant off?
The organization's owners and admins, in Settings ▸ Security ▸ Assistant. The switch applies to everyone working on the organization's instructions.
How do I stop agents from publishing on their own?
Leave Agents may publish off in Settings ▸ Security, which is where every organization starts. Agents then suggest changes, and a person publishes them.
Does changing who can read new instructions change my old ones?
No. It is the starting point for new instructions only. Change an existing one from its share settings.
Is a Claude or ChatGPT I connected limited by the agent rules?
No. An AI app you connect as yourself acts as you, with your role. The agent rules are for agents with their own sign-in.
Do these rules apply in every workspace?
Yes. They belong to the organization, so each of its workspaces follows them.
Related
- Invite people and choose their roles
- Organizations and workspaces
- Add the tools your agents may use
- Keep agents on a stable version
- See who did what
For developers: every rule, its default and the ones not in the editor are on Organization policy.