Skip to main content

Documentation Index

Fetch the complete documentation index at: https://doc.rapida.ai/llms.txt

Use this file to discover all available pages before exploring further.

Rapida uses a two-level hierarchy to organize access and resources: Organizations at the top level, and Projects within each organization. Every user account belongs to an organization and can be a member of one or more projects within it.

​
Hierarchy

Organization
└── Project A
│   ├── Assistants
│   ├── Endpoints
│   ├── Knowledge Bases
│   └── Members (with project roles)
└── Project B
    └── ...

​
Key Concepts

Organizations

The top-level entity. An organization owns all projects, billing, and organization-wide members.

Projects

Isolated containers for assistants, endpoints, and knowledge bases. Each project has its own credentials and member roles.

Roles & Permissions

Fine-grained access control at the project level. A user can hold different roles across different projects.

Users & Teams

Invite team members to your organization or specific projects and assign them the appropriate role.

​
Role Summary

RoleScopeCapabilities
Super AdminProjectFull control — manage resources, settings, and members
AdminProjectManage resources and invite collaborators
MemberProjectCreate and use project resources
ViewerProjectRead-only access
Organization admins can create and archive projects but do not automatically inherit project-level admin rights.