Groups
Learn how Groups organize shared work, people, and access across Giga.
A Group is a top-level access and placement boundary in Giga.
Groups help organize who can access what. They can contain or scope Tracks, Agents, files, credentials, and other shared resources.
A Group is not a project or an AI worker. It is the broader container that gives related work a home and defines the audience around it.
What Groups are for
Organize shared work
Keep related Tracks and resources together under one broader area.
Control access
Give the right workspace members access to the work inside a shared Group.
Separate personal work
Use your existing private Group for work that should stay private to you.
Scope reusable resources
Groups can provide a shared home for resources such as Agents, files, and credentials.
Groups define the boundary around the work
Use a Group when you need a broader people or permission scope. Use a Track when you need an ongoing body of work with its own context and history.
Groups vs Tracks
Groups and Tracks work together, but they solve different problems.
| Group | Track |
|---|---|
| Defines a broader access and placement scope | Holds one ongoing project, area, client, or body of work |
| Can contain multiple Tracks and shared resources | Keeps subject-specific context, files, and memory together |
| Organizes who can access the work | Organizes what belongs to the work |
| Can be shared or private | Inherits its visibility from the Group it lives in |
For example, a Marketing Group might contain separate Tracks for Q4 campaign, Website redesign, and Customer research.
Learn more about Groups and Tracks →
Shared and private Groups
Every workspace member has access to shared Groups they belong to, plus their own private Group.
Shared Group
A shared access scope for teammates who need to work from the same resources and context.
Private Group
Your personal access scope for private Tracks and other work that should remain yours.
You generally do not need to create a new Group just to make a Track private. Put the Track in your existing private Group instead.
What can live in a Group?
Groups can act as the placement scope for several Giga primitives.
- Tracks for ongoing work with continuity
- Agents for reusable AI agents
- Files and other shared work product
- Credentials and connected access used through Giga
- Group-level instructions or context that should apply within that scope
The exact resources you can see or manage depend on the live workspace permissions available to you.
Live access is the source of truth
Group membership, workspace role, and resource permissions can change. Giga should check the current workspace state instead of assuming access from a hard-coded list.
When should you create a Group?
Create a new Group when you genuinely need a new top-level container or access boundary.
Good reasons include:
- a department needs its own shared area
- a client or business unit needs a distinct permission scope
- a set of Tracks and resources should be available to the same people
- work needs to be separated from other teams for access reasons
Avoid creating a new Group for every project. A Track is usually the better primitive for an individual project or ongoing effort.
A simple example
Imagine a company with a shared Sales Group.
Sales Group
Defines who on the team can access the shared sales area.
Pipeline review
A Track for ongoing pipeline analysis and decisions.
Enterprise accounts
A separate Track for work around strategic accounts.
Sales Agent
A reusable Agent that can live within the same shared access scope.
The Group keeps the shared audience consistent while each Track keeps its own work and history focused.
Image placeholder
Diagram showing one shared Group containing multiple Tracks, an Agent, files, and connected resources.
Managing members
Workspace admins can add existing workspace members to a shared Group.
Membership controls who can access that Group’s shared resources. Workspace membership and Group membership are separate steps, so someone must first exist in the workspace before they can be added to a shared Group.
Learn about members and access →