Share apps

Web apps are an effective way to share information in your map or scene or to display items and related information about a shared group. A web app is a customized user interface that focuses your map or scene for a specific purpose, message, and audience. For example, if you just want to showcase your map, your app only needs a few basic navigation tools. If, on the other hand, your map will be used to collect feedback from the public, it will need specialized data editing tools and instructions for how to enter the information.

For web apps created from maps or scenes, any changes the author makes to the map or scene, including its extent, layers, description, and so on, are reflected in the web app. If a map or scene that was available to everyone in the organization is made private (or deleted), the map or scene no longer appears in the app.

For web apps created from groups, any changes made to the group or items in the group are reflected in the app. If an item that was public or shared with the group is made private or is deleted, the item no longer appears in the app.

Share apps publicly that contain subscriber content

Apps are an effective way to share information in your map, and sharing your apps publicly helps extend the reach of your message. If the map behind your app contains content from ArcGIS Living Atlas of the World, the app may require credentials to access the content. Most of the ArcGIS Living Atlas content is free and can be viewed by anyone. However, a subset of layers, tools, and services known as subscriber content requires an organizational account to access. Subscriber content includes Landsat 8 imagery and landscape analysis layers. Premium content is a type of subscriber content that requires an organizational account to access and consumes credits. Premium content includes demographic maps and tools for geocoding and analytics.

If you want to share an app publicly that contains subscriber content, you can configure it to allow access to the content through your organizational subscription. This optional setting is built into ArcGIS Configurable Apps and indicates which layers require an organizational account and which also consume credits. In ArcGIS Web AppBuilder, this setting is available through the Attribute tab. If you enable access, users will not need an organizational account to access those layers in your app. You can track usage and disable sharing of the app at any time.


Any credits that users consume by accessing premium content within the app will be charged to your organization. If you do not want to consume credits on behalf of users, do not enable any of the premium layers to be accessible through your subscription. This way, users will be required to provide their own credentials for consuming credits. However, keep in mind that if you do this, you will limit who can access your app to people who have an organizational account with privileges to access premium content. For public apps, you should either remove all premium content from the map or you should configure the app to have your organization incur the credit costs. If you want to minimize credit costs incurred for premium content in your app, you can limit the number of requests allowed for each premium content layer in your app when you configure the app or modify the configuration.

Follow the steps below to share publically a configurable app that contains subscriber content.

  1. Use a Configurable Apps template to create a map-based app.

    When you first create your app, the configuration page automatically opens. The Subscriber Content setting appears at the top of the configuration pane with a list of the subscriber and premium content in the app. Premium content is marked with an icon Premium content and indicates layers that consume credits.

  2. If you have already created your app, click Configure App from the item details to open the configuration page.
  3. Check the box beside each premium content layer to allow full access to your app through your subscription. Optionally enter a request limit and interval for each layer—for example, to limit the number of requests for a premium content layer in your app to 100 requests per minute, set the Request Limit value to 100 and the Interval value to Minute. Save your changes when finished.

    If you leave some layers unchecked, the app will prompt the user for credentials, which isn't a good option for a public app. Instead, you should consider removing the layers from the map.

  4. Share your app with everyone (public).
  5. To test that the setting is working correctly, sign out of your organization and open the app. You should not be prompted to sign in.
  6. To view usage, including any credit consumption for premium content, open the item page for the app and click the Usage tab. You can adjust the report to see credits or users and change the time frame for the reporting period. If you have privileges to view status reports, you can view the Apps with Premium Content Proxy section on the Apps tab to track the number of requests, credits used, and other premium content usage information.
  7. To disable allowing access to subscriber content through your subscription once you have enabled it, open the item page for the app, click Configure App, and uncheck the layers in the Subscriber Content section. Be sure to save your changes. The Credits Used option is also disabled from item details.