In a managed organization, rules define what members can use. Moon AI applies them to every request, starting with a member’s next message, as long as the organization features are turned on. A member cannot get around them: a feature that is turned off shows “Disabled by your organization.”. The one exception is “Moon CLI autonomous mode”, which Moon CLI enforces on the member’s computer: see its limits.
How rules combineLink to the How rules combine section
- The organization sets the default value of each setting.
- For each setting, a role or a group can follow the organization (“Same as organization”), allow it or deny it.
- A deny wins over an allow that comes from another role or another group.
- An exception for a member takes precedence over everything else.
A group’s rules do not apply to its managers. A member who is in no group follows the rules of the organization and of their roles.
Where rules are setLink to the Where rules are set section
| Level | Where |
|---|---|
| Organization | Admin console › “Rules”, “The organization” tab |
| Role | The role’s page, “Rules” tab. The “Roles” tab of the “Rules” page lists the roles that have their own rules. |
| Group | The group’s page, “Rules” and “Models” tabs |
| Member | Admin console › “Rules”, “Member rules” tab |
See what applies to a memberLink to the See what applies to a member section
- Admin console › “Rules” › “Member rules” tab.
- Search for the member by name or email address.
- “What applies to this member” shows each rule and where it comes from. “Show every rule” also shows the ones that do not restrict them.
The member can see the rules that apply to them in “Settings” › “Your workspace”.
Give a member an exceptionLink to the Give a member an exception section
- In “Member rules”, choose the member, then “Add exception”.
- Allow or deny the settings you want, for this person only. You can also write “Instructions for this member”.
- Click “Save exception”.
The “Exceptions” tab lists the members who have one. “Remove” gives the member back the rules of the organization, their roles and their groups.
The settingsLink to the The settings section
ModelsLink to the Models section
“Available models”: all Moon AI models, new ones included, or a chosen list. The list is set in “Models” › “Allowed models”: see Models and resources. The titles and summaries Moon AI writes for conversations never use a model that the rules take away.
ModesLink to the Modes section
| Setting | What it allows |
|---|---|
| “Auto mode” | Moon AI picks the model for each message. |
| “Agent mode” | Moon AI plans and carries out a task in several steps. |
| “Comparing models” | Two models answer the same message, side by side. |
FeaturesLink to the Features section
| Family | Settings |
|---|---|
| “Creation” | “Image generation”, “Video generation”, “Music generation” (it follows the videos setting until you set it), “Voice”, “Artifacts” |
| “Research” | “Web search”, “Reading web pages”, “Deep research” |
| “Automation” | “Agents”, “Routines”, “Skills”, “Messaging apps” |
| “Conversations and data” | “Memory”, “Projects”, “File uploads”, “Import from another AI”, “Temporary chats”, “Personal instructions” |
| “Sharing” | “Public share links” |
| “Technical access” | “Isolated computer”, “Moon CLI”, “Moon CLI autonomous mode” (see below), “API keys” (developer API) |
ConnectorsLink to the Connectors section
- “Allowed connectors”: all connectors, none, or a chosen list. A role or a group can “Add connectors to the organization’s list” or “Remove connectors”.
- “Personal MCP servers”: allows or blocks the servers a member adds on their own, outside the organization’s catalog.
The organization’s MCP servers are set in “Resources”: see MCP servers.
FilesLink to the Files section
- “Maximum file size”: from 1 to 500 MB.
- “Allowed file types”: “All types”, or “Only these”. Tick a family (“Documents”, “Spreadsheets”, “Presentations”, “Images”, “Audio”) or type extensions without the dot, for example
pdfordocx, followed by Enter.
UsageLink to the Usage section
“Share of the 5-hour limit”, “Share of the weekly limit” and “Share of the monthly limit”: the share of the plan’s usage limits a member can use, from 1 to 100%. For a role or a group, a value lower than the organization’s restricts, and a higher value allows more. The limits themselves depend on the member’s license: see Licenses and contracts.
LearningLink to the Learning section
“Learning mode on by default”: Moon AI explains step by step and checks understanding instead of giving the answer, and offers quizzes, flashcards and guided paths first. This setting is mainly for schools and universities.
InstructionsLink to the Instructions section
Moon AI reads the instructions in every conversation of the members. A member cannot remove them. They stack up in this order:
| Order | Text | Where to write it |
|---|---|---|
| 1 | Organization instructions (4,000 characters at most) | Admin console › “General” › “Organization instructions” |
| 2 | Instructions of the roles | The role’s page, “Instructions” tab |
| 3 | Instructions of the groups | The group’s page, “Instructions” tab, or “My groups” for a manager |
| 4 | Instructions for a member | The member’s exception, in “Member rules” |
| 5 | Per-model instructions | “Models” › “Per-model instructions” |
| 6 | The member’s personal instructions | The member’s “Settings”, if the organization allows them |
Members can read their organization’s instructions in “Settings” › “Your workspace” › “Your organization’s instructions”.
MemoryLink to the Memory section
Admin console › “General” › “Memory” › “Allow memory in this workspace”.
With memory turned off, Moon AI neither uses nor creates memories in this workspace, for all members. Each member keeps their memories and can always delete them. Only the owner and the admins can change this setting. The “Memory” feature in the rules also lets you deny it to a role or a group.
Access outside the organizationLink to the Access outside the organization section
Admin console › “General” › “Access and retention” › “Access outside the organization”. The same setting appears in “Rules”, “The organization” tab.
| Value | Effect |
|---|---|
| On | Members keep their personal workspace and the other workspaces they belong to. |
| Off | Each active member can only work in the organization. Their personal workspace is no longer offered to them, and they cannot leave the organization on their own. |
Before you save, a confirmation shows how many members will be affected. A member who is held in the organization and tries to leave reads “Your organization manages your membership. Ask one of its administrators if you need to leave.”.
This setting only applies while the organization features are turned on. Closing access outside the organization requires a contract.
Conversation retentionLink to the Conversation retention section
Admin console › “General” › “Access and retention” › “Conversations kept for”. The same setting appears in “Rules”, “The organization” tab (“Delete old conversations”).
- Enter a number of days between 30 and 3,650, or leave it empty to keep conversations until they are deleted.
- Before you save, the page shows how many of the organization’s conversations are older than the chosen duration.
Every night, Moon AI deletes the organization’s conversations that have had no activity for that number of days, pinned and archived ones included. Members are told in their settings and on their welcome card. Nothing is deleted while the organization functions are turned off.
Moon CLI Autonomous modeLink to the Moon CLI Autonomous mode section
In Autonomous mode, Moon CLI edits the files and runs the commands of a folder without asking each time, on the Code page, in Moon Desktop and in the terminal. The “Moon CLI autonomous mode” setting, in the “Technical access” family, allows or denies it like the other settings, for the organization, a role, a group or a member. When it has no value, it is allowed.
When it is denied, Moon CLI no longer offers this mode to the member, no longer applies an Autonomous mode the member had kept for a folder, and starts in normal mode even with the --auto option. “Accept edits” stays allowed. The member sees “Moon CLI’s Autonomous mode is turned off by your organization.”. See When your organization turns off Autonomous mode.
Moon Blur required in Moon CLILink to the Moon Blur required in Moon CLI section
Admin console › “API and keys”, “Moon CLI” section › “Moon Blur required in Moon CLI”.
When this setting is on, Moon CLI requests in this workspace keep Moon AI’s Moon Blur, even if a member turns off Moon Blur in their terminal. Only the owner and the admins can change it. See Moon Blur in Moon CLI.
In the app, Moon Blur is always on for every member: there is nothing to set.