No there is no security. You did everything fine
When you open following item:
/sitecore/templates/Feature/Experience Accelerator/Navigation/Rendering Parameters/Navigation/Navigation Settings/NavigationRoot you will notice that inside Source field there is following token
This token should be resolved to start item of your site. Nothing else special here, standard Droptree field with dynamic source
My theory is that you created your site on SXA 1.0.
There was an issue in site scaffolding and not all fields were populated correctly.
Navigate to your site definition item (
/sitecore/content/Group/Tenant/site/Settings/Site Grouping/site) and make sure that Start Item field is set.
I suppose that in your case it is not, thus you can see not your Home item but default Sitecore Home item because
$home token in Navigation Rendering Parameters was incorrectly resolved.
You can also notice that by looking at the Home item icon as well. SXA home template icon is slightly different.
In SXA 1.1 this issue has been resolved and you no longer need to define Star Item manually.
This solution is for people who could not solve their issue with the solution provided above.
There is some rare case when, even if you have got everything configured properly your site is resolved incorrectly, thus some functionalities might not work as expected (navigation is a great example).
How do I know if I am experiencing that extra case
Assuming that you configured everything like I described above and you open a page using Experience Editor button from Content Editor and gets
sc_site query parameter with website value or value different than your site definition item name then you've got a problem.
How to mitigate this:
To mitigate that issue you have to reconfigure standard Sitecore website a little bit. What we want is rootPath property cannot be a substring of any other SXA based sites rootPath.
Default value is
rootPath="/sitecore/content" and we need to make it more unique, for example
Then you have to create any item under
/sitecore/content and move default Sitecore Home item there.
This is a workaround for a small issue that we've found with @keith-vanderveen in site info resolution logic.
This issue should be fixed in the next release of SXA.
SXA 1.0, SXA 1.1