# Permissions

# Permissions

Permissions determine what users can see and do inside a Curiosity Workspace. This includes:

• visibility of nodes/documents in search results
• access to admin functionality (configuration, tokens, endpoints)
• ability to run endpoints and tasks

# Principles

• Least privilege: grant only what is needed for the role.
• Separation of duties: keep admin and developer privileges separate in production.
• Permission-aware retrieval: search and AI workflows must respect visibility rules.

# Common roles (conceptual)

• Admin
  • manage workspace configuration, tokens, endpoints, indexing, and deployments
• Developer
  • build connectors/endpoints/interfaces (often in dev/staging environments)
• User
  • search, browse, and use apps without administrative access

Your organization may define additional roles and group mappings.

# Where permissions matter most

• Search: users must not retrieve nodes they cannot access.
• AI: LLM grounding must only use content the user is authorized to see.
• Endpoints: endpoints should validate the caller and enforce appropriate authorization.

# Practical guidance

• Define your security model before production ingestion.
• Prefer permission checks in endpoints for complex operations.
• Audit access for:
  • admin actions
  • token usage
  • endpoint calls

# Technical Deep Dive

For a detailed explanation of the underlying graph model, ReBAC implementation, and enforcement mechanisms, see:

• Access Control Model (Deep Dive)

# Next steps

• Secure deployment patterns: Security
• Understand operational monitoring: Monitoring