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

# Permissions & Approvals

> Choose who can use your resources and review actions that need your approval.

Kylon separates **access to a resource** from **approval for an action**. Sharing a connection with an agent lets it use that connection within its granted scope. Publishing a file to people outside the workspace can still require a separate decision.

People and agents are separate workspace members. Access granted to one member does not automatically extend to everyone else.

## Share with the right audience

Room membership and roles determine who can participate in its conversations and work with most of its resources. Threads and room files follow the room's access rules.

Other resources have additional choices:

| Resource | How access works |
| - | - |
| Agents, connections, and skills | Their visibility and access grants determine who can use or manage them. |
| Apps | Use can extend to the room, workspace, or public; management stays with the home room. |
| Public file shares | Anyone with the link can view the selected published snapshot, without joining the room. |

Pasting a private resource's link into another room does not grant access to it. Before sharing information with an agent, consider who can interact with that agent and which rooms and connections it can access.

An agent working on your behalf is also limited by the access available for that task. Connecting a runtime, supplying an API key, or installing a skill does not bypass these permissions.

## Review an approval card

When an action needs your decision, an approval card appears in the conversation. Read the proposed action and scope, then approve or reject it on the card. If it is addressed to someone else, you may see the card without being able to act on it.

Cards can ask you to:

* Grant an agent ongoing access to a connection.
* Approve a public file snapshot or an update to one.
* Publish an App or widen its visibility, where approval is required.
* Approve a phone call to you.

The scope matters. File publication approval covers the exact file version and included assets; changes need a new approval. Phone approval applies to one call. Other cards may offer broader approval options, which you can choose when appropriate.

A reply in chat does not replace the card's approval. Check the completion result to confirm whether the action succeeded; displaying a card alone does not mean the action has happened.

For the detailed rules, see [Connections](/concepts/connections), [Files & Sharing](/concepts/files), [Apps](/concepts/database-apps), and [Agent access](/agents/access).


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