> For the complete documentation index, see [llms.txt](https://docs.omnata.com/omnata-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/how-it-works/access-control.md). # Access Control Privileges in Omnata are granted via Snowflake roles. *** From Snowflake [blog](https://www.snowflake.com/en/blog/snowflake-native-apps-security/): When a provider publishes an application, it includes a [manifest](https://docs.snowflake.com/en/developer-guide/native-apps/creating-manifest) file. This manifest contains the permissions to be granted to the application, which can be reviewed by the application consumer during installation. By default, a Snowflake Native App has no permissions outside of the application itself, including data access or the ability to create database objects (tables, tasks, warehouses, etc). Additional rights can be granted to the application, but that must be done by the application consumer administrators through explicit grants or [references](https://docs.snowflake.com/en/developer-guide/native-apps/requesting-refs). Application code runs as a new application role, with owner’s rights, such that it can only access what that role has been granted to do. This means that the application can’t access data that the caller has access to—it must be explicitly granted permission. *** #### Granting Omnata application role to other roles If you would like to grant access to Omnata owned objects to other roles, you grant the `OMNATA_ADMINISTRATOR` role to the other roles. Run the command: ```sql grant application role OMNATA_SYNC_ENGINE.OMNATA_ADMINISTRATOR to role MY_OTHER_ROLE ``` #### Managing access to the inbound sync storage location By default, Omnata lands data in the Omnata Sync Engine database. Refer to [Inbound Storage Location](/omnata-product-documentation/omnata-sync-for-snowflake/how-it-works/sync-directions-and-strategies/inbound.md#inbound-storage-location) for more information on how this can be customized. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/how-it-works/access-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.