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
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
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
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 1 hour ago
Itai Shmida
2,69311843
2,69311843
add a comment |
add a comment |
1 Answer
1
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.
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.
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
1 Answer
1
active
oldest
votes
1 Answer
1
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.
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.
add a 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.
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.
add a 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.
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.
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.
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.
answered 37 mins ago
Dave Humm
4,51451329
4,51451329
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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