CertSafari
    Snowflake SnowPro Specialty: Native Apps· Lessons

    Domain 3 · Lesson 9/12

    Installing Snowflake Native Apps: privileges, listings and packages

    Install and configure applications.

    18 min read
    3.67% of exam
    15 sources
    Published 21 Oct 2026
    Docs as of 18 Oct 2026

    What you will be able to do

    • Explain what installing a Native App creates in the consumer account and who owns it
    • List the privileges the consumer role and the provider role need before an install can succeed
    • Contrast installing from a Marketplace or private listing with CREATE APPLICATION FROM APPLICATION PACKAGE
    • Separate the manifest privileges Snowflake grants automatically from those the consumer must grant by hand
    • Enable and limit multiple instances of one app in a single consumer account
    • Choose the install path and distribution setting that let a consumer in another account or organization install an app
    • Explain how provider-shared objects, remote-region replication and regional event sharing affect an app after it is installed

    Key concept

    Installation creates an owned APPLICATION object — Installing a Native App creates an APPLICATION object in the consumer account and runs the provider's setup script inside it. The role that ran the install owns that object, so every later grant, configuration change and recovery step depends on that role.

    1.What an installation creates, and who owns it

    An install creates one APPLICATION object in the consumer account, and the provider's setup script then builds everything the app needs inside that object. The app usually isn't ready to use yet when the install finishes. The consumer still has to approve any App Specs and set up the explicit data access grants the app needs, so whoever does the install should have enough privilege to finish that configuration in the same session.

    The installing role becomes the owner of the APPLICATION object. This matters later. If someone drops that role, the app stops working and can't be repaired: the only fix is to drop the app and install it again. To retire the role safely, first move the app to another role with GRANT OWNERSHIP, then drop the original role. A dedicated install role that nobody tidies away is cheaper than a reinstall.

    The installation screen lists what the app asks for. This includes its Category 1 privilege requests, which are granted automatically if the consumer proceeds, and any initial App Specs that need approval. If the list contains something that wasn't discussed during procurement, stop and ask the provider before continuing. Private listings call for the same care as public ones, because they may not have been through the Marketplace-level review.

    A consumer in another account can only install through a listing. CREATE APPLICATION ... FROM APPLICATION PACKAGE works only in the account that holds the package, so every cross-account install uses FROM LISTING, which takes the listing's global name, such as GZSNP47HXH1, rather than its display name. A script that passes the display name fails before the setup script ever runs. How far the listing can reach is set on the package by its DISTRIBUTION property. INTERNAL allows only private listings inside the provider's own organization. EXTERNAL is needed before an account in a different organization can install the app, and the framework supports that case.

    Checkpoint 1 of 9· Check yourself

    A team installed a Native App using a role called APP_INSTALLER. They now want to retire that role and leave the app with ADMIN_ROLE. What should they do?

    Sources1234

    2.Privileges the consumer and provider need before installing

    An install from a listing means the consumer account is consuming an inbound share, so the installing role needs the share-consumption privileges. IMPORT SHARE lets a role see the inbound shares offered to the account. Combined with the global CREATE DATABASE privilege, it also lets the role create objects from those shares. ACCOUNTADMIN holds both by default. Any other role must be granted them first, for example with GRANT IMPORT SHARE ON ACCOUNT TO SYSADMIN; run as ACCOUNTADMIN. The Native App install page names CREATE APPLICATION as the privilege that goes with IMPORT SHARE.

    Paid apps add one more requirement. To select Buy instead of Get, the role must also hold PURCHASE DATA EXCHANGE LISTING and meet Snowflake's other payment criteria.

    The provider side has a separate set of privileges, and they belong to building the app, not consuming it. Creating the package that consumers will install requires the global CREATE APPLICATION PACKAGE privilege. To make a package available outside the organization, select Distribute to accounts outside of your organization. That choice starts an automated security scan of every version and patch. Privileges such as CREATE SHARE, MANAGE GRANTS or CREATE ACCOUNT don't let a consumer role install anything.

    Who needs which privilege for an install to succeed
    ActorPrivilegeWhat it enables
    Consumer installing roleIMPORT SHARESee inbound shares, including app listings
    Consumer installing roleCREATE DATABASE (with IMPORT SHARE)Create objects from an inbound share
    Consumer installing role (paid app)PURCHASE DATA EXCHANGE LISTINGBuy a monetized listing
    Provider roleCREATE APPLICATION PACKAGECreate the application package consumers install

    Checkpoint 2 of 9· Check yourself

    SYSADMIN has been given IMPORT SHARE and CREATE APPLICATION, and it installs free apps from listings without trouble. On a monetized listing, though, it can't select Buy. Which privilege does SYSADMIN still need?

    Checkpoint 3 of 9· Exam question

    Before a consumer role (other than ACCOUNTADMIN) can install a Snowflake Native App from a Marketplace listing, which pair of privileges must that role hold?

    Checkpoint 4 of 9· Exam question

    Which privilege must a role in the provider account hold in order to create and manage the application package that consumers will later install?

    Sources567

    3.Installing from a listing versus from an application package

    The two install paths share one command but have different sources and different users. Consumers install from a listing. That can be a public Marketplace listing (Marketplace » Snowflake Marketplace) or a private listing that shows up under Catalog » Apps in Recently shared with you. Both flows look the same: review the Security details (account-level privileges, privileges on objects, SNOWFLAKE database role grants, connections and events), select Get or Buy, choose a warehouse to run the install, optionally name the app, and select Get again. Behind that flow is the FROM LISTING form of CREATE APPLICATION.

    The listing form of CREATE APPLICATION, used for consumer installssql
    CREATE APPLICATION <name> FROM LISTING <listing_global_name>
       [ USING RELEASE CHANNEL { QA | ALPHA | DEFAULT } ]
       [ COMMENT = '<string_literal>' ]

    Installing from an application package is how a provider tests an app in the same account where the package lives, before publishing it. Here the privileges are on the provider side. The role needs the account-level CREATE APPLICATION privilege plus the object-level INSTALL privilege on the package. The role that created the package can already do this. Any other role that should create and test apps from the package needs the DEVELOP privilege on that package. The package form can point at a specific version and patch, and it accepts DEBUG_MODE, which the listing form doesn't.

    The package form, pinned to a version and patch for local testingsql
    CREATE APPLICATION <name> FROM APPLICATION PACKAGE <package_name>
      USING VERSION  <version_identifier> [ PATCH <patch_num> ]
      [ DEBUG_MODE = { TRUE | FALSE } ]

    To test the consumer experience across accounts, the provider creates a private listing, shares it with another account in the organization, signs in to that account and installs from the listing. This exercises the consumer privileges and Security screen that a same-account package install skips. Release channels apply to both paths: the default channel carries the reviewed production version, and alpha and QA carry previews that may not have passed review.

    Checkpoint 5 of 9· Check yourself

    Before publishing, a provider wants to rehearse exactly what a consumer will go through: the Security screen, Get, and the consumer-side install privileges. How should they install the app for this test?

    Sources86

    4.Granting privileges and binding references during installation

    With manifest_version: 2, most of the privileges a provider declares in the manifest are granted to the app automatically at install and upgrade, with no extra step by the consumer. The setup script can then run CREATE OR REPLACE WAREHOUSE application_wh; without first checking for a grant. Automatic grants can't be revoked afterwards, which is why consumers should read the Security details before selecting Get.

    Manifest privileges by how they reach the app
    PrivilegeHow it is granted
    EXECUTE TASK, EXECUTE MANAGED TASKAutomatically
    CREATE WAREHOUSE, CREATE COMPUTE POOL, CREATE DATABASEAutomatically
    BIND SERVICE ENDPOINTAutomatically
    CREATE EXTERNAL ACCESS INTEGRATION, CREATE SECURITY INTEGRATION, CREATE SHARE, CREATE LISTINGAutomatically, but use also needs an approved app specification
    MANAGE WAREHOUSESManually by the consumer
    IMPORTED PRIVILEGES ON SNOWFLAKE DBManually by the consumer
    READ SESSION, EXECUTE ALERTManually by the consumer

    Manually granted privileges follow the Consumer privilege-granting workflow. For installation, the practical point is that the consumer's role runs those GRANT statements, so it has to hold the privileges before the install starts. Apps can check for account-level privileges in the consumer account, and a provider without a UI should document the exact GRANT statements, preferably in the README. If the provider built a Python Permission SDK interface, Snowsight runs the GRANT statements for the consumer.

    Access to existing consumer objects works through References to consumer objects, which the consumer binds to actual objects during or right after installation. If there's no permission UI, the consumer creates each reference and associates it with the app by hand. A reference that is never bound, or that points to an object the app can't access, is a common reason an app installs cleanly and then fails the first time it touches consumer data.

    Checkpoint 6 of 9· Match them up

    A manifest_version: 2 app needs each of the following. Match each one to how the app gets it.

    Tap a term, then the definition that fits it.

    Checkpoint 7 of 9· Exam question

    A provider declares several privileges in the application manifest under manifest_version: 2. During installation, which of these privileges can only be granted through explicit manual action by the consumer, because Snowflake does not grant them automatically? (Select all that apply)(Select 3)

    0 of 3 selected

    Sources910

    5.Running more than one instance of an app in one account

    By default a consumer account gets one instance of an app. The provider opts in to more by setting MULTIPLE_INSTANCES on the application package. The setting covers every release channel in the package, but it only affects apps installed from a listing, not apps created directly from a package. Each instance gets its own name at install time, so a team can run separate instances side by side and test each one independently.

    Enabling multiple instances when creating or altering the packagesql
    CREATE APPLICATION PACKAGE <name> MULTIPLE_INSTANCES=TRUE;
    ALTER APPLICATION PACKAGE <name> SET MULTIPLE_INSTANCES=TRUE;

    Paid listings are the exception. Behind a paid listing a consumer can still run several instances on the QA or ALPHA channels, but only one on the DEFAULT channel. Free listings allow several DEFAULT-channel instances. For a paid app, the usual pattern is one production instance on DEFAULT plus any number of evaluation instances on ALPHA.

    Checkpoint 8 of 9· Check yourself

    On a paid listing whose package has MULTIPLE_INSTANCES=TRUE, a consumer already runs the production app on the DEFAULT channel. They now want a second instance in the same account so they can run user acceptance testing on the provider's upcoming version. How should they install it?

    Sources116

    6.What an installed app still depends on in the provider account and region

    An installed app keeps depending on the provider's account after the install finishes. Data the provider shares through the application package isn't copied into the consumer account. The app reads it from the package on every query, so when a provider inserts rows into a shared table, every consumer's app returns them on the next query, with no upgrade. The same link explains an error consumers sometimes report. If a provider removes the listing and its attached package, the app still appears in the consumer account, but opening it returns an error saying the application package has been removed. A provider can't drop a package while a listing is still attached to it.

    Provider objects reach the consumer only through objects the app owns. A table in a database outside the package can't be shared straight to the installed app. Instead, the provider grants REFERENCE_USAGE on that database to the package and exposes the table through a view inside the package. Even then, consumer roles can't query shared content directly. Only the app's views, stored procedures, functions and tasks can read it. So when a consumer reports a missing provider table, check whether the setup script exposes it through an app-owned object before you suspect the share.

    Consumers in other regions get the app through Cross-Cloud Auto-Fulfillment, which replicates the application package to their region, and that replication sets how quickly they see changes. A new release directive takes effect in a remote region only after the package has been replicated there. LISTING_AUTO_REFRESH is TRUE by default, and in that case Snowflake starts replication as soon as the directive changes. If it is FALSE, remote consumers stay on the old version until a scheduled or on-demand refresh. Two limits come up before publishing. Packages containing external or Apache Iceberg tables can't be auto-fulfilled at all. Publishing to remote regions also needs a role that holds MANAGE LISTING AUTO FULFILLMENT.

    Multi-region event sharing has a boundary of its own. A consumer turns on event sharing the same way in every region, but the events go only to a designated provider account in that consumer's region. A provider with consumers in several regions therefore needs a provider-side centralized setup, described on the page about collecting events from consumers in other regions, to read the events in one place. Before you answer an EU consumer's question about where their shared events go, find out which provider account is designated in their region.

    Checkpoint 9 of 9· Check yourself

    A provider moves the DEFAULT release directive to a new version. Consumers in the provider's own region pick it up, but a consumer served through Cross-Cloud Auto-Fulfillment in another region is still on the old version a day later. The package has LISTING_AUTO_REFRESH = FALSE. What explains it?

    Sources12711131415

    Sources

    (15)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “The role you use to install a Snowflake Native App becomes the owner of the APPLICATION object.”
      ↩︎ What an installation creates, and who owns it
      “private listings may not have gone through the same Marketplace-level review that public listings require”
      ↩︎ What an installation creates, and who owns it
      “your account must have Snowpark Container Services enabled”
      ↩︎ What an installation creates, and who owns it
      “All human users in your account must have multi-factor authentication (MFA) enrolled.”
      ↩︎ What an installation creates, and who owns it
      “Installing a Snowflake Native App creates an APPLICATION object in your account and runs the app’s setup script”
      ↩︎ Key concept
      “If the owner role is dropped, the app becomes non-functional and cannot be recovered”
      ↩︎ Exam trap 3
      “If you need to change the owner, use GRANT OWNERSHIP to transfer ownership to a different role before dropping the original role.”
      ↩︎ Checkpoint
      “from the alpha channel for previews or User Acceptance Testing (UAT) prior to production use”
      ↩︎ Checkpoint
    2. 2.
      “This clause can only be used to create an app in the same account as the application package.”
      ↩︎ What an installation creates, and who owns it
      “Use the listing global name (for example, GZSNP47HXH1) rather than the display name.”
      ↩︎ What an installation creates, and who owns it
      “This clause can only be used to create an app in the same account as the application package.”
      ↩︎ Exam trap 4
    3. 3.
      “INTERNAL indicates that a provider can only create a private listing within the same organization where the application package was created.”
      ↩︎ What an installation creates, and who owns it
    4. 4.
      “the Snowflake Native App Framework supports sharing apps with accounts in different organizations”
      ↩︎ What an installation creates, and who owns it
    5. 5.
      “The privilege also permits creating databases from inbound shares if the role is also granted the global CREATE DATABASE privilege.”
      ↩︎ Privileges the consumer and provider need before installing
    6. 6.
      “To access a listing, you must use the ACCOUNTADMIN role or another role with the IMPORT SHARE and CREATE APPLICATION privileges.”
      ↩︎ Privileges the consumer and provider need before installing
      “To pay for an app, your role must also have the PURCHASE DATA EXCHANGE LISTING privilege”
      ↩︎ Privileges the consumer and provider need before installing
      “As a provider, you can test your app by creating a private listing, sharing it with another account in your organization”
      ↩︎ Installing from a listing versus from an application package
      “Apps installed from the Alpha release channel may contain versions that have not passed the security review.”
      ↩︎ Installing from a listing versus from an application package
      “Installing different versions of the app allows you to test each version independently.”
      ↩︎ Running more than one instance of an app in one account
      “To pay for an app, your role must also have the PURCHASE DATA EXCHANGE LISTING privilege and you must meet additional criteria.”
      ↩︎ Checkpoint
    7. 7.
      “To create an application package you must have the global CREATE APPLICATION PACKAGE privilege granted to your role.”
      ↩︎ Privileges the consumer and provider need before installing
      “Selecting this option initiates an automated security scan for each version and patch defined in your application package.”
      ↩︎ Privileges the consumer and provider need before installing
      “If a consumer tries to access the Snowflake Native App, they receive an error indicating the application package has been removed.”
      ↩︎ What an installed app still depends on in the provider account and region
      “providers cannot remove an application package that is currently associated with a listing.”
      ↩︎ What an installed app still depends on in the provider account and region
    8. 8.
      “you can create an app in the same account as its application package and test it before you publish it to consumers.”
      ↩︎ Installing from a listing versus from an application package
      “The INSTALL object-level privilege granted on the application package.”
      ↩︎ Installing from a listing versus from an application package
      “To let other roles create and test apps from an application package, grant them the DEVELOP object-level privilege on the application package.”
      ↩︎ Installing from a listing versus from an application package
    9. 9.
      “After privileges are automatically granted during installation or upgrade, these privileges cannot be revoked.”
      ↩︎ Granting privileges and binding references during installation
      “Consumers must manually grant these privileges when installing or upgrading an app.”
      ↩︎ Exam trap 1
      “Consumers must manually grant these privileges when installing or upgrading an app.”
      ↩︎ Prediction
      “Some privileges are not automatically granted to the app. Consumers must manually grant these privileges when installing or upgrading an app.”
      ↩︎ Checkpoint
    10. 10.
      “Check for account-level privileges in the consumer account.”
      ↩︎ Granting privileges and binding references during installation
      “SQL statements that the consumer must run to grant the necessary privileges to the app”
      ↩︎ Granting privileges and binding references during installation
      “the consumer must manually create the reference, then associate it with the Snowflake Native App”
      ↩︎ Granting privileges and binding references during installation
    11. 11.
      “You can allow consumers to create multiple instances of an app in their account by setting the package’s MULTIPLE_INSTANCES property.”
      ↩︎ Running more than one instance of an app in one account
      “Enabling multiple instances for the application package applies to all release channels within the application package.”
      ↩︎ Running more than one instance of an app in one account
      “a change to a release directive takes effect in a remote region only after the application package is replicated to that region”
      ↩︎ What an installed app still depends on in the provider account and region
      “When LISTING_AUTO_REFRESH is FALSE, changes require a scheduled or on-demand refresh.”
      ↩︎ What an installed app still depends on in the provider account and region
      “Note, this property only applies to apps installed from a listing.”
      ↩︎ Exam trap 2
      “a consumer can only have one instance of an app using the DEFAULT release channel”
      ↩︎ Prediction
    12. 12.
      “Snowflake doesn’t copy or snapshot shared content when a consumer installs or upgrades an app.”
      ↩︎ What an installed app still depends on in the provider account and region
      “You cannot share objects outside the application package directly with app installed in the consumer account.”
      ↩︎ What an installed app still depends on in the provider account and region
      “Only objects that the app owns, such as views, stored procedures, functions, and tasks, can access shared content.”
      ↩︎ What an installed app still depends on in the provider account and region
      “Cross-Cloud Auto-Fulfillment is not supported for apps that contain external or Apache Iceberg™ tables.”
      ↩︎ What an installed app still depends on in the provider account and region
      “Snowflake doesn’t copy or snapshot shared content when a consumer installs or upgrades an app.”
      ↩︎ Exam trap 5
    13. 13.
      “Grants the ability to publish listings to remote regions using Cross-Cloud Auto-Fulfillment and manage auto-fulfillment settings for listings.”
      ↩︎ What an installed app still depends on in the provider account and region
    14. 14.
      “Snowflake sends the shared events to a designated provider account within the same region as your account.”
      ↩︎ What an installed app still depends on in the provider account and region
    15. 15.
      “allows an app to share telemetry messages from different regions to a central location”
      ↩︎ What an installed app still depends on in the provider account and region

    Continue to part 2 of 2

    Native App event tables, event sharing and install troubleshooting

    Spotted a mistake, or was something unclear? Tell us.