Feature · Context Profiles
The right knowledge for the right team
Organization-scoped profiles that bundle RAG sources and control exactly who can ask what.
Owners, admins and superadmins create, update, archive and assign profiles, by individual user or by organization role (owner, admin, billing, developer, user).
Listings are caller-scoped, so non-admins only see active profiles they own or are assigned to.
Every chat request that names a profile passes an access gate before any quota or retrieval work begins, access is enforced, not assumed.
Role & user assignment
Assign by individual user or organization role.
Archive / unarchive
Retire old profiles without deleting their history.
Per-query access gate
Every request checked before retrieval or quota work.
Caller-scoped listing
Non-admins only see active profiles they can access.
Source bundling
Group sources into role-specific knowledge sets.
Org-scoped by default
Profiles live at the organization level, not the user.
Frequently asked
Context Profiles — questions we hear
Who can create or manage profiles?
Owners, admins and superadmins. They can assign profiles by individual user or by organization role.
Does everyone see every profile?
No, listings are caller-scoped, so people only see active profiles they own or are assigned to.
How is access actually enforced?
Every chat request that names a profile passes an access gate before any retrieval or quota work begins.
Related reading
Keep learning
See Modly on your own knowledge
Request a demo, or join the waitlist for early access.