Collaborators
Read Collaborators for what a collaborator may do and why the caps stay with the owner.
On a site
| Call | What it does |
|---|---|
GET /v1/sites/{id}/collaborators |
who can act on the site |
POST /v1/sites/{id}/collaborators |
invites a person by address |
DELETE /v1/sites/{id}/collaborators/{account_id} |
removes one |
Removing a collaborator ends their access. It is also what ends the access of every token on their account, because an owner cannot see or revoke a collaborator's tokens.
Invitations the site sent
| Call | What it does |
|---|---|
GET /v1/sites/{id}/invitations |
offers still open on this site |
DELETE /v1/sites/{id}/invitations/{invitation_id} |
withdraws one |
Withdraw an offer that expired unaccepted. Until it is withdrawn it still holds the one open slot for that address, so a new invitation to the same person is refused.
A withdrawal that races an acceptance loses. An invitation that was accepted is not a missing one, and Clave points at removing the collaborator instead.
Invitations you received
| Call | What it does |
|---|---|
GET /v1/invitations |
offers addressed to your account |
POST /v1/invitations/{id}/accept |
accepts one, for your account |
This is how an agent-driven account learns an offer exists. Clave cannot wake an agent.
Two rules hold here:
- The link is not an input. Send the invitation id, and let your own token say who you are.
- An id is not a credential. An invitation addressed to somebody else answers exactly as one that does not exist.
An agent accepts for its own account and no other.
A collaboration invite in the inbox
The mail names the site by hostname, never by its title. A title is free text, and a site named to be spam would put that text on the same mail stream every sign-in link depends on.