Share a space #

View this page as Markdown

Prompt:

Give Dana access to our tzTrack space so her sessions see the same issues.

Also works: "Share the issue space with the team." "Who is on our tzTrack space?" "Take Sam off our tzTrack space."

What your tool does #

  • Asks you for each person's email address, the one their Turn Zero account signs in with, and the level to give them.
  • Calls share with the action add for each person, with the address their account signs in with.
  • Tells you to have each person sign in once, with their own account, through their own AI tool.
  • Checks that the project's setting file gives the space, so each member's sessions connect to it.
  • Calls share with the action list to answer who is on the space, and with remove to take a member off once you agree.

What you need #

  • To own the space. Only the owner shares it.
  • Each person's email address, as their Turn Zero account signs in with it.
  • Each person's own Turn Zero account. A person without one creates one; while sign-ups are closed, Turn Zero invites them. No account holder invites another.

Before your AI starts #

This section is for your AI coding tool: what it checks and gathers before it begins. You don't need to do these steps yourself.

  • That your person owns the space. Only the owner shares it.
  • Each person's email address, from your person. Never guess one.
  • The level for each person: report, to raise, find, and read issues; contribute, to work issues as well; or owner, every act on the space's issues, closing and reopening them among it. share gives contribute when no level is given.
  • Whether .tztrack/config.json gives the space. If it does not, follow Name your space in a setting file first.

Steps #

1. Add each person #

Call share with the action add, the person's email, and their level. If no Turn Zero account signs in with the address, the call is refused no_such_account, and nothing is kept. Ask your person to check the address, or to have the person create an account first, then add them again. The answer lists the members, each with their account, email address, level, and when they were added, and users, the members plus the owner.

2. Each person signs in #

Each person connects their own AI tool to tzTrack and signs in once with their own account, as Connect your AI tool describes. A member who holds no space of their own and one shared space works that space without passing it in calls.

3. The setting file connects them #

The committed setting file gives the shared space. A member's session working in the project reads it, and works the same space as yours, at the level you gave.

A member working in Claude or ChatGPT never reads the file, since those apps do not read files on your computer. If the shared space is their only space, they work it without passing it. Otherwise their AI passes the space in its calls.

4. Read who is on the space #

Call share with the action list to answer the members and users, the count of members plus the owner.

5. Remove a member #

At your person's word, call share with the action remove and the member's email. Their sessions are refused at their next call on the space.

Expected result #

Each member's sessions read and raise issues in the same space as yours, at the level you gave. An issue can wait for one member, with its waiting for set to person:<account>. Feedback to Turn Zero about your space stays yours alone.

Refusals #

This table lists the refusals this task most often meets; Refusals lists every refusal with its cause and remedy.

Refusal Status Cause Remedy
no_such_account 404 No Turn Zero account signs in with the email address, so nothing was kept. Check the address, or have the person create an account first, then add them again.
space_not_owned 403 The space named is not one your account holds, so you cannot share it. Share a space your account owns.
credential_required 401 The call carried no sign-in, or the sign-in did not finish. Sign in again through your tool.