# Co-editors - let a second person build and publish an app

An app has one owner, the person who created it. The owner can add co-editors: other people who may publish new versions, share the app and build change requests with their own agent. Use co-editors when a tool is maintained by a small team and not by one person.

## Add a co-editor

The owner adds co-editors on the app page at scava.ai, in the browser. Agents cannot do it, so nobody can talk an agent into giving someone control. An app can have up to 20 co-editors.

The owner's house rules apply to co-editors too. A person outside the allowed domains cannot be added, and a person the owner removed from all apps cannot be added until the owner lets them in again. See [House rules](/docs/house-rules).

> Add only people you trust with all the data of the app. A co-editor has no special rights over the entries of the running app; the rules apply to them like to everybody. But they can publish new rules and new server code, and with that reach all the data of the app.

## What a co-editor can do

- Publish new versions, and put an earlier version back live.
- Share the app and remove shares, within the owner's house rules.
- Answer requests for access.
- Accept, decline and finish change requests, and build the ones they accepted with their own agent.
- Fetch the files of the app to work on them, with the tool `pull_app`.
- See the state of the server part of the app and the problems reported for it. Webhook keys stay hidden from them.

## What stays with the owner

- The name of the app, pausing, deleting.
- The own address of the app (see [Your own address](/docs/custom-domains)).
- Secrets and webhook keys.
- Adding and removing co-editors.
- Downloading all data of the app.

## The app stays the owner's

Everything is counted on the owner's side: the plan of the owner, the storage of the owner, the limits of the owner's server code and the owner's house rules. If the owner has no plan, nobody can publish to the app. Every version records who published it.

## Work on an app you co-edit

A co-editor connects their own AI, as described in [Connect your agent](/docs/agents). Then they ask it:

```text
Fetch the Scava app team-vacation-k3x9 into a folder, add half days, and publish it again.
```

`list_apps` shows the apps you co-edit. `pull_app` writes the files of the live version into a new, empty folder, or into the folder that already belongs to that app, and remembers the app, so publishing from that folder goes to the same app. It writes only inside the target folder. Viewers never get the server code of an app; only the owner and the co-editors do.

## Change requests with co-editors

A change request is accepted by one person and goes to that person's agent. A co-editor who accepts a request builds it with their own agent. If the person who accepted can no longer edit the app, the request falls to the owner's agent. See [Change requests](/docs/change-requests).

## Remove a co-editor

The owner removes a co-editor on the app page. A co-editor can also leave. If the owner removes a person from all apps with "remove person", the person is no longer a co-editor anywhere.