Reference

Roles and permissions

DIJJI.ai has two roles: admin and member. This page lists every permission-gated action and the role it requires. For what the roles mean and where the difference shows on screen, see the Roles: admin and member concept page.

The rule of thumb: money, people, integrations, and organization settings are admin-only; the delivery work is open to everyone. A ✓ means the role can perform the action.

Billing

ActionAdminMember
View balance, spend, and runway✓✓
View transaction history✓✓
Set the daily spending limit✓—

Members

ActionAdminMember
View the member list and pending invites✓✓
Invite a new member✓—
Resend or revoke a pending invite✓—
Change a member’s role✓—
Remove a member✓—

Teams

ActionAdminMember
View teams and team members✓✓
Create a team✓—
Rename a team or edit its description✓—
Delete a team✓—
Add or remove a team’s members✓—

Organization

ActionAdminMember
View the organization profile✓✓
Edit the organization’s name and logo✓—
View the audit log✓—

Integrations

ActionAdminMember
View connected integrations✓✓
Connect GitHub or Jira✓—
Disconnect or reconnect an integration✓—
Add, change, or remove a Slack connection✓—

Projects and pipelines

ActionAdminMember
Create a project✓✓
Edit, pause, archive, or delete a project✓✓
Design and edit a pipeline✓✓

Tasks and runs

ActionAdminMember
Run a task✓✓
Approve or reject a plan✓✓
Answer a question a run is waiting on✓✓
Resume a run waiting on a gate or for payment✓✓
Trigger E2E tests✓✓
Cancel a run✓✓

A note on team scope

Roles decide what a person can do; teams decide which projects they see. A member sees and works on the projects of the teams they belong to. An admin sees every team’s projects regardless of team membership. Promoting a member to admin therefore widens both what they can do and what they can reach.

The viewer role

A read-only viewer role is planned for after launch. Until it ships, everyone is either an admin or a member — there is no way to grant view-only access today.