Canvas Personal App Process

Here’s how to make canvas personal apps available to end users.

1. You verify that the organization administrator has enabled personal apps within the destination organization. For details, see Enabling Canvas Personal Apps within an Organization.
2. You create the app, and specify that it’s a canvas personal app. For details, see Making an App a Canvas Personal App.
3. The end user clicks the app link that you’ve provided. For example, the link could be a button on your website, or delivered in an email. Clicking the link invokes the OAuth approval process for the app. Here’s an example of what a link to the app looks like:
   https://MyDomainName.my.salesforce.com/services/oauth2/authorize?response_type=code&client_id=<your_client_id>&redirect_uri=<your_redirect_uri>

4. When prompted, the end user approves the app and allows access to Salesforce data.
5. The OAuth approval flow triggers the canvas installer in asynchronous mode. The canvas installer gets context information for the app from the API, and installs the app’s metadata. The app is installed in the background, and the end user receives an email when installation is complete.

   Only the canvas personal app’s metadata is installed. Any additional components that are typically packaged with a canvas app are not installed with the app. This means that users get only the functionality they need, and installation is quick and lightweight. However, if the administrator chooses to install the canvas personal app for the entire organization, the additional package components are installed, as with any canvas app.

   Note

6. The user starts using the canvas personal app by clicking the app’s icon from the Chatter tab.