Skip Navigation
Show nav
Heroku Dev Center Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
Heroku Dev Center Dev Center
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log in or Sign up
View categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Buildpacks
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
      • Working with Node.js
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • Working with PHP
      • PHP Behavior in Heroku
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Vector Database
    • Model Context Protocol
    • Working with AI
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Heroku Inference Quick Start Guides
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
    • Heroku AppLink
      • Getting Started with Heroku AppLink
      • Working wtih Heroku AppLink
      • Heroku AppLink Reference
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
    • Other Salesforce Integrations
  • Integrating with Salesforce
  • Heroku AppLink
  • Working wtih Heroku AppLink
  • Heroku AppLink User Mode Options

Heroku AppLink User Mode Options

Last updated July 14, 2025

Table of Contents

  • User Modes
  • User Mode Examples
  • Additional Reading

There are three user mode options that apply the permissions and roles defined in your Salesforce org when using our SDK: user, user-plus, and authorized-user. You can manage what Salesforce data your Heroku apps can access depending on the user mode. This article describes the user mode options.

User Modes

User

user is the default user mode. In this mode, the context is sent as part of your request from Salesforce to Heroku. The SDK uses the user permissions defined in Salesforce, and applies the permissions when performing DML operations. This mode doesn’t grant additional permissions or additional access to data.

For example, this sample app performs complex compute calculations over Salesforce Opportunities and stores the result back in a Quote record in Salesforce. In user mode, a sales rep can only invoke the app operation on opportunities they own and have access to.

User-Plus

In user-plus mode, the developer and admin can define and grant an additional session-based permission set. You can define the permission set to use for additional permissions through the OpenAPI specification when publishing your app. See Configuring OpenAPI Specification for Heroku AppLink for more information.

For example, the same sample app uses a custom DiscountOverride__c field that only sales leaders can access on the OpportunityLineItem object. In user-plus mode, non-sales leaders can also invoke the app operation because they’re granted the additional permission to access the custom field.

Authorized-User

Authorizations, or authorized-user mode, allow you to provide an authorized user that you can reference in your code. You can perform DML operations in Salesforce and Data Cloud as the specific authorized user in your app’s code. It’s common to have a dedicated user to run workloads, such as in worker dynos or nightly jobs. To use this mode, create an authorization.

For example, this sample app uses the Salesforce Bulk API to exchange data across multiple connected Salesforce orgs. Salesforce APIs are always accessed in the context of the authenticated user, so the code can only access the objects and fields the user has access to. By using a dedicated integration user and running in authorized-user mode, you have more control over what data the app can access.

User Mode Examples

Here are some example integration scenarios and which user modes you can use:

Integration Path Description User Mode
Salesforce → Heroku User in Salesforce invokes the Heroku app and the app maintains the user context when interacting with Salesforce using an AppLink SDK user, user-plus, or authorized-user
Salesforce → Heroku → Salesforce User in Salesforce invokes the Heroku app, the app maintains the user context when interacting with Salesforce using an AppLink SDK, and updates back in Salesforce user, user-plus, or authorized-user
Heroku → Salesforce Heroku app invokes Salesforce via Salesforce APIs authorized-user

Additional Reading

  • Heroku AppLink category
  • Getting Started with Heroku AppLink

Keep reading

  • Working wtih Heroku AppLink

Feedback

Log in to submit feedback.

Working with Heroku AppLink Invoking Heroku AppLink Apps

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices