Manage your team with Organizations, Projects, user roles, and permissions for secure collaboration.

User Management

AngenAI uses Organizations and Projects to structure teams and control access. This guide covers user roles, permissions, and team management.

Organization Structure

Organizations

An Organization is the top-level container for your AngenAI usage:

Contains one or more Projects
Has its own team of members
Manages billing and subscriptions
Has a unique URL identifier (slug)

Projects

Projects exist within Organizations:

Represent individual codebases or applications
Have their own Source Folder configuration
Can have project-specific members
Contain Work Items, Media, and project-scoped content

Hierarchy

Organization (e.g., "Acme Corp")
├── Project A (e.g., "Web App")
│   ├── Work Items
│   ├── Media Library
│   └── Project-scoped Knowledge/Personalities/Meetings
├── Project B (e.g., "Mobile App")
│   └── ...
└── Organization-wide Knowledge/Personalities/Meetings

User Roles

AngenAI has four user roles with different permission levels:

Owner

Full control over the organization.

Permissions:

All Admin permissions
Delete the organization
Transfer ownership
Manage billing and subscriptions

Each organization has exactly one Owner. Ownership can be transferred to another Admin.

Admin

Manage the organization and its members.

Permissions:

All Member permissions
Invite and remove members
Change member roles (except Owner)
Create and delete projects
Create and modify organization-wide content
Manage organization settings

Member

Standard access for team members.

Permissions:

All Viewer permissions
Create and manage Work Items
Create project-scoped Knowledge, Personalities, and Meetings
Upload to Media Library
Apply generated code to projects

Limitations:

Cannot create or modify organization-wide content
Cannot invite or manage other members
Cannot create or delete projects

Viewer

Read-only access.

Permissions:

View Work Items and their generated code
View Knowledge, Personalities, and Meetings
View Media Library

Limitations:

Cannot create or modify any content
Cannot generate code
Cannot apply changes

Managing Members

Inviting Members

Go to Settings > Organizations
Select your organization
Click the Members tab
Click Invite Member
Enter the email address
Select a role (Admin, Member, or Viewer)
Click Send Invitation

The invitee receives an email with a link to join your organization.

Pending Invitations

View and manage pending invitations:

Go to Settings > Organizations > Members
See the Pending Invitations section
Cancel invitations if needed

Changing Member Roles

Go to Settings > Organizations > Members
Find the member in the list
Click the role dropdown
Select the new role
Confirm the change

Note: Only Owners can change Admin roles. Admins can change Member and Viewer roles.

Removing Members

Go to Settings > Organizations > Members
Find the member to remove
Click Remove
Confirm removal

Removed members immediately lose access to the organization and all its projects.

Content Scope Permissions

Different roles have different access to content based on scope:

Content Type	Organization-Wide	Project-Scoped
View	All roles	All roles
Create	Owner, Admin	Owner, Admin, Member
Edit	Owner, Admin	Owner, Admin, Member (own content)
Delete	Owner, Admin	Owner, Admin, Member (own content)
Move to Org	Owner, Admin	Owner, Admin

Organization-Wide Content

Only Owners and Admins can:

Create Knowledge articles at organization level
Create Personalities at organization level
Create Meetings at organization level
Move content from project to organization scope

Project-Scoped Content

Members can:

Create content within projects
Edit their own content
Delete their own content

Admins and Owners can edit and delete all project content.

Project Access

Project Membership

By default, all organization members can access all projects. Project-specific restrictions can be configured if needed.

Source Folder Access

Each user configures their own Source Folder path for projects. This allows:

Different team members to have code in different locations
Local development environments on different machines
Personal folder structures

Note: Source Folder paths are stored per-user and not shared with the team.

Team Setup Best Practices

Small Teams (2-5 people)

One Owner (typically team lead)
All others as Members
Use organization-wide content for shared standards

Medium Teams (5-20 people)

One Owner
1-2 Admins for team management
Most as Members
Consider Viewer role for stakeholders who need visibility

Large Organizations (20+ people)

One Owner
Multiple Admins across different areas
Members for active developers
Viewers for managers, QA, or external stakeholders
Separate projects for different teams or applications

Role Assignment Guidelines

Role	Assign To
Owner	Team lead or organization creator
Admin	Tech leads, senior developers, team managers
Member	Active developers, contributors
Viewer	Stakeholders, QA (read-only), temporary access