Access control for Snowflake App Runtime¶
This topic describes common access control patterns for delegating operations and viewing access on Snowflake App Runtime. For the full list of privileges, see Snowflake App Runtime privileges.
Deploy to a standard database when sharing with other roles¶
Until an administrator completes
account administrator setup,
snow app setup resolves the destination to a
personal database (USER$<login_name>). You
can’t use GRANT to give other roles access to an Application Service in a
personal database.
To delegate view, operate, or monitor access to other roles, deploy the
Application Service to a standard database and schema. We recommend configuring
the destination through
account administrator setup
before deploy, or explicitly in your snowflake.yml identifier.
Share view-only access to a running app¶
Grant USAGE on the Application Service, plus USAGE on the database and schema that contain it, to let a role open the app. The service must be in a standard database, not a personal database. In Cortex Code CLI or Cortex Code Desktop, you can ask the agent to grant access for other roles, or use the Apps view in Desktop to manage sharing.
Delegate lifecycle control¶
Grant OPERATE to let a role suspend, resume, upgrade, and configure the service without transferring ownership:
An OPERATE role can run:
Delegate monitoring¶
Grant MONITOR to let a role view runtime status and read container logs:
Revoke access¶
For general RBAC concepts, see Overview of Access Control.