Skip to main content

​
Overview

An Organization is a unit for sharing knowledge across teams. Invite members for collaboration and implement role-based access control.

​
Personal vs Organization Use

Neuradex supports two usage patterns.
PatternDescriptionBest For
PersonalOwn projects directly without an organizationIndividual development, testing
OrganizationCreate an organization and share with membersTeam development, enterprise use

​
Roles and Permissions

Organizations have three roles, each with different permissions.
RolePermissions
OwnerDelete organization, change member roles, all operations
AdminInvite/remove members, manage projects
MemberAccess projects, manage knowledge
The user who creates an organization automatically becomes the Owner. At least one Owner is required.

​
Inviting Members

Members are added via email invitation.
  1. Admin or Owner creates an invitation with an email address
  2. An email is sent to the invitee
  3. Invitee clicks the link to confirm
  4. Added as an organization member
This approach prevents accidental additions and confirms the invitee’s intent.

​
Data Isolation

Data between organizations is completely isolated.
  • Organization A’s knowledge is inaccessible from Organization B
  • Further isolation by project within an organization
  • Personal projects are inaccessible to other users
Deleting an organization removes all projects and knowledge belonging to it. This action cannot be undone.

​
Organization Structure

Organization
├── Members
│   ├── Owner (1 or more)
│   ├── Admin
│   └── Member
└── Projects
    ├── Project A
    ├── Project B
    └── ...

​
Next Steps

Project

Separate knowledge by purpose

Quickstart

Create your first project