Team Management
Control who has access to your organization and individual projects with a two-level, role-based permission system.
Overview
DYPAI uses a two-level access model that separates organization-wide permissions from project-specific access. This lets you give team members broad dashboard access while keeping individual project resources locked down.
- Organization members — Users who belong to the organization and can access the dashboard, billing, and shared resources
- Project users — Members assigned to specific projects with granular, project-level roles
A user must first be an organization member before they can be added to any project. Organization membership is the prerequisite for all project access.
Access Model
| Level | Scope | Controls access to | Managed in |
|---|---|---|---|
| Organization | Entire organization | Dashboard, billing, members, project list | Members |
| Project | Single project | API, Database, Storage, Auth, Metrics, Console, Credentials, Versions, Settings | Project Users |
Roles Summary
Organization Roles
| Role | Weight | Capabilities |
|---|---|---|
| Owner | 100 | Full control: billing, member management, delete organization, all project access |
| Admin | 80 | Manage projects, invite/remove members, access settings and billing |
| Normal | 50 | View and access only projects they are explicitly assigned to |
Project Roles
Project-level roles are configured per project and determine which dashboard sections a user can access. Each section has a minimum weight threshold and a set of allowed roles.
Organization roles and project roles are independent. An organization Admin still needs to be explicitly added to a project to access its resources, unless they are the Owner.
How It Works
Here's how the two levels interact in practice:
- An Owner creates an organization and invites team members
- Each member gets an organization role (Admin or Normal)
- The Owner or Admin creates projects within the organization
- Team members are added to specific projects with project-level roles
- Each project-level role controls which sections that user can see and interact with
Team Roles vs. Auth Roles
It's important to distinguish between team roles (managed here) andauthentication roles (managed in the Auth section):
| Aspect | Team Roles | Auth Roles |
|---|---|---|
| Purpose | Control dashboard access for your team | Control API access for your app's end users |
| Scope | Organization & project dashboard | API endpoints & database (RLS) |
| Managed in | Team > Members / Project Users | Auth > Roles |
| Used by | Developers, admins, team members | End users of your application |