GroupsPersonal vs shared work

Personal vs shared work

Learn when work should stay in your private Group and when it belongs in a shared Group with teammates.

Giga separates personal work from shared work through Groups.

Every member has an existing private Group for work that should stay personal. Shared Groups give teammates a common access scope for Tracks, Agents, files, credentials, and other resources they need to work with together.

Personal work

Use your private Group when the work should stay with you.

Good examples include:

  • private notes or research
  • early thinking that is not ready to share
  • a personal Track
  • experiments or drafts that only you need
  • context that should not be available to a broader team

You generally do not need to create another Group just to make a Track private. Put the Track in your existing private Group.

Private work already has a home

Each member has a private Group. Use it as the default placement for work that should remain personal.

Shared work

Use a shared Group when several people need access to the same work.

A shared Group can provide a common home for:

  • team or department Tracks
  • shared Agents
  • files and work product
  • credentials and connected access
  • Group-level instructions or context

The Group defines the broader access boundary, while each Track keeps its own subject-specific context and history.

Personal vs shared at a glance

Personal workShared work
Lives in your private GroupLives in an appropriate shared Group
Intended for youIntended for teammates with Group access
Good for private Tracks, drafts, and experimentsGood for team Tracks, shared Agents, and reusable resources
Keeps personal context separate from team workGives collaborators a common context and access scope

Choosing where work belongs

Ask one simple question:

Who should be able to use this context later?

If the answer is only you, use your private Group.

If a team needs to return to the same Track, files, or shared resources, place the work in a shared Group that contains the right people.

Moving from personal thinking to shared work

Work often starts privately and becomes collaborative later.

For example, you might begin researching a new initiative in your private Group. Once the team decides to pursue it, the ongoing work should live in an appropriate shared Group so everyone can work from the same context.

The important part is the access boundary around the work. Giga should use the live workspace state to determine which Groups you can access and where shared resources belong.

Choose the audience deliberately

Group placement affects who can access the Tracks, files, context, and other resources inside it. Sensitive work should stay in the appropriate private scope.

A simple example

Imagine you are exploring a new pricing strategy.

Access is permission-aware

Giga should never assume that a person can see a Group or the work inside it.

The live workspace is the source of truth for:

  • which Groups a member can access
  • which Tracks are visible to them
  • which shared credentials or resources are available
  • what actions their current permissions allow

Learn about members and access →

Image placeholder

Split illustration showing a private Group on one side and a shared Group with several teammates on the other.