Role Based Access

The help system controls which content is visible to each user based on their role. This applies to both the AI search results and the navigation.

Role Hierarchy

Content visibility follows a hierarchy where higher roles see everything below them:

| User Role | Sees Content From | |---|---| | Guest (unauthenticated) | guests/ | | Member (authenticated) | guests/, members/ | | Administrator | guests/, members/, admin/, fieldhelp/ | | Developer | guests/, members/, admin/, dev/, fieldhelp/ |

How Roles Are Determined

The system checks the current user's Contensive account properties:

• If the user is not authenticated, they are a guest.
• If the user is authenticated, they are a member.
• If the user has the Admin flag checked in their people record, they are an administrator.
• If the user has the Developer flag checked in their people record, they are a developer.

How Roles Are Assigned to Content

When help files are indexed for search, each chunk is tagged with a role based on its file path:

• Files in helpfiles/guests/ or helpfiles/{collection-name}/ are tagged as guest content.
• Files in helpfiles/members/ are tagged as member content.
• Files in helpfiles/admin/ are tagged as administrator content.
• Files in helpfiles/dev/ are tagged as developer content.
• Files in fieldhelp/ are tagged as fieldhelp content, visible to administrators and developers.

Field Help

The fieldhelp folder contains markdown files that document database tables and their fields. Each file describes one table. This content is intended for administrators and developers who need to understand the data structures behind the site. Field help files are included in search results for administrators and developers but are not visible to members or guests.