Lightning community how to hide / disable / remove GENERIC RECORD PAGES
I have a community which I created with the Build Your Own template:
This template creates by default 3 GENERIC RECORD PAGES:
I don't want to give access to my users for these pages, but I could not find any way to remove the pages or access to them. Usualy in the page properties there is a PAGE VARIATIONS tab and there you can delete or remove access, but this tab does not exist for these pages:
QUESTION
How can I remove or hide these pages?
community lightning-community community-builder
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
add a comment |
I have a community which I created with the Build Your Own template:
This template creates by default 3 GENERIC RECORD PAGES:
I don't want to give access to my users for these pages, but I could not find any way to remove the pages or access to them. Usualy in the page properties there is a PAGE VARIATIONS tab and there you can delete or remove access, but this tab does not exist for these pages:
QUESTION
How can I remove or hide these pages?
community lightning-community community-builder
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
add a comment |
I have a community which I created with the Build Your Own template:
This template creates by default 3 GENERIC RECORD PAGES:
I don't want to give access to my users for these pages, but I could not find any way to remove the pages or access to them. Usualy in the page properties there is a PAGE VARIATIONS tab and there you can delete or remove access, but this tab does not exist for these pages:
QUESTION
How can I remove or hide these pages?
community lightning-community community-builder
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
I have a community which I created with the Build Your Own template:
This template creates by default 3 GENERIC RECORD PAGES:
I don't want to give access to my users for these pages, but I could not find any way to remove the pages or access to them. Usualy in the page properties there is a PAGE VARIATIONS tab and there you can delete or remove access, but this tab does not exist for these pages:
QUESTION
How can I remove or hide these pages?
community lightning-community community-builder
community lightning-community community-builder
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
asked Dec 31 '18 at 9:03
Itai ShmidaItai Shmida
2,80131946
2,80131946
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
But in my community I can access records - for example:.force.com/grants/s/detail/a1a0x000000RMIOAA4opens the record page (detail is the url for the page in it's properties)
– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
|
show 1 more comment
Every community user has a profile. The trick is to edit that profile and remove the read access to that object at profile level. Once the read access is invoked, the User even if they have access to record they wont be able to access the content via URL hacking or directly hitting the Salesforce Rest Endpoint(Community user is API enabled, so it can hit the SF rest endpoint and access data of records which you haven't' provided access via UI)
You can find the profile of community member under
Communities -> Workspaces -> Member > Selected profile.
Once you get profile name, edit that profile like the way you do it normally and edit the FLS and Object setting to not even have read permission
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245058%2flightning-community-how-to-hide-disable-remove-generic-record-pages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
But in my community I can access records - for example:.force.com/grants/s/detail/a1a0x000000RMIOAA4opens the record page (detail is the url for the page in it's properties)
– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
|
show 1 more comment
You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
But in my community I can access records - for example:.force.com/grants/s/detail/a1a0x000000RMIOAA4opens the record page (detail is the url for the page in it's properties)
– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
|
show 1 more comment
You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
edited Dec 31 '18 at 18:39
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
answered Dec 31 '18 at 10:08
Dave HummDave Humm
4,53751330
4,53751330
But in my community I can access records - for example:.force.com/grants/s/detail/a1a0x000000RMIOAA4opens the record page (detail is the url for the page in it's properties)
– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
|
show 1 more comment
But in my community I can access records - for example:.force.com/grants/s/detail/a1a0x000000RMIOAA4opens the record page (detail is the url for the page in it's properties)
– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
But in my community I can access records - for example:
.force.com/grants/s/detail/a1a0x000000RMIOAA4 opens the record page (detail is the url for the page in it's properties)– Itai Shmida
Dec 31 '18 at 11:01
But in my community I can access records - for example:
.force.com/grants/s/detail/a1a0x000000RMIOAA4 opens the record page (detail is the url for the page in it's properties)– Itai Shmida
Dec 31 '18 at 11:01
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
Dont give object access to the community profile. You being system admin can access it in community builder and when you login as urself in community
– Pranay Jaiswal
Dec 31 '18 at 11:07
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
@PranayJaiswal how do I do that? I cannot find it, can you guide me (as an answer)?
– Itai Shmida
Dec 31 '18 at 11:19
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
If you enable external sharing you can restrict the objects using private sharing settings - I'll edit into my answer.
– Dave Humm
Dec 31 '18 at 11:29
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
@DaveHumm I have customer community login licenses, and I use sharing set to allow these users for records, but it seems that the user can access all records in the community from this url. I did not understand from your answer what exactly should I do
– Itai Shmida
Dec 31 '18 at 12:04
|
show 1 more comment
Every community user has a profile. The trick is to edit that profile and remove the read access to that object at profile level. Once the read access is invoked, the User even if they have access to record they wont be able to access the content via URL hacking or directly hitting the Salesforce Rest Endpoint(Community user is API enabled, so it can hit the SF rest endpoint and access data of records which you haven't' provided access via UI)
You can find the profile of community member under
Communities -> Workspaces -> Member > Selected profile.
Once you get profile name, edit that profile like the way you do it normally and edit the FLS and Object setting to not even have read permission
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
add a comment |
Every community user has a profile. The trick is to edit that profile and remove the read access to that object at profile level. Once the read access is invoked, the User even if they have access to record they wont be able to access the content via URL hacking or directly hitting the Salesforce Rest Endpoint(Community user is API enabled, so it can hit the SF rest endpoint and access data of records which you haven't' provided access via UI)
You can find the profile of community member under
Communities -> Workspaces -> Member > Selected profile.
Once you get profile name, edit that profile like the way you do it normally and edit the FLS and Object setting to not even have read permission
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
add a comment |
Every community user has a profile. The trick is to edit that profile and remove the read access to that object at profile level. Once the read access is invoked, the User even if they have access to record they wont be able to access the content via URL hacking or directly hitting the Salesforce Rest Endpoint(Community user is API enabled, so it can hit the SF rest endpoint and access data of records which you haven't' provided access via UI)
You can find the profile of community member under
Communities -> Workspaces -> Member > Selected profile.
Once you get profile name, edit that profile like the way you do it normally and edit the FLS and Object setting to not even have read permission
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
Every community user has a profile. The trick is to edit that profile and remove the read access to that object at profile level. Once the read access is invoked, the User even if they have access to record they wont be able to access the content via URL hacking or directly hitting the Salesforce Rest Endpoint(Community user is API enabled, so it can hit the SF rest endpoint and access data of records which you haven't' provided access via UI)
You can find the profile of community member under
Communities -> Workspaces -> Member > Selected profile.
Once you get profile name, edit that profile like the way you do it normally and edit the FLS and Object setting to not even have read permission
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
answered Dec 31 '18 at 16:24
Pranay JaiswalPranay Jaiswal
16.9k32755
16.9k32755
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245058%2flightning-community-how-to-hide-disable-remove-generic-record-pages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
