Skip to content

Docs/apps/updating perm docs #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lc-cbot wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Docs/apps/updating perm docs #324

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d840274
Clarify custom mini apps permissions and scope
lc-cbot Jul 28, 2026
c5a8df8
docs(apps): document the app.* user permissions and correct .mtd scope
lc-cbot Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/apps/creating-and-managing-apps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,9 @@
You manage everything from **Apps** in your organization sidebar
(`/orgs/<your-org>/apps`). The page header reads:

> Custom mini apps for this organization. Apps run in a sandboxed frame and act on
> your behalf only within the permissions you approve.
!!! info "Custom mini apps for this organization"

Check failure on line 9 in docs/apps/creating-and-managing-apps.md

View workflow job for this annotation

GitHub Actions / check-markdown

Trailing spaces 

docs/apps/creating-and-managing-apps.md:9:50 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md009.md
Apps are scoped to the organization they're installed in. They're run in a sandboxed

Check failure on line 10 in docs/apps/creating-and-managing-apps.md

View workflow job for this annotation

GitHub Actions / check-markdown

Trailing spaces 

docs/apps/creating-and-managing-apps.md:10:89 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md009.md
frame and act on your behalf only within the permissions you approve.

## Building an app with the AI assistant

Expand Down
35 changes: 23 additions & 12 deletions docs/apps/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,18 +86,29 @@ and it can read LimaCharlie data on your behalf. Three things keep that safe.

## Who can use apps

Access is governed by a small set of organization permissions:

| To… | You need |
| --- | --- |
| See and open apps | `app.get` |
| Create or edit apps | `app.set` |
| Delete apps | `app.del` |
| Turn an app on or off | `app.set.mtd` |

These permissions control who can *manage app records*. They are separate from the
permissions an individual app requests to do its job. See
[Permissions](../8-reference/permissions.md) for the full model.
Access to apps is governed by a small, dedicated set of organization
permissions — the `app.*` set. They follow LimaCharlie's standard config-hive
pattern: a plain permission grants access to the **whole record** (including the
app's HTML and its name, description, and icon), while its `.mtd` ("metadata")
counterpart grants access only to the record's metadata envelope — its
enabled/disabled status, tags, and timestamps — never the app's contents.

| Permission | Grants | What it's for |
| --- | --- | --- |
| `app.get` | Read the full app record — its HTML, name, description, and icon | **View and run** an app, view its source, and see it in the launcher |
| `app.get.mtd` | Read only the record's metadata envelope — enabled/disabled status, tags, timestamps, last editor — **not** the app's HTML, name, or description | Check whether apps exist and are turned on, without being able to open, run, or read them |
| `app.set` | Create and modify app records, including their HTML and configuration | Build a new app or edit an existing one |
| `app.set.mtd` | Modify only the record's metadata, most notably its enabled/disabled status | Turn an app on or off without the ability to change what it does |
| `app.del` | Delete app records | Remove an app from the organization |

!!! note "These gate managing apps, not what an app can do"
The `app.*` permissions decide who can **manage app records**. They are
entirely separate from the permissions an individual app requests in its
`required_permissions` to do its job — those are minted into the app's
scoped, per-viewer key. Don't conflate the two. See
[Permissions](../8-reference/permissions.md) for the full catalog and
[Reference: Permissions and consent](reference.md#permissions-and-consent)
for how an app's own permissions work.

## Your first app in two minutes

Expand Down
Loading