Documentation for Salesforce DLS #2056
Conversation
| Document level security (DLS) enables you to restrict access to documents based on a user's permissions. This feature is available by default for the Salesforce connector. | ||
| Salesforce connector DLS supports for both standard & custom objects. | ||
|
|
||
| Refer to [document level security](https://www.elastic.co/guide/en/enterprise-search/master/dls.html) for more information. |
There was a problem hiding this comment.
Should this link to /current/ ?
There was a problem hiding this comment.
I took the reference from already merged connector DLS documentation. Do we need to update this link?
There was a problem hiding this comment.
We're on main here so master in the main docs makes sense
| 2. Choose `Read Only` or `Standard User` for the Existing Profile dropdown, give a name to the profile and save it. By default, `Read Only` or `Standard User` have the read permission to access all standard objects. There can be some more profiles which do have a read access to standard objects but these are some of them. | ||
| 3. Now, edit the newly created profile and under `Object Permissions`, assign at least a `Read` access to the standard objects and custom objects you want to ingest into ElasticSearch. | ||
|
|
||
| **Note:** If users specify advanced sync rules then they need to assign a `Read` access for that specific object in the profile. |
There was a problem hiding this comment.
need to assign a
Readaccess for that specific object
Is this true for both standard and custom objects?
There was a problem hiding this comment.
Yes, this is applicable to both standard and custom objects
|
|
||
| Refer this tutorial to get more idea on setting the permissions - [link](https://howtovideos.hubs.vidyard.com/watch/B1bQnMFg2VyZq7V6zXQjPg#:~:text=This%20is%20a%20must%20watch,records%20in%20your%20Salesforce%20organization.) | ||
|
|
||
| ### Set Permissions using Profiles |
There was a problem hiding this comment.
I think this + the sections below revolving around permissions can be simplified to just explaining what permissions are required for the user.
From what I can see, the only required permissions would be "Read" permissions for the standard/custom objects that the user wants to ingest. Is that correct?
There was a problem hiding this comment.
Yes, the Read permission is sufficient for the users to ingest the objects.
There was a problem hiding this comment.
Looking good, just some copyediting from me. If @navarone-feekery and @danajuratoni are happy we can merge this
| Document level security (DLS) enables you to restrict access to documents based on a user's permissions. This feature is available by default for the Salesforce connector. | ||
| Salesforce connector DLS supports for both standard & custom objects. | ||
|
|
||
| Refer to [document level security](https://www.elastic.co/guide/en/enterprise-search/master/dls.html) for more information. |
There was a problem hiding this comment.
We're on main here so master in the main docs makes sense
|
LGTM also, once @leemthompo's change requests are implemented 👍🏻 |
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
💔 Failed to create backport PR(s)The backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
Part of #1859
Checklists
Pre-Review Checklist