Best Practices: Site Architecture

For general information on sites, check out this article.

Sites are the containers of information across your intranet, and are central to the Simpplr architecture. 

  • All content resides or exists within some site on Simpplr. 
  • Sites can be public, private, or unlisted. Sites are valuable because they help you organize your content and people into logical groups that your employees expect. 
  • Sites can be mandatory so that employees are automatically members of sites. 
  • Each site contains a dashboard, pages, events, albums and files to help you better organize information for employees. 


Before you build content, you'll need to create your site. Determine what audience your site will serve. Ask yourself, “Who should have access to this site? Will there be confidential information on this site? Will there be company-wide information on this site?” Define your site access before you build content. 

Things to consider for site creation:

  • Build content before you create your site dashboards. 
  • Determine content classifications and who will be responsible for the content on the site. 
  • Does the content require expert knowledge? Is the content evergreen? 
  • Who will be responsible for creating and maintaining content for this site? 
  • Am I going to upload files or am I going to link to files/integrate?
  • Define your file strategy for your sites. 
  • Utilize files and pages to house important documentation like policies, forms, and resources. 
  • Define parameters around your site feed and content feed.
  • Classify information as Knowledge when you're creating your pages and be sure to create a policy for validation within your content governance application settings. 

Pictured below you will find sample featured sites and a sample New Hire Onboarding site. 






Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • Question: Why doesn't the Subscription automatically add new folks who fall into the Audience parameters? Why do we either have to "re-run" subscriptions or make them "mandatory" in order for the auto-routine to work? The definitions of work are getting crossed here. It should be as such:

    1. Audience: A group of users sharing a demographic parameter.

    2. Subscription: One or more audiences assigned to a specific site. 

    3. Mandatory: Audience members cannot choose to discontinue the site Subscription. 

    The daily data file additions/changes and hourly Subscription alignment shouldn't be tied to the Mandatory field. If someone is in the Audience, they are added and become Subscribers. Done. 

    Am I understanding how this works?

    Comment actions Permalink
  • Hey Linda. Sorry to hear you're having trouble. Actually, the way you said it is exactly how subscriptions are supposed to work. Once assigned to an audience, the user will automatically be part of whatever subscription that has the audience in it. You shouldn't have to manually run any schedulers or anything. A mandatory subscription just means that users can't opt out of being a site member. If a subscription is NOT mandatory, users will still be added to it if they're part of the audience, but they have the option to remove themselves from the site membership. 

    It sounds to me like this is unexpected behavior. I'm going to suggest capturing the problem you're having in a screenshot or video clip, then opening a ticket with our Support team. I also did just confirm with the Product Manager around Subscriptions that there are some known issues effecting functionality currently. The team is already looking into this bug. 

    Comment actions Permalink

Please sign in to leave a comment.

Articles in this section

See more