> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/miscellaneous/security.md).

# Security

## Built on Salesforce, Secure by Design

The Avonni Components Library provides ready-to-use building blocks to enhance your Salesforce Screen Flows and Experience Cloud Sites. Built using the same technology as Salesforce, these components ensure seamless integration and compatibility while adhering to the highest security standards.

## Key Advantages

### **Native to Salesforce**

Avonni Components are built on the Salesforce platform, guaranteeing smooth integration and a consistent user experience.

### **Secure**

The library adheres to Salesforce's strict security standards, including:

* Field-Level Security (FLS)
* CRUD (Create, Read, Update, Delete) permissions for objects
* Data sharing through role hierarchy, sharing rules, and Apex sharing

### **Approved by Salesforce**

The package has undergone a rigorous security review and is listed on the AppExchange, subject to annual security checks.

## Data Access & Security

**Installing the Avonni Components package from the AppExchange won't send any of your Salesforce data outside your Salesforce environment.** Our components are built to work directly within Salesforce and don't interact with any external services. We utilize Salesforce's built-in tools, such as Lightning Data Service, to retrieve data from Salesforce.

Avonni Labs Inc. does not have access to your Salesforce data. If needed, customers can temporarily grant support access using the Salesforce "[Grant Access](https://help.salesforce.com/s/articleView?id=000384334\&type=1)" feature. The Avonni Components package is designed to run entirely within your Salesforce instance, ensuring your data remains secure within your environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/miscellaneous/security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
