Skip to main content
Domino enforces App access at the proxy level, before any request reaches your App code. Set it when you publish, or at any time afterwards from the Share App dialog.

Choose a sharing mode

Project collaborators can also edit the App, so you add an editor by adding that person as a collaborator on the project that holds the App.
The Share App dialog, showing sharing mode and the list of users with access.

Handle access requests

The Share App dialog is where you review pending requests, grant or deny access, and track notifications.
  • Pending requests appear with Accept and Deny options.
  • Access request notifications go out by email and in Domino when someone requests access, naming the requester, the App, the project, and linking to the Share App dialog.
  • Access granted notifications go out by email and in Domino when you grant access, naming the App and linking to its details page.
Domino sends a notification whenever you grant access, whether you accepted a request or assigned access directly.

Decide whose identity the App uses

By default an App acts with the identity and privileges of its publisher, so every viewer shares the publisher’s permissions when the App reaches Domino resources. Enable Allow App to act for viewers in Domino when the App has to query Datasets under row-level security, start Jobs for a viewer, use Data Sources that need viewer credentials, or take any other action as the viewer. The change takes effect after you restart the App. Only SysAdmins or CloudAdmins can enable this setting.
An App with this setting has full access to Domino on behalf of each viewer, including running Jobs, reaching files and data, and managing Projects. Enable it only for Apps you trust to act responsibly with user-level permissions. App security and identity covers the configuration steps and the security implications.
Last modified on August 27, 2026