Skip to main content
Groups are the fundamental organizational units in Paradigm that control access to workspaces and resources.

​
What are Groups?

A Group in Paradigm is a group of users that :
  • Determine resource access (workspaces, agents, tools)
  • Could link users and give access to workspaces through group membership

​
Architecture

Users
  ↓
Groups (member : controls access)
  ↓
Workspace (organizational container)
  ↓
Collection (document storage)
  ↓
Documents

​
Key relationships

  1. Group → Members: A group contains users
  2. Group → Workspaces: A group grants access to one or more workspaces
  3. Workspace → Group: Each workspace is associated with exactly one group
  4. User → Multiple Groups: Users can be members of multiple groups
Key Concept: Instead of granting workspace access to individual users one-by-one, you add users to groups, then give groups access to workspaces. When a user joins a group, they automatically inherit access to all workspaces that group can access. Why Groups Matter:
  • Scalability: Manage access for groups instead of individuals
  • Maintainability: Update once (group membership) instead of updating every workspace
  • Organization: Mirror your company structure (departments, projects, functions)

​
Group Types

Paradigm has three distinct group types, each with specific creation rules and use cases:

​
1. Company Group

Automatic group including all company members Characteristics:
  • Automatically created when a company is created
  • Includes ALL company users automatically
  • Cannot be deleted - exists as long as the company exists
  • Membership is automatic - users added when they join the company
  • Exactly one per company
Use cases:
  • Company-wide shared resources
  • General documentation accessible to all employees

​
2. Private Group

Personal group for individual user resources Characteristics:
  • Automatically created when a user joins
  • Single member only - the user who owns it
  • Cannot be deleted - exists while user account exists
  • Cannot add other members - strictly personal
  • Exactly one per user
Use cases:
  • Private agent configurations
  • Personal workspace isolation

​
3. Custom Group

Manually created groups for specific groups Characteristics:
  • Manually created by Admins through Admin Panel
  • Custom membership - Admins explicitly add/remove members
  • Can be deleted by Admins
  • Flexible membership - any number of users
  • Can be SCIM-synced with external groups
Use cases:
  • Project groups (“Project Phoenix Group”)
  • Departmental groups (“Engineering”, “Sales”, “Product”)
  • Cross-functional workgroups (“Security Committee”)
  • Client-specific groups (“Client ABC Group”)
  • Temporary collaboration groups

​
Type comparison

TypeCreationMembersManagementDeletion
CompanyAutomaticAll company usersAutomaticNever
PrivateAutomaticSingle user (owner)AutomaticNever
CustomManual (Admin)Selected usersAdmin PanelYes (Admin)