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

# Security

> Agent ownership, access, and protection of data

[Appy.ai](https://Appy.ai) recognizes that the confidentiality, integrity and availability of information and data created, maintained and hosted by us are vital to the success of the business and privacy of our partners.

<Note>
  **See Appy's SOC-2, GDPR, HIPAA, ISO-27001 compliance and more in the** [Appy.ai Trust Center](https://trust.appy.ai/)
</Note>

***

## Ownership: one accountable owner per resource

Every agent, automation, and agent-created website carries the same three-part access list:

* **Owner** — the one person accountable for it. Only the owner can decide who else is allowed to use or manage it.
* **Managers** — people who can edit, configure, share, or delete it. This always includes the owner.
* **Users** — people who can open or run it, without being able to change it.

### Who can see something when it's created

* **A new custom agent or business process starts visible only to the person who created it.** They're automatically its owner, and its only user and manager, until they choose to widen it.
* **A new website starts visible to your whole organization.** Everyone signed in can open it, and its creator manages it (and owns it, if they're a member of your org) — so a page built for your team doesn't accidentally lock out the rest of it.

Nothing is public until someone with manage access decides to make it so.

### Moving ownership and changing access

**Only the owner can change who else has access.** A manager who isn't the owner can still edit the resource itself, just not reassign who's allowed to see or manage it. If you ever get a message saying only the owner can make a change, that's why.

<Note>
  Message @ [appy.ai](https://appy.ai) to ask to change access to something when you have the appropriate permissions.
</Note>

## Confirm before anything is destroyed

Nothing below happens on the first ask. Before any of these actions take effect, Violet tells you exactly what's about to happen and waits for your approval: nothing is changed, deleted, or disabled until you say yes.

| **Action** | **What you're asked** |
| - | - |
| Renaming or deleting a database table, column, or link | "Rename or delete the '{name}' table, column, or link? This can destroy existing data." |
| Archiving a custom agent | "Archive the '{name}' agent? Nobody in your organization can use it after that." |
| Deleting a skill | "Delete the '{skill}' skill? All the files in it are removed permanently." |
| Removing one of Violet's standing rules for an agent | "Delete the '{rule}' standing rule for {agent}?" |
| Deleting a published website | "Delete the '{site}' published site? Public links stop working and the files are removed." |
| Deleting a business process, its brief, one of its triggers, or a file inside it | "Delete the '{name}' business process? This also stops its schedules." (and the matching question for each part) |
| Deleting a cloned voice | "Delete the '{voice}' cloned voice? It's removed permanently and can't be used to make audio again." |

A couple of guardrails sit underneath this:

* **An agent can never delete or archive itself or its core behaviors**
* Only Violet changes a database's structure. Adding a new table, column, or link takes effect immediately, since there's nothing to undo; renaming or deleting an existing one is what triggers the approval above — a custom agent or automated business process that needs either hands the request to her rather than making the change directly.
* If a request mixes a safe database addition with a change to something that already exists, Violet holds the whole request for your approval together, rather than applying the safe part and asking about the rest.
* If an unattended, automated run would need one of these approvals and there's nobody present to ask, Appy refuses the action outright and leaves everything as it was, rather than guessing on your behalf.


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