Access and Search Visibility
#Members and active memberships
Add the restriction tag to the page whose content needs to be restricted.
| Page tag | Who can view the page content |
|---|---|
restrict:members |
Someone signed in with an active NationBuilder membership or a person tag containing member:. |
restrict:membership |
Someone signed in with an active NationBuilder membership. A member: person tag alone is not enough. |
| Both tags | An active membership is required. |
members only is an older alias for restrict:members. Use the current spelling on new pages.
Page tags configure content. Person tags are managed on records under People. Adding restrict:members to a page does not create a membership, take a payment or assign a person tag. Membership types, expiry dates and signup workflows need their own configuration.
A visitor who does not qualify sees an access notice instead of the restricted page content, with sign-in or joining links. Cards pointing at restricted pages can still show their public heading, summary and image; the card links to the joining page for a visitor without access. Keep private information out of these teasers.
Restrictions need checking at every destination
Restrictions are not inherited by subpages. Apply the appropriate tag to each standalone destination that needs it.
The current theme does not check every ordinary module's restriction separately when embedding it into a public subpage_layout parent. To restrict an assembled page, restrict the parent landing page. Do not rely on a restriction tag on a text, hero or accordion child to hide that section inside an otherwise public parent. The gallery does check access to its items individually.
Use private browsing to check the logged-out view, then test a signed-in member and a person without the required membership. Page tags do not establish access controls for a directly linked uploaded file; ask For Purpose before publishing documents that need protected downloads.
Keeping component URLs out of search engines
Add page_no_robots to a page that should not have its own search-engine listing, such as a module record used only as part of a landing page. The checked theme supplies no-index instructions and excludes tagged entries from its generated sitemap output.
Keep a public landing page indexable unless there is a specific reason to hide it. Search engines may take time to process changes. page_no_robots is a search instruction, not password protection; the page can still be opened directly.
hide_from_search_results is present as a legacy check, but its current branch does not add a working SearchIQ exclusion. Do not rely on it to hide a result. Confirm any internal-search requirement with For Purpose.
Changing top navigation or supporter navigation changes where content appears on the site; it does not by itself secure the content or remove an existing search-engine listing.