Skip to main content
Integrate Salesforce in amber

How amberSearch mirrors Salesforce permissions

amber shows a Salesforce record only to users who can open that record in Salesforce. During indexing, amber reads your Salesforce sharing settings and stores the allowed audience with every record. At search time, a user finds a record only if they belong to that audience.

Permission mirroring is switched on per data source by the amber team. Without it, every user with access to the Salesforce data source in amber can find all indexed Salesforce content.

How access is decided

For each record, amber first checks the org-wide default (OWD) of its object.

Public objects (OWD Public Read Only or higher): everyone who has Read on the object, through a profile or a permission set, can find the record.

Private objects: a user can find the record if at least one of these applies.

Salesforce rule

Who can find the record in amber

Ownership

The record owner

Role hierarchy

Users in every role above the owner's role. Users in the same role as the owner get no access from it.

Sharing

Every user, public group, role or queue the record is shared with: manual shares, sharing rules and team shares

View All

Users whose profile or permission set has View All on the object, or View All Data

Controlled by Parent objects take the audience of their parent record.

Owners and directly shared users must also have Read on the object. If amber cannot determine who may read a record, the record is hidden, not shown to everyone.

Special content types

Content

Who can find it in amber

Emails, feed posts, comments and attachments

Same audience as the record they belong to, for example the case

Files

Everyone who can reach the file through any of its links: the users, libraries and records it is shared with. Users with Query All Files see all files.

Contacts without an account

The owner and users with View All only, as in Salesforce

Email templates, reports and dashboards

Follow their folder: public folder = everyone, personal folder = its owner, any other folder = users with View All Data only

Known limitations

  • Folders shared with selected users or groups are visible to View All Data users only, because Salesforce does not expose folder shares through its API.

  • When a record is shared with a group or role, every member can find it, including members who lack Read on the object.

  • The role hierarchy is always applied, also for custom objects where Grant Access Using Hierarchies is turned off.

  • A file link counts only if it points to a user, a library, the whole organization, or an account, contact, lead, opportunity, case or campaign. A file shared only through a Chatter group or another object type is visible to Query All Files users only.

Requirements

The amber user from the connected app setup must be able to read your sharing configuration, in addition to the content itself:

  • Org-wide defaults, profiles, permission sets and their assignments

  • Users, roles and folders

  • Share entries of the indexed objects and the links of files

In practice this means the permissions View Setup and Configuration and View All Data for the amber user.

When changes take effect

Change in Salesforce

Visible in amber

Record edited, including a new owner

The record itself: next incremental indexing run. Its emails, feed posts, comments and files: next full indexing run.

Sharing changed without editing the record: new or removed share, sharing rule, OWD, role hierarchy

Next full indexing run

Salesforce does not mark a record as modified when only its sharing changes. Removing access therefore takes effect with the next full run.