Logo IconNavigator
Core Concepts

Understanding Navigator's Hierarchy

How organizations, teams, projects, and chats work together

Navigator uses a clear organizational hierarchy to help you structure your work and control access. Think of it like a filing system for your AI-powered workspace.

The Four Levels

🏢 Organization
👥 Teams
📁 Projects
💬 Chats

1. Organization

Your top-level workspace

An organization represents your company or primary workspace. It's where:

  • Billing is managed
  • Company-wide settings are configured
  • Users are invited and managed
  • Global integrations are set up

Key features:

  • Single sign-on (SSO) authentication
  • Multi-organization support (users can belong to multiple orgs)
  • Admin and member roles
  • Centralized billing

2. Teams

Groups within your organization

Teams help you organize people and work. Each team can have:

  • Multiple members with different roles
  • Shared projects and resources
  • Team-specific settings

Types of teams:

  • Personal teams: Automatically created for each user
  • Shared teams: Created for departments, projects, or any grouping

Example teams:

  • Engineering Team
  • Marketing Team
  • Executive Team
  • Client Project Teams

3. Projects

Specific work areas within teams

Projects organize related chats and resources. They:

  • Group related AI conversations
  • Connect specific data sources
  • Control access at a granular level
  • Can be personal or shared

Use cases:

  • Q4 Marketing Campaign
  • Product Launch Analysis
  • Customer Research
  • Personal Notes

4. Chats

Individual AI conversations

Chats are where the magic happens. Each chat:

  • Contains a full conversation history
  • Can access connected data sources
  • Supports file uploads and attachments
  • Can be private or shared with collaborators

Permission Inheritance

Permissions flow down the hierarchy:

Organization Admin
    ↓ Can manage everything
Team Admin
    ↓ Can manage team and below
Project Member
    ↓ Can access project chats
Chat Collaborator
    → Can access specific chat

Best Practices

Organizing Your Workspace

  1. Use teams for departments or long-term groups

    • Create teams that mirror your organization structure
    • Keep personal work in your personal team
  2. Create projects for specific initiatives

    • Time-bound projects (Q1 Planning)
    • Ongoing areas (Customer Support)
    • Topic-specific work (Competitive Analysis)
  3. Keep chats focused

    • One topic per chat
    • Use descriptive titles
    • Archive completed chats

Access Control

  • Organization level: Who can join your workspace
  • Team level: Who can see and create projects
  • Project level: Who can access chats and data
  • Chat level: Individual collaboration permissions

Examples in Action

Marketing Department Setup

Navigator Organization
└── Marketing Team
    ├── Content Strategy Project
    │   ├── Blog Planning Chat
    │   ├── SEO Research Chat
    │   └── Competitor Analysis Chat
    └── Campaign Management Project
        ├── Q4 Campaign Chat
        └── Email Marketing Chat

Personal Workspace

Navigator Organization
└── John's Personal Team
    ├── Learning Project
    │   ├── AI Concepts Chat
    │   └── Python Notes Chat
    └── Side Projects
        ├── App Ideas Chat
        └── Investment Research Chat

Next Steps

Now that you understand the hierarchy: