Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
Web workspace

Organization, members & teams

Give existing Gonu users the right workspace and project access.

Open OrganizationExplore the example

WHEN IT HELPS

Put it to work.

Set up a team pilot with clear ownership, limited project access and a read-only role for people who only need to inspect work.

Before you begin

  • A shared workspace and an owner/admin role for membership changes.
  • The person being added already has a Gonu account.

WALK THROUGH IT

See the workflow, step by step.

Interactive example

Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.

  1. Create/select the shared workspace in Projects. Open its Members view and enter an existing user’s email.

  2. Choose Developer or Viewer; only the owner can grant/remove administrator access. Confirm the access change before submitting.

  3. In Organization → Teams & access, create a team, add appropriate members and assign projects. Review restricted-project membership.

gonu / Organization, members & teamsSAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 3

Members / Example access request

WorkspaceExample engineering team
PersonAn existing Gonu account
DecisionConfirm that this person may access the workspace
Example only · your real screen shows your own data.
Step 1 of 3

THE USEFUL RESULT

What you should leave with.

Shared project context with server-enforced workspace/team permissions.

Know the boundaries.

  • Granting membership does not send an invitation email. The person must already have an account.
  • Team roles can restrict access but do not grant organization administrator powers. Workspace ownership is separate from platform administrator status.

IF SOMETHING DOESN’T WORK

A member cannot see the project.

Check workspace membership, team assignment and project restrictions. Review permissions instead of sending private content outside the workspace.

Contact support