Groups and Tracks
Learn how Groups provide the access boundary around work while Tracks keep individual projects, areas, and ongoing efforts organized.
Groups and Tracks work together to organize Giga.
A Group defines the broader access and placement scope. A Track holds one ongoing body of work inside that scope.
A simple way to think about it:
Group = who and where. Track = what.
The Group defines the audience around the work. The Track keeps the subject-specific context, memory, files, and history together.
How they fit together
Group
The broader container and access boundary for related work and resources.
Track
One ongoing project, area, client, or body of work that develops over time.
A shared Group can contain several Tracks, each with its own focus.
For example, a Marketing Group might contain:
- Q4 campaign
- Website redesign
- Customer research
- Content calendar
The same teammates can access the broader Group, while each Track keeps its own work organized separately.
Group vs Track
| Use a Group when you need… | Use a Track when you need… |
|---|---|
| A broader permission or placement boundary | An ongoing subject with continuity |
| A shared home for several related Tracks | Context and history for one project or area |
| A place for shared Agents, files, and credentials | Files and memory tied to one body of work |
| A private or shared audience | A focused place people can return to over time |
Creating a new project usually calls for a Track, rather than another Group.
Example: a Marketing team
Imagine a company with a Marketing Group.
Marketing Group
Gives the marketing team a shared access scope.
Website redesign
Keeps website strategy, files, decisions, and Chats together.
Q4 campaign
Keeps campaign planning and progress separate from the website work.
Marketing Agent
A reusable Agent can sit within the same broader Group scope.
The Group keeps the audience consistent. The Tracks keep each stream of work focused.
Example: private work
The same model applies to personal work.
Every member already has a private Group. You can create multiple private Tracks inside it, such as:
- Personal research
- Career planning
- Draft product ideas
You do not need a separate private Group for every Track.
Learn about personal vs shared work →
Track visibility follows the Group
In the current Giga model, a Track inherits its visibility from the Group it lives in.
That means:
- a Track in your private Group is personal to you
- a Track in a shared Group is available within that Group’s access scope
Because of this, choosing the right Group matters before you add sensitive Context Notes, Files, or other durable context.
Group placement is part of the permission model
When Giga creates a Track, it should use a Group the user can access. For private work, it should use the member’s existing private Group rather than creating a new one.
Context can exist at both levels
Giga can keep standing context at more than one level.
| Context level | Good for |
|---|---|
| Group | Instructions or context that should apply across the broader shared area |
| Track | Background and instructions specific to one ongoing body of work |
For example, a Customer Success Group could contain team-wide operating instructions, while an Acme renewal Track keeps the account-specific background and decisions.
This lets broad rules stay broad while project-specific context stays focused.
Keep the hierarchy useful
A clean structure usually has:
- a small number of meaningful Groups that reflect real access boundaries
- multiple Tracks inside those Groups for the actual ongoing work
- context, memory, Chats, and files attached to the appropriate Track
Avoid creating extra Groups just to organize individual projects. That creates more permission boundaries than the work actually needs.
Use Groups sparingly
A new Group should represent a real top-level container or access boundary. A new Track is usually the better choice for a new project, client, initiative, or area of work.
Image placeholder
Image placeholder
Hierarchy diagram showing Workspace → Marketing Group → several Tracks, with shared members and resources at the Group level.