Cookies on Kythene

We use cookies and similar technologies for the things below. You can accept all, reject everything except what's essential, or pick what you're OK with.

Preferences
Theme, language, dismissals. Improves the experience but the site works without.
Improvement
Anonymous usage measurement so we can fix bugs and prioritise work.
Marketing
Lets us measure whether ads we run send people who actually use the site. We don't share personal data with advertisers.

Read our cookies policy and the privacy policy. California residents: Do Not Sell or Share My Personal Information.

Loading…
kythene
Open the app

Walkthrough: working with a client

Your team plus an outside collaborator - a contractor, an agency, or a client's own developer - who is outside your org and may be on a different stack. You want to share specific work with them, let them contribute and comment, and be certain nothing outside that scope leaks - and that when the engagement ends, their access ends cleanly while their contributions remain.

Scope with a project (tag) and a share code

Put the shared work behind its own project tag - say client-x - so only what carries that tag is in scope. Then mint a share code for that tag (from the Tags / sharing surface in the workspace). A share code is a pseudo-identity: it lets a named outsider in without an account, and it is scoped to exactly that tag.

Send the guest the link and the code. They can:

  • view the collections tagged client-x,
  • comment on them, and
  • approve them,

all for free - guests never consume a seat. Everything not tagged client-x stays invisible to them.

They contribute back, marked as external

Work the guest contributes comes in provenance-marked as external, so your team's instances can weigh it appropriately (it is a contribution from outside the trust boundary, not team-authored). Your own work continues in your other projects, untouched and unseen by the guest.

Revoke cleanly when it's over

When the engagement ends, revoke the share code. Access is cut immediately - the guest can no longer view the project, even if they still hold the link. Their contributed artifacts and comments remain part of the record; only their way in is gone. (Revocation is enforced server-side: a revoked code stops working at once, including for password-protected tags.)

Tips

  • One tag per engagement makes scope obvious and revocation total.
  • Because access is at the tag level, you can share a subset of a workspace without giving away the workspace.
  • The guest can be on any MCP-capable client, or none at all (the web view works without an account) - Kythene is vendor-neutral.
  • Need the guest's agent to read the scope over MCP, time-boxed access, or memory-topic scoping? That is on the roadmap - talk to us if you need it now.