> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Mini-app editing access

> Control who can edit mini-apps and inbox widgets. Invite editors, separate viewing from editing, and transfer ownership to another teammate.

Mini-apps and inbox widgets have an owner and a list of people allowed to edit
them. Creating an app makes you its owner. By default, everyone with app edit permission can edit it.

Editing always requires app edit permission in the workspace. An empty editor
list allows everyone with that permission. Selecting people restricts editing to
those people and the owner. This restriction applies to admins too. Being able
to open an app does not grant app edit permission.

## Invite or remove editors

1. Open **Apps** and choose **Share** from the app's menu.
2. Under **Can edit**, leave the picker empty to allow everyone with app edit
   permission, or select people to restrict editing. The picker includes you as
   the owner. Select only yourself to allow only you to edit.
3. Remove someone from a restricted list to revoke their editing access. Clearing
   the list allows everyone with app edit permission again. Changes save immediately.
   The owner always retains access, even when selecting only other people.

Only the owner can change this list. Invited editors can change code, app details
and widget channels; save versions; publish or unpublish; and delete the app.
Changing the roles under **Can open** also requires the existing manage roles
permission. Sharing through role settings enforces the same app editor restriction.

Removing workspace edit permission or organization membership prevents someone
from editing even if their name remains on the app's editor list. Unavailable
editors remain selected until the owner removes them; changing another selection
does not remove them automatically. They can edit again only after their workspace
membership and app edit permission are restored.

## Transfer ownership

In **Share**, choose a teammate under **Transfer ownership**, then select
**Transfer ownership**. The new owner must have app edit permission.

The new owner controls the editor list. Existing editors keep access, including
the previous owner. The new owner can remove the previous owner afterward.
Transfer ownership before leaving the organization. If the owner has already
left, existing editors can keep editing, but ownership recovery requires support.

## Existing apps

Existing apps start with an empty editor list, preserving editing for everyone
with app edit permission. Existing apps are not assigned an owner automatically.
Contact support to assign an owner before restricting editors. Published apps
remain available to their existing viewers.

## Editing through connected tools

The same restrictions apply when Companion or a connected tool changes an app.
The request must identify the acting user, carry the required access, and—when
changing an existing app with a restricted list—come from a selected editor or its owner. A bare API key cannot
create or change mini-apps, even if its scopes allow app writes.

If an edit is refused, ask the owner to add you under **Can edit** and check your
workspace app edit permission. Admin permission alone does not override the list.

Companion checks edit access before changing app files or building a new version.
If access is denied, it explains that the owner must invite you and leaves the
existing app available to open. You can still ask questions about an app you can view.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.