Bring someone new onto the team's material
Use casesThe handbook already answers most of week one. It just is not where the new person — or their agent — is looking.
The situation
A new colleague spends their first week asking questions the handbook already answers. Once they have been granted access to a private vault, receiving it puts a local copy on their machine and indexes it, so their own agent answers from the team's material on day one. Accepting the GitHub invitation alone does not do that — it grants access without putting anything on the machine.
How you do it
List what is pending first, then receive the one you mean. This clones and indexes a repository onto the machine, so the ask is written to stop at Lyt's confirmation gate rather than run straight through.
Needs: Lyt initialized.
Using Lyt, list the vault invitations pending for me, then receive the one for the team/handbook vault onto this machine so I can search it — I want the vault cloned and indexed locally, not just the GitHub invitation accepted. Show me the invitation id you are about to accept and what it will put on my machine, then wait for my confirmation before anything is cloned.
Use the invitation id from lyt vault invites. Nothing is received until you confirm it: the command refuses to act unless --yes is added, and that flag is the confirmation. Assumes Lyt is installed and initialized on this machine.
lyt vault accept-share --invite 123456789What changes
A new person's first questions are answered from the team's own pages, by their own agent. The granting side of this — and how to inspect or revoke access later — is covered in the share a vault guide.