Like others before me, I would like to restrict my community users to only viusalforce pages. Most of the questions regarding this seem a bit dated. Are there any new and improved ways to deal with this?

Relevant other questions

These solutions are based on:

  • Overwrite all standard page links, and have a controller figure out where the community user should go.
  • Use javascript to redirect community users away from standard page urls.
  • Create new page layouts that minimize what is visible.
  • Restrict read access to all fields, and use an apex class with the without sharing keyword to make information available as needed.
  • What community template are you using?
    – Raul
    Mar 28, 2017 at 15:01
  • Salesforce Tabs + Visualforce. But i really don't want the tabs ;)
    – Kasper
    Mar 28, 2017 at 15:09
  • If you use something like Bootstrap you can have all the navigation handled via VF pages with a home page component then the other parts navigated to from that home page and say a sidebar component.
    – Dave Humm
    Mar 28, 2017 at 15:12
  • @DaveHumm Thanks, I did that. Is there an easy way to prevent people from hacking the url?
    – Kasper
    Mar 28, 2017 at 15:18

1 Answer 1


You have pretty much sum it all.

Here are few additional points:

  1. Brand communities:

    • Customize look and feel.
    • By placing HTML file in header, customize look and feel as per the requirement.
  2. Use template:

    • to reuse header navigation and footer functionalities.
  3. Standard pages:

    • Override standard buttons such as view, edit and new record pages, and list views with custom pages if necessary.
    • For custom pages try reusing the functionality as much as possible with use of field sets.
  • Thank you for your addition. Too bad nothing has changed ;)
    – Kasper
    Mar 30, 2017 at 16:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .