Skip to main content
A project can be shared by email. Everyone with access searches the same archive, and every session stays attributed to whoever recorded it.
The invitee does not need an account yet. The invite waits until they sign in. Addresses match the way mail providers deliver them: case never matters, and on Gmail neither do dots or a +tag, so an invite to Priya.Raman+work@gmail.com reaches priyaraman@gmail.com. They accept with resumecontext accept in the project directory, or from the dashboard.

​
Access is not the same as activity

Two different questions, deliberately kept apart:
  • Who has access: the member list.
  • Who has recorded work: the contributors.
Someone can be in one and not the other. A teammate invited this morning has access and no history; someone removed last week has history and no access. The dashboard shows them separately, and your agent is told not to confuse them.

​
Removing someone

Their access ends immediately. The history they already recorded stays in the archive and stays attributed to them. Removing a person does not rewrite the project’s past.
The project owner cannot be removed. Delete the project instead.