Overview of Teams/Projects

Teams and Projects Are the Same

RebelOps treats a team and a project as the same core entity. You can call it a team for people-focused work or a project for delivery-focused work—the data model is identical.

This keeps navigation simple: whenever you see “team” or “project,” you are working within the same scoped workspace.

Nested Structure for Real-World Hierarchies

• Create parent teams/projects to represent departments, client portfolios, or programs.
• Add child teams/projects for squads, initiatives, or deliverables.
• Each level keeps its own chat, files, and extension data while still being grouped under the parent.

Members and Supervisors

Teams/projects can have members assigned directly, along with supervisors who oversee activity and coordination. This lets leadership stay aligned without joining every conversation.

Organization roles still apply; supervisors complement the organization role system by shaping visibility and accountability for each team/project.

Scoped Chat, Files, and Extensions

• Chat stays inside the selected team/project so conversations never bleed into unrelated work.
• Files are scoped to the team/project and show related context when you browse or search.
• Extensions are attached to the selected team/project, keeping integrations focused on that workstream.

Some extensions, like Tasks, can surface nested data so parent teams/projects can roll up work from child spaces.

Tips for Organizing Teams/Projects

• Use a consistent naming pattern so teams/projects sort together in the sidebar.
• Create a top-level “Operations” or “All Teams” space to hold shared announcements and resources.
• Keep extensions lightweight at the parent level and add specialized extensions inside child teams/projects.
• Switch the active team/project before sending messages or uploading files to ensure the data is stored in the right scope.

Need Help?

If you want help designing your team/project hierarchy, open live chat support to reach an agent.