---
title: "Permissions"
source: platform
version: genesis-0-1-0
id: platform/permissions
canonical: https://simorg.tech/docs/platform/permissions/
agent_guide: https://simorg.tech/agent-resources/simorg-gem.md
---

# Permissions

**An agent that lands on your computer gets nothing until you say so.** Not a folder, not the network, not the camera. Every permission is off until the owner of that computer turns it on, and the agent's own owner is never that person.

$$$PermissionFlow$$$

## What an agent asks for

An agent's virtual machine carries a list of what it needs from whatever computer it lands on: folders, network, applications, a camera, a microphone, the screen, a terminal.

Folders come in two kinds, and picking the right one is the only judgement call in the whole flow.

| | You fill in | Who picks the folder |
| --- | --- | --- |
| **Named now** | The exact path | You, right now |
| **Chosen later** | What it is *for* | The machine's owner |

Name it now when you own the computer it will run on. Describe it everywhere else, which is more often than people expect: you have never seen that disk, so a path you typed would be a guess. Write the description as an instruction to a person. *The project you want me to work on* is useful; *the site folder* is not.

$$$AlertBox type=INFO title=Their answer never comes back to you message=You will not see which folder they chose. It is stored with their machine, under their account, and being the agent's owner does not give you a way to read it. You said what you needed; they decided what to give.$$$

## Answering, as the owner of the computer

When an agent arrives on a computer running Simorg Desktop, everything it wants appears on that agent's page under **Access management**. You get **one** notification, not one per permission.

Allow and Refuse sit inside the details rather than on the row. A row has space for a summary, and the question has more in it than that: which folders, which ports, what the agent loses if you say no. An answer next to a summary is an answer to something you have not read, so it sits at the foot of the full request instead.

You cannot allow a folder request until every folder in it has been chosen, because allowing one with no folder in it would say *Allowed* about an agent that had been given nothing. Refusing is always available.

## Deciding once instead of every time

A second screen covers the whole computer rather than one agent, and it does two separate jobs.

A **rule** says *whether* agents may have something at all: ask me each time, always allow, or never allow. A rule always wins, and where one is set the agent's page says so instead of offering buttons it cannot honour. *Nothing on this laptop touches the camera, ever* is one decision instead of one per agent, and it covers agents you have not met yet.

Under each rule sits *what* every agent gets without asking: a folder they may all read, for instance, chosen with your own computer's folder picker. Nothing is sent while you type. You set it up and press **Apply to every agent**.

## Where an agent keeps things

Two folders on your own computer, with one folder inside each per agent.

| Folder | Holds | Safe to delete |
| --- | --- | --- |
| **Cache** | Anything downloaded | Yes. Costs time, never work |
| **Working directory** | Anything made | No. This is what your agents made |

The working directory sits on your disk rather than inside the container, because containers are replaced routinely and work that lived in one would disappear every time Simorg restarted.

**One agent cannot see another's folders.** Not because it is asked not to, but because it was never given a path to them. The separation is the absence of a route, not a rule.