Every person in your organization holds one of two roles: admin or member. The role decides what they can change — money, people, and organization settings are admin-only; the everyday work of running tasks is open to everyone. This page covers what each role can do and where you’ll notice the difference.
The two roles
Admin is the role with full control. An admin manages billing, invites and removes people, changes roles, edits the organization’s profile, and creates and manages teams.
Member is the working role. A member does the actual delivery work — creating projects, designing pipelines, syncing issues, running tasks, and approving plans — but can’t manage money, people, or organization-level settings.
When you sign up and create an organization, you become its admin automatically. Everyone you invite after that is whatever role you pick for them — member by default, admin if you choose.
What only an admin can do
A member is fine for nearly all day-to-day work. These are the actions reserved for admins:
-
Billing. View the organization’s balance, monthly and daily spend, and runway; set the daily spending limit.
-
People. Invite new members, resend or revoke pending invitations, change someone’s role, and remove a member from the organization.
-
Teams. Create teams, rename them, edit descriptions, delete them, and add or remove people from a team.
-
Organization profile. Change the organization’s name and logo.
-
Audit history. View the audit log for the organization, teams, members, projects, tasks, and integrations.
-
Integrations. Connect GitHub or Jira, disconnect or reconnect an integration, and add or change a project’s Slack connection.
Everything else — projects, pipelines, tasks, and runs — is available to members and admins alike. Members can view connected integrations; only admins connect or change them.
Where you’ll see the difference
The role isn’t something you have to look up. The interface simply shows or hides controls based on it:
- The balance card. In the Organization scope of the Usage screen, an admin sees the full balance card — current balance, spend, and low-balance warnings. A member sees a placeholder in its place: “Ask an admin to manage credits for your organization.”
- The Members page. An admin sees the Invite button and, next to each person, a menu to change their role or remove them. A member sees the list but none of those controls.
- Organization settings. For an admin the name, logo, and daily-limit fields are editable with a save button. For a member the same fields are visible but disabled.
- Teams. The Create Team button and the edit, delete, and add-member controls appear only for admins.
Each person’s role is shown in the member list as a small badge — a violet Admin badge or a grey Member badge — so you can always see who holds what.
Changing someone’s role
Roles are changed on the Members page under Settings, and only an admin can do it. Open the menu next to a person and choose Change Role; it toggles them between admin and member. You set a role the same way when you first invite someone — the invitation dialog has a Role dropdown with Member and Admin.
A role applies across the whole organization. A person is an admin or a member everywhere — it isn’t set per team. Promote a member to admin and they can manage every team and the billing for all of them.
A note on the viewer role
DIJJI.ai today has exactly two roles. A read-only viewer role is planned for after launch; until it ships, anyone who needs access is either an admin or a member.
In short: member for people doing the work, admin for people who also manage money, people, and settings. If a control is missing, a member is looking at an admin-only action — the fix is to ask an admin, or to be made one.