Above projects and tasks sit two more nouns: the organization and the team. They decide who you work alongside, where your projects live, and who pays.
Organization
Your organization is the top of the structure. It’s created when you sign up — and you become its admin.
The organization is the billing and access boundary. It holds:
- Credits and balance — one balance funds every project in the organization.
- Members — the people who can sign in and work.
- Integrations — the GitHub connection your projects draw repositories from.
- Its own name and logo, which you can change under Settings.
Everything else in DIJJI.ai belongs, directly or indirectly, to one organization.
Team
A team is a group inside the organization. Its job is to organize members and the projects they work on.
When your organization is created, a team named General is created automatically and you’re added to it. Most organizations can run on the General team alone. Create more teams (an admin task, under Settings) when separate groups of people work on separate sets of projects and you’d rather they didn’t share one list.
You can rename or delete a team you’ve created. The General team can be renamed but not deleted — it’s the fallback every organization keeps.
How projects belong to teams
Every project lives in exactly one team. You choose that team when you create the project.
The project list groups projects by team — each team gets its own heading, with its projects below. When your projects span more than one team, an All teams filter appears at the top, alongside one tab per team. It’s view-only and starts on All teams: switch to a single team to hide the rest, but it never changes which projects exist. So a team is, in practice, the set of projects a group of people share.
Members and team membership
These are two separate things, and the difference matters:
- Organization membership makes someone part of your organization and gives them a role — admin or member. This is what an invite grants.
- Team membership adds an existing organization member to a specific team, so they see that team’s projects.
Being in the organization doesn’t put you in every team. An admin adds members to teams under Settings. Roles, by contrast, are set once at the organization level — a person is an admin or a member everywhere, not per team.
What’s organization-wide, what’s team-wide
| Lives at the organization | Lives at the team |
|---|---|
| Credits, balance, spending limits | Projects |
| The member list and invites | Team membership |
| Integrations | — |
| Organization name and logo | Team name and description |
Organization — billing, members, integrations
└── Team — a group of members and their projects
└── Project — one repository's worth of work
Once the structure is clear, Projects, tasks, and runs covers the work itself.