Plan a SharePoint Online Intranet with Secure Permissions and Navigation
Question details
Plan a SharePoint Online intranet that separates private department content from organization-wide content while preserving navigation for visitors.

- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- An organization is designing an intranet with department-specific and organization-wide content connected through hub and site navigation.
- Observed behavior
- Visitors need access to the appropriate pages, assets, and navigation without gaining access to private department content.
List the audiences for each site and identify which content should be private or available organization-wide. Confirm that you have the permissions needed to review site and library access and edit navigation.
Design sites and permissions around content audiences
Use separate sites and groups to control department and organization-wide access before configuring navigation.
In your intranet plan, group organization-wide content separately from private department content. Use separate sites where audiences require different access.
Open each site and select Settings > Site permissions. Grant the appropriate groups visitor, member, or owner access, and limit private department sites to authorized users.
Associate relevant sites with the intended hub through Settings > Site information, if your administrator has made a hub available. Configure shared links from the hub navigation's Edit control.
Sign in with representative organization-wide and department visitor accounts. Open the hub and site navigation links, pages, and assets to confirm that each audience has the intended access.
Review Site Pages and Site Assets permissions
Use this review when visitors cannot open pages, see assets, or follow navigation after library permissions have changed.
Create Intranet Content with WPS Office
SharePoint permissions and navigation must be configured in SharePoint. For creating documents and presentations to share on your intranet, WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making migration easier.

Frequently Asked Questions
Should private department content be stored on a separate site?
A separate site is useful when a department needs a different audience from the rest of the organization. Set its access through Settings > Site permissions and grant access only to authorized groups.
Can I use navigation audience targeting to secure private content?
No. Audience targeting helps display relevant links, but it does not replace permissions. Restrict access on the destination site, library, or content itself.
Why can visitors see a link but not open the page?
The destination page or its site may have different permissions from the navigation. Check Settings > Site permissions and review unique permissions on the Site Pages library or the affected page.
Should Site Pages and Site Assets always inherit site permissions?
Not necessarily. Inheritance is often simpler to manage, but unique permissions may be intentional. Review the content and intended audience before changing either library's permissions.
Does joining a hub give everyone access to its associated sites?
No. Hub association connects sites for shared experiences such as navigation, but each site retains its own permissions. Check each site's access separately.




